Summary: | OPAC reports incorrect hold limit in warning | ||
---|---|---|---|
Product: | Koha | Reporter: | Owen Leonard <oleonard> |
Component: | Hold requests | Assignee: | Kyle M Hall <kyle.m.hall> |
Status: | NEW --- | QA Contact: | Bugs List <koha-bugs> |
Severity: | normal | ||
Priority: | P5 - low | CC: | gmcharlt |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
See Also: |
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8238 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12200 |
||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: |
Description
Chris Cormack
2010-05-21 01:27:46 UTC
If C4::Reserves::CanBookBeReserved is already doing the queries to check whether something can be placed on hold, can we get it to return the maximum and current holds numbers at the same time? I wonder how to make this easy to understand for users. We now have several limits that could trigger: - system preference maxreserves for a global limit - limits on number of holds per record in circ rules - limits on number of holds per itemtype in circ rules Especially for the settings in circ rules giving a good feedback to the user might be really difficult as library and itemtypes (might be different on the same record) can also play a role. |