https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31546
Bug ID: 31546
Summary: Hold delays
Change sponsored?: ---
Product: Koha
Version: 21.11
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P5 - low
Component: Hold requests
Assignee: [email protected]
Reporter: [email protected]
QA Contact: [email protected]
CC: [email protected]
It seems there is a disadvantage to hold fulfillment if holds are delayed in
transit.
Take for example, Joe requests an item in a record to be picked up at library
A. Library B checks that item in and triggers Joes request. It is in transit,
but for any number of reasons, transit is taking longer than usual. Meanwhile,
other patrons request items from that same record, and are triggered and
fulfilled. Joe is at the mercy of the system and the delays in transit.
Would there be a way for other items on the record that happen to get checked
in at library A to step in and swap holds with the one in transit and fulfill
his hold quicker, since he is at the top of the list waiting? Maybe based on
his priority level? So, for example, another item from that record comes in,
and if it doesn't have a hold and Joe's hold was a first available, it could
take the place of the one in transit? And if there is a hold for that item and
lower than Joe's priority, the one in hand could be changed to Joe, and the one
in transit would be reassigned to the patron the ready one was for?
I don't know if this would wreak havoc with the local holds priority, but this
scenario seems more fair than making someone at the top of the list wait
because of something out of their control.
--
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
[email protected]
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
