-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Propose a strategy for hold/recalls for multi-volume works #1453
Comments
Should we consider this a bug in Folio and file it upstream? |
I'm not sure it matters whether it's a FOLIO bug or not, we'll need a plan or local work-around before going live. |
@cbeer I agree that we need to fix it regardless, but it's still interesting to me whether we think of this as a bug in Folio. |
Could we prevent title level requests from being made if it's a multi-volume work? Then we leave it up to the patron to select the correct item. |
We're currently placing title-level holds for hold/recall requests in order to let the ILS figure out what item to deliver.
FOLIO's notion of a title-level hold seems to imply it will pick any item within an instance, whether or not its an additional copy of the same volume or a totally different volume. For most resources this may not be a problem, but multi-volume works seem to be problematic.
The text was updated successfully, but these errors were encountered: