[Koha-bugs] [Bug 19288] Holds placed on a specific item after a next available hold will show varied results

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19288

--- Comment #14 from Nick Clemens <nick at bywatersolutions.com> ---
(In reply to Katrin Fischer from comment #13)
> We should not make such a change without fully understanding the why and how
> here. That's why I pick 'in discussion'. If we end up doing it, I want to be
> able to explain to the libraries why.

Imagine Patron A has a 'next available' hold and Patron B has an item level
hold on Item A

To find the holds on an item we call Koha::Item::current_holds - this will
returnholds on the specific item, it will never find 'next available' holds
because they are not on a specific item - We will display Patron B

At checkin we actually check the holds, and we check hold_fill_targets at some
level. The effect being that if you have not run the holds queue the item will
fill the higher priority hold for Patron A, however, if you have built the
holds queue it could do a few things:
If there are multiple items available then Patron A may get assigned Item B for
the queue and Patron B will get Item A - for this scenario Item A will trigger
for patron B
If there is only one available item then Patron A will be assigned Item A and
Item A will trigger Patron A

This scenario seems reasonable, the holds queue is going to try and fill the
holds so that both patrons can get the item they want if it can. For display
though we would need to check the DB for both hold_fill_targets and specific
holds. 

I don't think this information of who gets the hold is so important on details,
since we will resolve it at checkout, I think simply letting the librarian know
this item is held should suffice. I will ask around internally for more
opinions

-- 
You are receiving this mail because:
You are watching all bug changes.