This report is a follow-up for bug 13478.
Some ideas to start with: Option for specific biblio can be set/unset on staff catalog detail page. Might be interesting to add the option for item types too. For some item types you may want to force item holds. Add a script that allows you to incidentally add or remove books from the list under specified conditions.
Created attachment 36606 [details] [review] Bug 13479: Enable/disable forced item holds on biblio level This is a follow-up of report 13478. If you set OPACItemHolds to 'selectiveforce', you can now enable or disable forced item holds on biblio level on the Holds tab of the staff detail page.
This work is not yet ready, but this may helps those want to sign off on report 13478.
Created attachment 36608 [details] [review] Bug 13479: Enable/disable forced item holds on biblio level This is a follow-up of report 13478. If you set OPACItemHolds to 'selectiveforce', you can now enable or disable forced item holds on biblio level on the Holds tab of the staff detail page.
Created attachment 36921 [details] [review] Bug 13479: Enable/disable forced item holds on biblio level This is a follow-up of report 13478. If you set OPACItemHolds to 'selectiveforce', you can now enable or disable forced item holds on biblio level on the Holds tab of the staff detail page. TEST PLAN: [1] Run the adjusted unit test (t/db_dependent/Reserves.t). [2] Set OPACItemHolds to Allow. [3] Check the Holds tab of staff catalog detail. You should not see the Force item holds-box. [4] Set OPACItemHolds to Selectively force. [5] Goto the Holds tab of staff catalog detail. [6] Enable forced item holds. Check behavior with placing hold in OPAC. [6] Disable forced item holds. Check behavior with placing hold in OPAC.
(In reply to M. de Rooy from comment #1) > Might be interesting to add the option for item types too. For some item > types you may want to force item holds. Moved this to a new report: bug 13839.
Bug 13478 needs attention first.