https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30687
--- Comment #9 from Katrin Fischer <[email protected]> --- (In reply to Kyle M Hall from comment #7) > (In reply to Katrin Fischer from comment #6) > > Hi Aleisha, could you please look into Daniel's comment? If the hold cannot > > be filled at the pickup-location this might not work as intended. > > The library community has spoken loud and clearly in the past and present, > and the consensus is that librarians should be able to force holds that are > unfillable. In the past I attempted to limit forced holds to those that > would be filled, and what we found out is that libraries utilize those > unfillable holds for a variety of reasons. We ended up reverting those > changes in community. We also have partners with this very same issue > Aleisha is describing. I think it's safe to say that the questions of "can > this hold be placed" and "can this hold be filled" are very much separate > questions. In that spirit, I think the question of "should this item be > trapped instead of transferred back" should be dealt with on a separate bug > report. I am actually confused about this one and feel like I have been missing out on the discussion. How do libraries utilize holds that can never be filled? I'd be interested in examples to understand better. At the moment there is no way to utilize those unless you change the item values or you cancel the hold as it can otherwise not move to filled. I don't remember from testing, but does this unlock all pickup locations or will a hold with no pickup location be placed? (see bug 31086). -- 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/
