What’s Different in Encore? October 16, 2009
Posted by virtualnotes in encore.Tags: encore, holds, Library Catalog, book bag
add a comment
Now that we have been using Encore for almost two weeks, what have you or your patrons found different with Encore?
One thing to point out, if you or your patrons are using the book bag to request multiple titles in the Classic Catalog, you will find in Encore this is not what the Book Bag does. The user can use Book Bag to send themselves or someone else either brief information or full information about the item but no holds are placed. In order to place a hold the user needs to use the Request It link.
Share what other ‘features’ you have found.
Encore Question September 21, 2009
Posted by virtualnotes in Library Catalog.Tags: encore, holds
add a comment
I had a very good question about Encore today. A staff member started using Encore to see how it was going to impact her work as well as the patrons. Once of things she noticed was Encore does not display the number of holds on a title. The display is not on the brief nor the Bib. Well, the good news – this is an enhancement to be found in Encore 3.3 which is currently in Beta and soon to be released. According to Rice Majors – Product Manager the number of holds will display the same way in Encore as they do in the Classic Catalog.
Did you know? Patrons can Freeze Requests August 30, 2008
Posted by virtualnotes in Did you know?.Tags: freezing requests, holds
add a comment
“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 available
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.
|
NOTE |
| 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.
