Skip to content
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

Open
cbeer opened this issue May 18, 2023 · 4 comments
Open

Propose a strategy for hold/recalls for multi-volume works #1453

cbeer opened this issue May 18, 2023 · 4 comments

Comments

@cbeer
Copy link
Member

cbeer commented May 18, 2023

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.

@cbeer cbeer converted this from a draft issue May 18, 2023
@jcoyne
Copy link
Contributor

jcoyne commented May 18, 2023

Should we consider this a bug in Folio and file it upstream?

@cbeer
Copy link
Member Author

cbeer commented May 18, 2023

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.

@jcoyne
Copy link
Contributor

jcoyne commented May 18, 2023

@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.

@jcoyne
Copy link
Contributor

jcoyne commented Jul 27, 2023

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.

@cbeer cbeer moved this from 🔖 Ready to 📋 Backlog in Searchworks/FOLIO Summer 2022/23 Sep 1, 2023
@thatbudakguy thatbudakguy self-assigned this Sep 15, 2023
@thatbudakguy thatbudakguy removed their assignment Oct 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 📋 Backlog
Development

No branches or pull requests

3 participants