https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40792
Andrew Fuerste-Henry <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #16 from Andrew Fuerste-Henry <[email protected]> --- (In reply to David Cook from comment #15) > (In reply to David Cook from comment #14) > > Sounds like this is the opposite of bug 20955 ? > > Or maybe not. Holds is fun... Related to 20955, certainly. Getting overly detailed for any passing reader: I've found it helpful in these bugs to think about holds as having three steps: placing a hold, triggering the hold at checkin to capture an item, and then fulfilling the hold at checkout. Bug 20955 is about when we should or should not trigger a hold and capture an item at checkin. Currently we check the holds rules/policies at checkin and will not trigger a hold that violates those rules/policies (even though one may be able to place a hold that violates those rules/policies if AllowHoldPolicyOverride is enabled). This bug is about whether or not a hold gets fulfilled when an item gets checked out. As far as I know, currently a hold will always get fulfilled at checkout if there is a waiting item attached. This is good and should not change. But there's some difference of opinion among libraries about what should happen when a patron has a bib-level hold with no item waiting and checks out a non-holdable item attached to that bib. -- You are receiving this mail because: 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/
