Block patrons from putting holds on items they already have checked out
Our site manager said this was a previous long-standing enhancement request and suggested I check here and vote on it. I can't find anything that matches, so am starting an idea.
We have several patrons at different branches placing holds on items they already checked out so as to bypass our unwritten guideline of leaving items available to others for 24 hours before being checked out again. Now, for older items this isn't a problem and staff are allowed to make exceptions, but this practice is becoming a issue. We do allow one renewal, but apparently this isn't enough for some patrons.
Diana
shared this idea
-
Jessica Sayers
commented
We have multiple patrons attempting to always have our limited mobile hotspots checked out using this workaround. It's hard to enforce our loan policy on them when the ILS doesn't provide a method to support that policy, and it's too much work for staff to constantly monitor.
This has been under review for 3 years - it's long past time to make it a priority.
-
Kasey Blankenship
commented
I'm a bit shocked to see that this was submitted in 2023 and is still in the "Under Review" status. This block should be a configurable setting.
Our library experiences the same issues with patrons finding workarounds for our checkout limits. This is especially a concern with new and popular items that never make it to our shelves due to the same patron checking it out and holding it.
-
Amy
commented
I agree with Beth Lane. Our libraries would like to prevent patrons from placing holds on "library of things" and "hotspots" [specific material types] that they already have checked out. Thank you.
-
Beth Lane
commented
I agree, particularly when customers are borrowing from "library of things". These collections are usually small.
-
AdminSamantha Quell
(Admin, Innovative)
commented
As people see this enhancement request, please comment. There is a request under Vega Discover right now asking for the ability to place holds on items out (https://ideas.iii.com/admin/v3/ideas/46756351), while this request is asking us to restrict them. So there is clearly a need for configuration to support different library policies. Having comments on different library policies would be very helpful.
(Edited by admin)