| Summary: | Too many holds message needs to be smarter | ||
|---|---|---|---|
| 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: | gmcharlt |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| GIT URL: | Initiative type: | --- | |
| Sponsorship status: | --- | Comma delimited list of Sponsors: | |
| Crowdfunding goal: | 0 | Patch complexity: | --- |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
|
Description
Christopher Brannon
2019-08-19 22:50:06 UTC
I am not sure if this would be better. If Koha says too many, I know that the reason is in the circulation rules (somewhere it limits the number of holds for the user). If it says 'none of the items' I would assume that I can still place holds on other records and that the issue is item related. I think being as precise as possible should be the goal to allow for easy 'debugging' of circuation rules and to understand what's going on. All I can say is that it leads to confusion to some libraries using it. I think we could be more accurate. I think having it generalized like this is over simplification. I am with you on more accurate vs. it being too general. |