Summary: | Allow different limits for on-the-shelf holds vs holds on checked out items | ||
---|---|---|---|
Product: | Koha | Reporter: | Rhonda Kuiper <rkuiper> |
Component: | Hold requests | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | andrew, gmcharlt, slmontesdeoca |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: |
Description
Rhonda Kuiper
2023-02-15 17:48:43 UTC
Our library is interested in this development as well. The new rule allowing a separate limit for on shelf items means less pulling holds for our hardworking Pages. Plus the hold shelves fill up so quickly. We can't keep up without a limit! We've been doing this manually so far, but a development in Koha would help us tremendously. As Koha's hold data exists now, an on-shelf hold really forgets that it was on-shelf once it gets checked in -- the hold doesn't remember whether the book came from a return or from the stacks. That makes it hard to set a limit like "a patron can only have 5 on-shelf holds at a time" as the patron's count of current on-shelf holds would go down each time a hold goes to Waiting. This could be a time-based limit, sort of like we do with purchase suggestions? Patrons can only submit X on-shelf holds within a window of Y hours? Or we could add something to the reserves table to record that a hold was on-shelf when it was placed. We thought about this and the option to add something to the reserves table to the record to indicate that a hold was a on-shelf hold when placed would work best for us. |