►User Management > Locations: Circ Details: Reservations/Recalls
►Circulation Reference Data > User Categories
►Circulation Reference Data > Loan Terms
The following parameters should be defined to set up Reservations. The same set of parameters is used regardless of whether the reservation is placed in WorldView / OLIB Web / the OPAC.
Caution: note that the Reservation Rules should first be considered carefully and planned out prior to setting up reservations in OLIB. Once you have a single rule set up, all other materials / users are excluded from reservations. Do not change the rules during a busy operational time.
A number of parameters can be set against each Location record. These are found in Locations: Circ. Details: Reservations/Recalls section.
This page should be completed as follows:
This defines how reservations operate in the OPAC for users who are registered at that location. Consider carefully how this works with Multiple Locations and Reservation Rules
blank: leave Reservation Logic blank to indicate that users registered at this location can reserve anything, subject to limitations imposed in the other fields.
|Reservations if Expired
|If you set this field to No, users from this location will not be able to place reservations if their membership has expired, i.e. if the Expiry Date in their User record is on or before the current system date.
|Reservations if Banned
|If you set this field to No, users from this location will not be able to place reservations if they are 'banned' from circulation.
|Reserve If On Loan?
Enter No in this field if you do not wish to allow users from this location to be able to reserve an item that they currently have on loan.
If set, when the user attempts to place a reservation on an item that he/she currently has on loan, a message will be displayed to this effect the user will not be able to submit the reservation.
|Reserve if Reserved
|Either [null] or Yes in this field means you will allow users from this location to be able to reserve an item that they already have reserved (they can do this in WebView). This field determines whether users at this location can have multiple reservations per title. If it is set to No, the user will not be allowed to submit more than one reservation at a time for the same title. If an attempt is made to do this, a message is displayed to inform the user that the reservation was not possible because he/she already has a reservation on the title.
|Used for multi-site locations and reservation rules (below).
Indicate the number of days for which a held item will be retained. When an item is held, the calculation of the hold expiry date takes into account the library’s closed days and holidays. A process in daystart flags any held reservations as Held – Soon To Expire, when the To Expire On date is the day after the current system date. Library staff can run a filtered search on all reservations with this status and decide whether to warn the user that the hold on the item will be removed if he/she does not collect it that day or the following day.
Another process in daystart flags any held reservations that are past their expiry date as Held – Should Be Cancelled. Library staff can run a filtered search on all reservations with this status and decide whether to cancel the hold and return the item to the shelves (or hold it for the next user on the reservation list).
Additional Hold Period fields
If you have entered a location-copy category hold period, this takes precedence over a hold period you have defined in the Copy Category record itself.
|Reserve New Copies?
A Yes/No flag relevant to new copies, or copies whose category has been changed to a reservable category.
If set to No, copies are NOT added to existing active reservations:
If this flag is empty, the default position is Yes.
|Auto Expire Held Res?
|A Yes/No flag to indicate whether Held reservations should automatically expire and move on to the next user in the queue after the number of days specified.
These fields are used for Multiple Locations and Reservation Rules. The following fields implement reservations in multi-site libraries: Reservable User Categories, Reservable Locations, Reservable Copy Categories, Reservable Copy Statuses, Reservable Loan Statuses, Reservable Rules.
(Recall Num and Res Per Copy are not currently implemented).
Notice destination and notice destinations
These fields are used for Reservations Received Notifications and Rotas. It is now possible to configure OLIB so that Reservation Received notifications are only sent to the locations of the copies reserved. Where the reserved copies are at several locations, the Reservations Received Notifications would be sent to one location at a time in accordance with a pre-defined rota.
NCIP Password Required
If this field is set to Yes then when you make an NCIP request for which OLIB needs to authenticate the user, then the user record in OLIB must have a valid password, and the NCIP request must have the same password included. If the field is set to No or NULL then the password is never checked at all. (This means that in this case if a password is supplied on the NCIP message that is different to the users password then it won't be checked and authentication will still succeed).
Submit Res. As Active (NCIP), (SIP), (Folio)
Yes, No flag determines whether reservations placed by these functions should be submitted as Active reservations.
- Yes: reservations submitted in e.g. WebView by users registered at this location will be submitted as Confirmed reservations
- No / not set: e.g. WebView reservations will be submitted as Unconfirmed
This flag is not set by default, you should review it to ensure that it is set correctly for your library.
Set maximum reservations per user
This can be done in 3 places:
- Go to each User category enter the maximum number of reservations on the Details page in Max Res. This is the maximum that a user of that category can have at any one time.
- This field applies to all users in that category unless they have a different value in the Max Res field in their own User record. If this field is blank on the user record the value from the user category is used by default.
- In addition it is possible to set a value for Max Res in the Loan Terms for a particular User category/Copy category combination.
Default Reservation Type
The default reservation type (Title, Copy, Set) can be configured in Admin Client Defaults.
|potentially reserve all copies of a title
|reserve specific copy/ies
|reserve all copies in a set
The system administrator first needs to add the Default Reservation Type attribute to the Admin Client Defaults layout using Layout Manager.
This is implemented in the Reservations domain whenever you create a new reservation.
- Go to System Administration> Admin Client Defaults.
- In modify mode choose Title, Copy or Set from the Default Reservation Type drop down.
- Save the changes.
Whenever you create a new reservation this default will be implemented.