These preferences are general settings for your system.
Get there: More > Administration > Global System Preferences > Administration
This system preference allows you to choose between using the precise value or a rounded value when charging fees.
The Central Authentication Service (CAS) is a single sign-on protocol for the web. If you don’t know what this is, leave these preferences set to their defaults.
Default: Don’t use
Asks: ___ CAS for login authentication.
Asks: Logout of CAS when logging out of Koha: ___
CAS single logout means that a user gets logged out not only from the CAS server but also from all visited CAS client applications when logged out in one of them or after reaching a timeout.
The CAS server has to be set up to allow single logout for this to take effect, otherwise the behavior will remain unchanged
Asks: The CAS Authentication Server can be found at ___
Google OpenID Connect¶
Visit the Google Developers Console to obtain OAuth 2.0 credentials such as a client ID and client secret that are known to both Google and your application.
Create a project, and give it some details to help you identify it later
Next search for the Google Identity and Access Management API
Enable the Google Identity and Access Management API
Go to ‘Credentials’ and set the OAuth cosent screen values
Next choose to ‘Create credentials’ from the ‘Credentials’ page
Choose ‘Web application’ from the ‘Application type’ menu and fill in the form presented
Change the ‘Authorized Redirect URIs’ to http://YOUROPAC/cgi-bin/koha/svc/auth/googleopenidconnect
You will be presented with your values for your client ID and your client secret after saving
Asks: Google OAuth2 Client ID ___
Asks: Google OAuth2 Client Secret ___
Asks: Use Google OpenID Connect login: ___
You will need to select OAuth2 when creating an app in the google cloud console, and set the web origin to your_opac_url and the redirect url to your_opac_url/cgi-bin/koha/svc/auth/googleopenidconnect .
Default: Don’t Allow
Asks: ___ users logging in with Google Open ID to automatically register.
Asks: ___ Use this branchcode when automatically registering a Google Open ID patron.
Asks: ___ Use this category when automatically registering a Google Open ID patron.
Asks: Google OpenID Connect Restrict to domain (or subdomain of this domain) ___.
Leave blank for all google domains
These preference are related to your Koha interface
Default: lots of
Asks: Show ___ debugging information in the browser when an internal error occurs.
lots of - will show as much information as possible
no - will only show basic error messages
some - will show only some of the information available
This preference determines how much information will be sent to the user’s screen when the system encounters an error. The most detail will be sent when the value level is set at 2, some detail will be sent when the value is set at 1, and only a basic error message will display when the value is set at 0. This setting is especially important when a system is new and the administration is interested in working out the bugs (errors or problems) quickly. Having detailed error messages makes quick fixes more likely in problem areas.
Default: all libraries
Asks: When editing circulation rules show ___ the rules by default.
logged in library’s
This preference controls the default value in the branch pull down found at the top of the Circulation and fines rules.
Default: all libraries
Asks: When editing notices and slips show the ___ notices and slips by default.
logged in library’s
This preference controls the default value in the branch pull down found at the top of the Notices & slips tool.
Default: all libraries
Asks: When editing overdue notice/status triggers show the ___ rules by default.
logged in library’s
This preference controls the default value in the branch pull down found at the top of the Overdue notice/status triggers.
Asks: Separate columns in an exported report file with ___ by default.
This preference determines how reports exported from Koha will separate data. In many cases you will be able to change this option when exporting if you’d like.
This is the default ‘From’ address for emails unless there is one for the particular branch, and is referred to when an internal error occurs.
Asks: Use ___ as the email address for the administrator of Koha.
This preference allows one email address to be used in warning messages set to the OPAC. If no email address is set for the branch this address will receive messages from patrons regarding modification requests, purchase suggestions, and questions or information regarding overdue notices. It is recommended that a email address that can be accessed by multiple staff members be used for this purpose so that if one librarian is out the others can address these requests. This email address can be changed when needed.
Asks: Show itemtype icons in the staff interface: ___
This preference allows the system administrator to determine if users will be able to set and see an item type icon in the catalog in the staff interface.
If images of item types are disabled, text labels for item types will still appear in the staff interface.
The OpacNoItemTypeImages system preference is used to show or hide the itemtype images in the OPAC.
Asks: Use ___ as the email address that will be set as the replyto in emails
By default replies to notice emails will go to the library email address, if you would like to specify a default email address for all replies to notices you can do that here.
Asks: Use ___ as the email address set as the return path, if you leave this empty the KohaAdminEmailAddress will be used.
The return path is the email address that bounces will be delivered to. By default bounced notices will go to the library email address, if you would like to specify a default email address for bounces to go to then fill in this preference.
Asks: Email to redirect all messages to: ___ (Leave this field empty to send messages to their normal recipient)
This system preference is used to override any patron email address with this one when sending notices. This is meant to be used in a testing environment to test notices and to avoid spamming patrons.
This is not to be used in a production environment. Otherwise, no patron will receive their intended notices.
Asks: ___ staff and patrons to create and view saved lists of books.
This preference controls whether the lists functionality will be available in the staff client and OPAC. If this is set to “Don’t allow” then no one will be able to save items to public or private lists.
These preferences are related to logging into your Koha system
Default: Don’t require
Asks: ___ staff to log in from a computer in the IP address range specified by their library (if any).
Set IP address range in the library administration area
Get there: More > Administration > Basic Parameters > Libraries
This preference protects the system by blocking unauthorized users from accessing the staff client program and settings. Authorized and unauthorized users are determined by their computer’s IP addresses. When the preference is set to ‘Require’, IP authorization is in effect and unauthorized IP addresses will be blocked. This means that staff cannot work from home unless their IP address has been authorized. When set to ‘Don’t require’, anyone with a staff client login will have access no matter which IP address they are using.
Default: Don’t prevent
Asks: ___ staff (but not superlibrarians) from modifying objects (holds, items, patrons, etc.) belonging to other libraries.
This preference should only be used by library systems which are sharing a single Koha installation among multiple branches but are considered independent organizations, meaning they do not share material or patrons with other branches and do not plan to change that in the future. If set to ‘Prevent’ it increases the security between library branches by: prohibiting staff users from logging into another branch from within the staff client, filtering out patrons from patron searches who are not a part of the login branch conducting the search, limiting the location choices to the login branch when adding or modifying an item record, preventing users from other branch locations from placing holds or checking out materials from library branches other than their own, and preventing staff from editing item records which belong to other library branches. All of these security safeguards can be overridden only by the superlibrarian, the highest level of privileges.
It is important that this value be set before going live and that it NOT be changed
Asks: Prevent staff (but not superlibrarians) from viewing and approving/denying patron modification requests for patrons belonging to other libraries. ___
Asks: ___ check for change in remote IP address for session security. Disable only when remote IP address changes frequently.
When this preference is set to ‘Enable’ Koha will log you out of the staff client if your IP address changes as a security measure. For some systems the IP address changes frequently so you’ll want to set this preference to ‘Disable’ to prevent Koha from logging you out of the staff client every time that happens.
This is meant to help those whose IP address changes several times during the day, setting this preference to ‘Disable’ is not recommended otherwise because it is removing important security features from your staff client.
Default: in the MySQL database
Asks: Store login session information ___
as temporary files
in the MySQL database
in the PostgreSQL database
PostgreSQL is not yet supported
This preference allows administrators to choose what format session data is stored in during web sessions.
Asks: Automatically log out users after ___ seconds of inactivity.
This preference sets the length of time the Staff Client or OPAC accounts can be left inactive before re-logging in is necessary. The value of this preference is in seconds. At this time, the amount of time before a session times out must be the same for both the Staff Client and the OPAC.
SSL client certificate authentication¶
Asks: Use ___ field for SSL client certificate authentication
the common name
the email address
UnsubscribeReflectionDelay, PatronAnonymizeDelay & Patron Removal Delay
This is a new feature that allows you to set a certain amount of days after a patron has submitted an unsubscribe request(refused consent), anonymize accounts that are locked/expired and remove anonymized patrons.
Asks: Use following search engine: ___