When comparing the |z subfield data between call numbers, the capitalization, spacing, and punctuation must be exactly the same for SirsiDynix Symphony to determine that it found a match to satisfy the hold.
Every hold has a level to indicate the extent of the hold. In Demand Management, holds are either Title level holds or Copy level holds. If the library is part of a multilibrary system, these holds are applied across a range of item records to further indicate the extent of the hold.
| • | Title Level Hold |
| • | Copy Level Hold |
Information about each hold and its hold level is stored in the hold record.
In Demand Management, placing a Title level hold on a volume in a multivolume set may have unexpected results. If you place a Title level hold on Volume 3 of the Official Record of the Civil War, for example, any available volume of set will satisfy the hold.
A Title level hold places a hold on all copies of the title whose call numbers’ analytic portions (part, volume, or number) are the same, regardless of the base call numbers.
If a hold is placed on a specific volume of a multivolume set, Demand Management checks the call number’s |z field, which stores the part, volume, or number. If the |z subfield differs from the base call number, Demand Management detects that the item is a volume from a multivolume set. Demand Management places a hold on the requested volume and changes the label for the hold level from Title to Volume. The hold is now considered a Volume level hold. Volume level holds are considered a function of a Title level hold. The hold can only be filled by a copy of the requested volume, not just any volume in the multivolume set.
Example of a Title Level Hold
A user wants to check out The Adventures of Tom Sawyer and Huckleberry Finn. The library has a copy in the adult section and the juvenile section. However, both copies are checked out. Because the title is in two different sections of the library, it has two different call numbers. The user wants either a copy of this title, so a Title level hold is placed on this title. The user will be placed in the queue for both copies.
Example of a Volume Level Hold in Demand Management
A user wants a copy of Volume 3 from Ancient Greek Authors. Copies in the Main Library and Northstar Library are checked out. The staff member places a Title level hold on this item. Demand Management detects that the requested item is a volume from a multivolume set, so it changes the hold level label from Title to Volume. The user’s hold request can be satisfied with a copy of Volume 3 of the title from either library.
When comparing the |z subfield data between call numbers, the capitalization, spacing, and punctuation must be exactly the same for SirsiDynix Symphony to determine that it found a match to satisfy the hold.
A Copy level hold creates a hold on a specific physical copy of a title.
In Demand Management, if the requested copy would not normally be eligible to fill the hold, the operator is prompted for an override code to place the hold anyway.
For example, a library’s paperback copy of Milton’s Paradise Lost has been damaged due to heavy circulation, so it has been decided to hard bind the copy. However, a staff person in the Cataloging department discovers that the copy is checked out. She decides to place a Copy level hold on the item because she wants this specific physical copy.
The hold range is not used for Copy level holds because the operator is requesting a specific physical copy of a title.
Related topics
Getting Started in Demand Management
© 2006, 2014 SirsiDynix