Staff Creating Holds on Non-Cir Items - Changed Permissions to Limit This
We've noticed a significant problem with staff creating holds on items that can't be loaned (non-cirulating; lost; deleted; etc.) because they have the ability to bypass item block messages. We tried to fix this gap by removing the "Override Request Blocks" permission from general circ staff, but have found that when we do staff can't bypass patron alerts (as simple as 'patron has a hold to pick up').
There seem to be two challenges with using the "Override Request Blocks" permission: it overrides both patron and item blocks (where other 'override' permissions are more granular); also there doesn't seem to be good distinguishing between blocks that should prevent actions, and alerts that provide information - we either have to choose to give too much access to users, or prevent basic request functions.
We'd like to see the "Override Request Blocks" permission split into 'Override Request Patron Blocks' and 'Override Request Item Blocks' to help circumvent these problems. We'd also like to see an 'Override Alerts' permission(s) developed, which would not override blocks, and would allow us the ability to treat alerts and blocks differently.
Idea Value
Depending on their set-up, most libraries may be dealing with the same problem we have with staff placing holds on non-circulating items, leaving patrons waiting on holds that will never be filled, and also item and bib records that can't be deleted until the hold expires. The challenge with alerts and blocks overall is likely the cause of other challenges, as well. A fine-tuning of these override permissions are needed to give appropriate flexibility for staff hold functions.