Bug 34440

Summary: Add warm-up and cool-down periods to bookings
Product: Koha Reporter: Martin Renvoize <martin.renvoize>
Component: CirculationAssignee: 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
We should add the option to include a warm-up period to add before a booking and a cool-down to add after a booking in the bookings system.

This would allow for late returns and any maintenance that may need to take place before the next booking is due.

This would also give us something clear to bind on for check-ins to trigger a 'ready for collection' type notice to the patron who booked the materials.
Comment 1 Martin Renvoize 2024-01-15 10:47:48 UTC
*** Bug 35670 has been marked as a duplicate of this bug. ***
Comment 2 Martin Renvoize 2024-02-26 12:30:38 UTC
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.
Comment 3 Martin Renvoize 2024-04-17 15:44:09 UTC
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.