Bug 13756 - Holds over date
Summary: Holds over date
Status: CLOSED FIXED
Alias: None
Product: Koha
Classification: Unclassified
Component: Hold requests (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-24 15:25 UTC by Christopher Brannon
Modified: 2020-11-30 21:45 UTC (History)
3 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christopher Brannon 2015-02-24 15:25:47 UTC
Would like to see hold over date calculated at time of hold and recorded in the requests table with the hold.  As I understand it, holds over dates are calculated when the holds over table is looked at.  This is a very loose calculation, since if the value of ReservesMaxPickUpDelay is changed at any time, the holds over period changes with that, regardless of when the hold was filled.  Some libraries may prefer to have that date fixed in place on the table, while others might want the fluid, on the spot calculation, so perhaps it should be an option.

For me, as someone dealing with consistency and reports, a fixed date in the table is preferred.  It would be great to be able to run custom reports and see those dates.  It would be great to have that date show in the holds information for both item and patron screens on the staff side.  It would be great to be able to print that date on the hold slips.  It would be great to know that if we let patrons know how long they have to pick something up, that won't change because an adjustment is made to ReservesMaxPickUpDelay (although, how often does that happen?).

My two cents.

Christopher
Comment 1 Christopher Brannon 2015-04-16 19:06:04 UTC
Another benefit of going this route is that it will lend itself to more flexibility down the road, if for example, the holds over date (the ReservesMaxPickUpDelay which should be renamed to HoldsOver) is set for each library in the circulation rules rather than a global setting.

This one is my 3 cents, making an even nickel.  :)

Christopher
Comment 2 Katrin Fischer 2020-01-06 15:09:27 UTC
(In reply to Christopher Brannon from comment #0)
> Would like to see hold over date calculated at time of hold and recorded in
> the requests table with the hold.  As I understand it, holds over dates are
> calculated when the holds over table is looked at.  This is a very loose
> calculation, since if the value of ReservesMaxPickUpDelay is changed at any
> time, the holds over period changes with that, regardless of when the hold
> was filled.  Some libraries may prefer to have that date fixed in place on
> the table, while others might want the fluid, on the spot calculation, so
> perhaps it should be an option.
> 
> For me, as someone dealing with consistency and reports, a fixed date in the
> table is preferred.  It would be great to be able to run custom reports and
> see those dates.  It would be great to have that date show in the holds
> information for both item and patron screens on the staff side.  It would be
> great to be able to print that date on the hold slips.  It would be great to
> know that if we let patrons know how long they have to pick something up,
> that won't change because an adjustment is made to ReservesMaxPickUpDelay
> (although, how often does that happen?).
> 
> My two cents.
> 
> Christopher

I believe this is all resolved - the 'hold pickup expiration date' is saved to reserves.expirationdate (currently overwriting a 'not needed after' date set by the patron)