[Koha-bugs] [Bug 32565] Holds placed when all libraries are closed do not get added to holds queue if HoldsQueueSkipClosed and RealTimeHoldsQueue are enabled

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

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

--- Comment #12 from Katrin Fischer <katrin.fischer at bsz-bw.de> ---
Pre-allocation will require new logic that we currently not have and has some
issues that we could encounter.

Allocation right now can be random (StaticHoldsQueueWeight), static
(RandomizeHoldsQueueWeight) or driven by the transport cost matrix
(UseTransportCostMatrix). 
Only "open" libraries will be looked at with HoldsQueueSkipClosed.

So we have a complex system.

When pre-allocating, we could do open libraries first, but when all are closed,
should we take the duration of the closing into account? It could be just a
holiday closure or it could be library that is closed for months. What if the
calendar entries were changed after pre-allocating (closing period is
extended)? The hold could get stuck in limbo basically forever, while it sits
on the shelf in a library close by.

I believe pre-allocating is not good, as we don't have a way to "review" those.

What do you mean by have RTHoldsQueue check tomorrow? 

RTHoldsQueue means that every time a hold/item/biblio is added or updated we
trigger a 'review' of the holds queue entry for the bibliographic record
concerned. It's triggered by an action - so we'd still need to locate the
unallocated and trigger this step for these holds.

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