Summary: | Create message for patrons with multiple holds on the same item | ||
---|---|---|---|
Product: | Koha | Reporter: | Karen <karen> |
Component: | Hold requests | Assignee: | Nick Clemens (kidclamp) <nick> |
Status: | CLOSED FIXED | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | 1joynelson, bibliwho, gmcharlt, jonathan.druart, lisettepalouse+koha, liz, nick |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | Trivial patch |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: |
20.05.00
|
|
Circulation function: | |||
Bug Depends on: | |||
Bug Blocks: | 26762, 26763 | ||
Attachments: |
Bug 19718: Show message if patron has existing holds on a title
Bug 19718: Show message if patron has existing holds on a title Bug 19718: (follow-up) Make messages translatable Bug 19718: Show message if patron has existing holds on a title Bug 19718: (follow-up) Make messages translatable |
Description
Karen
2017-11-29 22:18:40 UTC
We also have had this problem a lot. Many of our older patrons will place a hold and then place an additional hold a couple weeks later when it has not yet arrived for them. So maybe what you'd like is the ability to allow multiple holds per branch or per user category, so that if someone else had allowed multiple holds, you wouldn't be required to? Having trouble following Liz's suggestion, but we have the same issue as Karen & Lisette. Karen's idea for a warning message seems like a good one to us. Sometimes a patron will have a very good reason for placing multiple holds on the same record (teacher wanting multiple copies, Vol.'s 1 & 2 cataloged on the same record, etc.) Other times, a patron will only want a single item but will have simply forgotten that they've already placed a hold. Created attachment 92489 [details] [review] Bug 19718: Show message if patron has existing holds on a title To test: 1 - Set a rule to allow multiple holds on a title 2 - Place a single hold in the opac for a patron 3 - Return to record and attempt place a second hold 4 - Note there is no message but that you must match the type placed before (item or record level) 5 - Don't place the hold 6 - Apply patch 7 - Attempt to place second hold again 8 - Note there is a message informing you of which level hold you may place 9 - Test with both item/record level holds and placing a single request or multiple requests Created attachment 95120 [details] [review] Bug 19718: Show message if patron has existing holds on a title To test: 1 - Set a rule to allow multiple holds on a title 2 - Place a single hold in the opac for a patron 3 - Return to record and attempt place a second hold 4 - Note there is no message but that you must match the type placed before (item or record level) 5 - Don't place the hold 6 - Apply patch 7 - Attempt to place second hold again 8 - Note there is a message informing you of which level hold you may place 9 - Test with both item/record level holds and placing a single request or multiple requests Signed-off-by: donnab <donna@bywatersolutions.com> Switching to Signed off - the sandbox doesn't do it automatically, so I think it was just forgotten. That makes it untranslatable. (In reply to Jonathan Druart from comment #7) > That makes it untranslatable. Can you explain? The strings in the template are: """ You already have at least one [% bibitemloo.forced_hold_level %] level hold on this title. All further holds must be [% bibitemloo.forced_hold_level %] level. """ With forced_hold_level == "item" or "biblio". Argh, thx for catching that. Created attachment 98946 [details] [review] Bug 19718: (follow-up) Make messages translatable Created attachment 99048 [details] [review] Bug 19718: Show message if patron has existing holds on a title To test: 1 - Set a rule to allow multiple holds on a title 2 - Place a single hold in the opac for a patron 3 - Return to record and attempt place a second hold 4 - Note there is no message but that you must match the type placed before (item or record level) 5 - Don't place the hold 6 - Apply patch 7 - Attempt to place second hold again 8 - Note there is a message informing you of which level hold you may place 9 - Test with both item/record level holds and placing a single request or multiple requests Signed-off-by: donnab <donna@bywatersolutions.com> Signed-off-by: Katrin Fischer <katrin.fischer.83@web.de> Created attachment 99049 [details] [review] Bug 19718: (follow-up) Make messages translatable Signed-off-by: Katrin Fischer <katrin.fischer.83@web.de> Nice work everyone! Pushed to master for 20.05 enhancement not pushed to 19.11.x |