“Freezing a request” means that the patron’s position in the hold queue is skipped over until the request is reactivated. This allows the patron to stay in the hold queue while holds are filled for patrons further down in the queue.
A patron cannot request that a hold be “frozen” (i.e., suspended) if:
· the hold can be fulfilled by an item that is:
o in-transit, or
o on the hold shelf for the patron
· the hold status is “in transit” or “on the hold shelf”
· the item is paged and the patron’s hold is next in the hold queue
· the patron’s position in the hold queue is fewer than the number of available items that can satisfy a bibliographic-level hold
When a patron freezes a request, the system changes the patron’s “not wanted before” date to 255 days (a system-specific maximum value) from the hold’s creation date.
|The 255 setting is a system setting that indicates that a request is being skipped over until reactivated. Patrons can reactivate the hold via the WebPAC. However, library staff do not have the ability to change the Not Needed By (NNB) date when the system sets it to 255. A skipped over record remains in the queue until the patron reactivates the hold, even if the hold extends beyond the actual date calculated by the NNB date.|
To freeze a request, the patron:
1. Selects the column for the request.
2. Click the Update List button.
To reactivate a request, the patron:
1. Clears the column for the request.
2. Clicks the Update List button.