Summary: | Don't trigger holds when patrons have already reached limit of checkouts | ||
---|---|---|---|
Product: | Koha | Reporter: | Christopher Brannon <cbrannon> |
Component: | Hold requests | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | george, gmcharlt, kebliss, tmisilo |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
See Also: | https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15489 | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: |
Description
Christopher Brannon
2014-10-29 20:33:48 UTC
You kinda lost me there "I would love to see holds updated to act kind of like the Netflix DVD queue system." :) (In reply to Katrin Fischer from comment #1) > You kinda lost me there > "I would love to see holds updated to act kind of like the Netflix DVD queue > system." :) Are you being funny, or just don't know? Maybe it is just a US thing? Basically, a patron could have placed 50 holds, but they are only allowed to have 10 holds at a time. Thinking about this more, we can kind of do this, but it means limiting the checkouts to 10. But the idea behind this is that their next hold request cannot get triggered until they are below the threshold. That threshold could be: * Number of items currently checked out * Number of items currently checked out from other libraries * Number of items currently in transfer or waiting I'm leaning towards the second one: Number of items currently checked out from other libraries. But, you could have 50 items on their way, and then after the 10th item checks out, the rest turn around and go home or to the next person. Waste of time. It might need to be a combination of the second and third. number of items currently transfer or waiting, and then if that is below the threshold, number of items currently checked out from other libraries. This idea stems from examples of patrons that hoard lots of items through holds. We also have patrons that place tons of holds and either don't pick them up, or pick through what comes in and only checks out what they want. Holds are not for browsing here. I HOPE that helps. Yes it does. Indeed Netflix loaning DVDs were never a thing here in Germany, afaik. So I didn't know how this works/worked. I think you are right that this turns into limiting checkouts in some way. So a hold can only trigger when there is 'room' on the patron account? I am not sure if we could make this transparent to the user. They might just assume that they can return items prior to picking up their holds and I would think that of a valid use of the system - timing their visit to the library to do both things. And we can limit the amount of holds a patron can place too... Not sure if that would not overcomplicate. I think that it should be up to the system admin to implement, not how complicated we might think it is for the patron. If a library can communicate this well, it would be worth it. It could simply be communicated at the time the hold is being placed like a warning: "Please note that holds are not filled if you have reached the limit of your library's checkouts." Maybe we could even have something that would display checkout limits, if any. It should be up to the library whether this would be implemented or not, leaving it to the library as to whether a patron's holds can be filled if their checkout limits have been reached. As is, a patron gets notified that they have a hold, and they go to pick it up, only to find out that they can't check it out until they return something. They probably are not prepared with this dilemma, and have to return home to get something to return so they can claim their hold. With a new option, they are not even eligible or notified until they are under the limit. |