Bug 31777 - Allow for scheduling of holds
Summary: Allow for scheduling of holds
Status: RESOLVED DUPLICATE of bug 29002
Alias: None
Product: Koha
Classification: Unclassified
Component: Hold requests (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-10-13 15:22 UTC by Donna
Modified: 2022-10-17 14:42 UTC (History)
2 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Donna 2022-10-13 15:22:28 UTC
We have recently had libraries asking for the ability to "schedule" a hold. These scenarios are things that are not really suited for suspension or future holds functions. For instance, a faculty member needs a DVD for use in a class on a specific day and staff would like to enter a hold for that.  Another use scenario is for book clubs - I'd like to reserve copies for my club next month etc.  

Again, this is something asked for by libraries, but I'm not quite sure how it would work, just passing along the suggestion.
Comment 1 Katrin Fischer 2022-10-14 21:40:45 UTC
I think we had discussed this before and my feeling that putting reservations/bookings on top of the holds system might not be the best way to go as we already have so many moving pieces there and the goal is very different. For holds the goal usually is: get it to the user as fast as possible. For a reservation it is: make sure that the item is available at a certain time slot and make sure the user gets it exactly then.

But: Martin has been working on something that could be interesting for you:
bug 29002
Comment 2 Donna 2022-10-17 14:42:01 UTC
Thanks, Katrin!  I thought I remembered something similar and that would definitely work!  I'm going to mark this as resolved.

*** This bug has been marked as a duplicate of bug 29002 ***