https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30687
Kyle M Hall <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |Signed Off CC| |[email protected] --- Comment #7 from Kyle M Hall <[email protected]> --- (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. -- 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/
