https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33523 trevor.diamond@mainlib.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |trevor.diamond@mainlib.org --- Comment #4 from trevor.diamond@mainlib.org --- I'm on 24.11 in a cooperative and this issue is causing a lot of staff confusion. However, I think I may have identified a behavior that might help a little with a workaround? Need someone else to test/verify though. Standard set of circulation rules has an item type policy that LIBTHINGS is local holds only. Have a bib with holdings at libraries A through G. Patron From A places a hold, which is allowed because that library has a copy. Library A is checked out though. The holds queue now has the request for Library A patron for the item at Library B. This is obviously not correct, since B's item would only be for B. I think that is what this bug is about? TEST WORKAROUND: Place an item type hold policy on Library B for local holds only (the same as in the standard rules, but applying it at the library level instead of the standard level for all libraries). Wait for the holds queue to rebuild. Check if the Patron A request is on any queue. When I did this in my system, the hold request not only got removed from the queue at Library B, but it didn't show up for ANY of the libraries that had on the shelf copies. This seems to imply that when there only a standard item type hold policy, the system won't always pay attention. But if there is a library level item type policy, then the system will check first the library level policies and THEN the system level policies. Does this make sense to anyone? The stadnard policy didn't apply until there was also at least one library level policy on the same item type. But then then standard policy was correctly applied to all other libraries (so the request will only show up for Library A when that copy is available and none of the other libraries were asked even though the library level policy was only applied to one library). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.