Bug 12095

Summary: Hold queue should take closed dates into account
Product: Koha Reporter: Christopher Brannon <cbrannon>
Component: Hold requestsAssignee: Bugs List <koha-bugs>
Status: RESOLVED DUPLICATE QA Contact: Testopia <testopia>
Severity: enhancement    
Priority: P5 - low CC: gmcharlt, jdemuth, katrin.fischer, marjorie.barry-vila, techservspec
Version: unspecified   
Hardware: All   
OS: All   
Change sponsored?: --- Patch complexity: ---
Documentation contact: Documentation submission:
Text to go in the release notes:
Version(s) released in:

Description Christopher Brannon 2014-04-16 14:28:06 UTC
I recommend that the hold queue should take closed dates on the calendar into account.  At least it should be an option.  And that option should include that it takes the dates into account if the number of consecutive days closed is X amount.  For example, if a library is closed 2 days, it might not be a factor, but if a library is closed for 4 or 5 days, it is.

This is particularly important for systems with branches that are open very little during the week, or perhaps they are closed during parts of the year, like school libraries.

Christopher
Comment 1 jdemuth@roseville.ca.us 2017-08-25 20:20:54 UTC
We are currently on 16.11.09 and still have this problem because we have RFID returns that check in items immediately. We keep our items on hold for 8 days so if an item is checked in on a closed day, it could send the notice to the patron saying it expires on a closed day which can be confusing and upsetting to the patron if they miss the hold. We are considering changing the days the items can be on hold and/or staff procedures but no matter how many days we change it too, this may still happen. I would love to see if there is a better work around out there or if we can get this bug moving.

Thanks, 

Jen DeMuth
Comment 2 Katrin Fischer 2017-08-27 10:29:54 UTC
I think this should already be possible, see bug 12803 and system preference HoldsQueueSkipClosed! 
If this doesn't cover what you need, please add a step by step description of how the problem happens to make it more clear.

*** This bug has been marked as a duplicate of bug 12803 ***
Comment 3 jdemuth@roseville.ca.us 2017-09-08 18:48:36 UTC
Hi Katrin, 

That feature solved our problem here, thanks so much for the information.

Jen