Overview

Project website koha-community.org/documentation
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
File mask */LC_MESSAGES/apis_protocols.po
Translation file Download cs/LC_MESSAGES/apis_protocols.po
Last change April 26, 2025, 1:04 a.m.
Last author Weblate Admin
yesterday

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 272 3,737 22,674
Translated 0% 0 0% 0 0% 0
Needs editing 9% 26 1% 69 2% 526
Read-only 0% 0 0% 0 0% 0
Failing checks 2% 7 1% 27 1% 168
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 90% 246 98% 3,668 97% 22,148
Last 12 months Previous

Activity in last 12 months

0 changes 8 changes 0 changes 0 changes 0 changes 0 changes 0 changes 11 changes 0 changes 4 changes 0 changes 3 changes 252 changes 2 changes 3 changes 1 change 7 changes 1 change 5 changes 2 changes 3 changes 2 changes 1 change 0 changes
Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar

Quick numbers

3,737
Hosted words
275
Hosted strings
0%
Translated
2
Contributors
and previous 30 days

Trends of last 30 days

−1%
Hosted words
+100%
+8%
Hosted strings
+100%
—
Translated
—
+50%
Contributors
+100%
User avatar admin

Resource updated

  1. koha-manual
  2. apis_protocols
  3. Czech
The “cs/LC_MESSAGES/apis_protocols.po” file was changed. yesterday
User avatar None

String added in the repository

  1. koha-manual
  2. apis_protocols
  3. Czech
e.g. if someone gets married and their surname changes then the new surname only needs to be updated in the existing LDAP database and that will be synced down to the Koha database automatically if the update configuration is set to 1.
 
yesterday
User avatar None

String added in the repository

  1. koha-manual
  2. apis_protocols
  3. Czech
Whereas the update LDAP config field (in the same file allows) allows for user information in the LDAP database to be synced down to the Koha database.
 
yesterday
User avatar None

String added in the repository

  1. koha-manual
  2. apis_protocols
  3. Czech
The replicate LDAP config field for LDAP in the koha-conf.xml file allow the Koha database to be added to with a new borrower account whenever a user logs into Koha (either the staff client or OPAC) with their LDAP username and password (assuming the same username and password does not already exist in the Koha database).
 
yesterday
User avatar None

String added in the repository

  1. koha-manual
  2. apis_protocols
  3. Czech
Hostname can either be a alphanumerical name or it can be the LDAP server IP address (its optional to write port number).
 
yesterday
User avatar None

String added in the repository

  1. koha-manual
  2. apis_protocols
  3. Czech
Note about hostname:
 
yesterday
User avatar None

String added in the repository

  1. koha-manual
  2. apis_protocols
  3. Czech
Policy: Policy defines the permitted SIP2 commands allowed from SC’s in this institution. For example: renewal=”true” means that SC’s at that institution have permission to send renewal item SIP2 commands.
 
yesterday
User avatar admin

Resource updated

  1. koha-manual
  2. apis_protocols
  3. Czech
The “cs/LC_MESSAGES/apis_protocols.po” file was changed. 2 days ago
User avatar None

String added in the repository

  1. koha-manual
  2. apis_protocols
  3. Czech
If plack is not disabled then LDAP errors are displayed in the plack-error.log file. If plack is disabled then the location that LDAP errors are printed to is either the opac-error.log file (if the user is logging into the OPAC) or the intranet-error.log file (if the user is logging into the staff client) All of these three log files are accessible in the following directory:
 
2 days ago
User avatar None

String added in the repository

  1. koha-manual
  2. apis_protocols
  3. Czech
Note about the replicate and update fields:
 
2 days ago
Browse all translation changes