Access OLIB defaults and edit settings
Note: These are settings that affect the operation of OLIB as a whole and are only accessible to System Managers.
- In the Menu go to System Administration> OLIB Defaults.
- Click the Defaults record to display the details.
- Click modify record to make changes.
Available User and Circulation defaults
|Expiry Date||The expiry date that defaults when a new User Category is created.
The number of days of membership which will default into a newly created User Category.
Only one of these should be set as they are mutually exclusive settings.
|Warning Days Before Expiry||The number of days before a user’s membership expires that a warning message displays during issues/returns.|
|Show Only Local Transactions||Yes/No whether to show transactions in Users: Circulation History, for all locations against a user – or for just the location set in OLIB Web. The default No means that all transactions are shown by default. This also applies to Copy transaction history lists.|
|Default User Email Root||Set a default root email ID so that as you create each user on the system OLIB automatically inserts the non-personal elements of their email address. Set here at an overall system level or set at Location level for different root email addresses depending on user location. (Circ. Details sheet of the Locations layout).|
|IRR Transaction Types||The default system level Transaction Types displayed in the Issues/Returns/Renewals (Circ Desk) screen. These can be removed, added or the order changed.|
|Automatic Reduced Loan||Enter Yes to reduce the loan period when a reservation queue exists. Amend the Loan terms to the reduced number of loan days.|
|Main Renew Trans Msg||Controls the wording of the messages in the Renew All function. Do not alter the values between the * *.|
|Fines Renew Trans Msg||Controls the wording of the messages about fines in the Renew All function. Do not alter the values within the * *.|
|Traps Renew Trans Msg||Controls the wording of the messages about traps in the Renew All function. Do not alter the values within the * *.|
|Maximum Automatic Renewals||Enter a value that is the maximum number of times an item can be renewed automatically, once it has reached its due date. OLIB then renews loans on the due back date, rather than setting them to overdue. This can also be configured in Copies, Users, Loan Terms, User Categories. If set at these levels, it overrides the system setting in OLIB Defaults. Maximum value is 999|
|In Transit Text||In a typical scenario, a user in Location A reserves an item on loan that belongs to Location B. When the item is returned at Location B, it is held as normal, but Location B then issues it In Transit to Location A. The reservation record indicates that an item has been held to satisfy the reservation, and the barcode of the held item is displayed in the By Barcode field. The text that is displayed to the right of the barcode to make it clear that the item is in transit (so staff don’t go looking for it on the Items For Collection shelf), is configurable here in OLIB Defaults. The message also indicates when the item was sent in transit and the location to which it was sent.|
|Stop OPAC Circ. Transactions Default||
Yes/No flag for OPAC/SIP/NCIP circulation trap messages. When you create a new Copy/Title/User trap, or a Standard trap, there is an option to stop circulation transactions going ahead for those affected copy/title/user records. If you enter e.g. Yes here in OLIB Defaults, then when you are creating new traps, Yes will always default into the trap record.
This default can also be set at the PC Location level, instead of, or as well as, the OLIB Defaults system wide level. The default will apply from the PC Location if set; if not set at that level, then the default from OLIB Defaults applies.
|Stop SIP Circ. Transactions Default|
|Stop NCIP Circ. Transactions Default|
|Default OCAPI log level||For support purposes (the results need to be queried in sql).|
|SIP Date Format||Select one of the valid Oracle date formats if required for SIP processing. A date in this more readable format is then passed back to the SIP client for return dates. If SIP Date Format is configured at Location level, that setting will take precedence over OLIB Defaults.|
|Mandatory Password (SIP)||Used for SIP Patron Authentication.|
|Include Email In BE (SIP)||
Whether the patron's email address should be included in the BE field in SIP's (64) Patron Information response.
If NULL or set to Yes, the email address is included.