[Koha-bugs] [Bug 25891] build_holds_queue can be daemonised

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

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

--- Comment #5 from Katrin Fischer <katrin.fischer at bsz-bw.de> ---
Hi Sally, sorry I didn't get back to that. I totally understand your use case.

Maybe we could start small by highlighting holds already filled (or removing
them) on the report page? This way staff who picked the book could see, why it
is no longer needed.

I imagine we could add a trigger on filling or cancelling a hold that checks
the holds queue... but not sure how hard this would be to do.

I was always told the slow schedule was on purpose. The explanation I came up
with for myself is that there are several options on how library to fill a hold
gets picked. One being the "random" option ( RandomizeHoldsQueueWeight ). My
thinking was that if the report ran again and again this would constantly
change the library to pick the item.

It would be great to discuss this with other consortia/multi branch libraries.

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