Summary: | Add warm-up and cool-down periods to bookings | ||
---|---|---|---|
Product: | Koha | Reporter: | Martin Renvoize <martin.renvoize> |
Component: | Circulation | Assignee: | Martin Renvoize <martin.renvoize> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | esther.melander, gmcharlt, kyle.m.hall, lisette.scheer, marie.hedbom, testopia |
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: | ||
Bug Depends on: | 36120, 36641, 35944 | ||
Bug Blocks: | 36383, 36666 |
Description
Martin Renvoize
2023-07-28 11:24:07 UTC
*** Bug 35670 has been marked as a duplicate of this bug. *** Quoting Esther Melander: This is perhaps the beginning of a list of circulation rules needed for bookings. To replicate: 1. Find an item and create a booking to start tomorrow for Patron 1. 2. Check out the same item to Patron 2 today. The bookings work correctly in that the item checked out today is also due today. However, if that item actually went out the door with Patron 2 the chances of getting it back in time for the booking is zero. A circulation rule is needed to prevent circulation within so many days of a booking and/or a circulation alert is needed for staff to not let the book circulate because of a pending booking. Work in progress for this is available at https://github.com/PTFS-Europe/koha/tree/bug_34440. I'm still refining the last pieces of it but will be asking for feedback imminently. The best way to help it continue to move forward at the moment however is to look at the dependencies and help those work their way through signoff and QA. |