Summary: | Holds daily is not looking at item type when not allowing holds | ||
---|---|---|---|
Product: | Koha | Reporter: | Kelly McElligott <kelly> |
Component: | Hold requests | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | normal | ||
Priority: | P5 - low | CC: | catrina, gmcharlt, hebah, sbrown, tech, tomascohen |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: | |||
Bug Depends on: | 15486 | ||
Bug Blocks: |
Description
Kelly McElligott
2020-06-02 13:07:34 UTC
This reads like a bug - updating. Hi there! Salina Public Library chiming in. We stumbled into this issue as well, so it would be very nice for this functionality to work. We have begun to increase the amount of holds people can place on items but as a way to help out our circulation department the ability to limit the number of holds per day would be nice. This is still relevant as of 21.11.05. Being able to use the feature with the accurate per-item type limit would be very helpful! I think it might not be easy to implement or maybe only with a fallback to the record level itemtype. When a hold is placed without being limited to an item type, it's not easy to determine which itemtype should apply if there are multiple items that could fill the hold with different itemtypes. Perhaps we should consider deleting this column from the table. Its location is misleading. (In reply to Catrina Berka from comment #5) > Perhaps we should consider deleting this column from the table. Its location > is misleading. Can you explain what you mean a bit more? |