►Alerting> Notices
►Circulation Reference Data> Locations: Circ Details: Reservations/Recall Parameters
If you have several locations in OLIB working together on reservations, you can set up a rota system for receiving the reservation received notices.
This information shows how you can set up a rota to determine what Locations should receive the Reservation Received notification and in what order. There is also background information About reservations received notifications and rotas.
Configure in the order shown below:
You will need to create one of these notices for each OLIB Location which is to receive reservations:
#ITEM# - all reserved copies
#ITEML# - reserved copies at the location specified in the notice’s location field
#ITEMX# - reserved copies at locations other than the location specified in the notice’s location field
<body><basefont size="3" color="blue" face="Arial"/>
A new reservation has just been received as follows:
<br />
<br />User: <NAMESDISP2>
<br />Barcode: <BAR>
<br />Reservation Ref: <RES_RESNO>
<br />Title: <TI>
<br />Reserved On: <RES_DATE>
<br />The following copies at this location have been identified to honour it:
<br /><TABLE>#ITEM#<TR><TD VALIGN="TOP"><CP_LOLD></TD><TD VALIGN="TOP">
<CP_BC></TD><TD VALIGN>="TOP"><CP_SM></TD></TR>
#ITEML#</TABLE><br />
<br /><br />Please go to the Reservations domain to process it.
</body>
Set up the notice rota for each Location that will process reservations:
You can also refine the rota order by these values. For example to set Available "21-day loan" copies higher up the rota than Available "14-day loan" copies or On Loan copies. They can be used with or without Priority - if you leave Priority blank, OLIB inserts the priority number based on the order you create each setting:
Res Rec'd Notice Rota
Copy Location | Copy Category | Copy Status | Loan Status | Priority | Sent Count |
---|---|---|---|---|---|
City Library | 21 DY | 1 | |||
City Library | 14DY | 2 | |||
Brincliffe | 7DY | 3 |
Using Priority and one or more of Copy Category / Copy Status / Loan Status together you can refine even further:
Copy Location | Copy Category | Copy Status | Loan Status | Priority | Sent Count |
---|---|---|---|---|---|
Location A | 21 DY | 1 | |||
Location B | 21DY | 2 | |||
Location C | 21DY | 2 | |||
Location A | 7DY | 3 | |||
Location B | 7DY | 4 |
In this example, if a reservation is placed by a user at Location A for an item that has 21DY copies at Location A, Location B and Location C, the notice rota will include Location A at the top.
Second priority for the rota, are reserved copies at Location B and Location C also with Category 21DY. Locations B,C share the load based on number of Res Rec’d alerts sent to each of these locations previously from Location A.
Third priority are reserved copies at Location A but with Category 7DY.
Fourth priority are reserved copies at Location B also with Category 7DY.
If you make a mistake building the rota or you need to subsequently alter the rota, it is easy to remove an entry:
OLIB removes that entry in the rota.
When a user places a reservation, and the reservation becomes confirmed, the rota is visible in the reservation details layout. There is a Notices section displayed (this requires the system manager to use Layout Manager to add these fields).
The Notice Rota field lists the locations that are on the reservation’s rota. They are sorted in priority order, with any locations that have an equal priority sorted by location long description. Reservation Received notices will be sent to the various locations in the order they are listed here, except for locations that have an equal priority. Notices that are sent to these locations will be load-balanced and randomised so that each location ultimately receives an equal number of notices.