[Koha-bugs] [Bug 13756] Holds over date

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13756

Katrin Fischer <katrin.fischer at bsz-bw.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED
                 CC|                            |katrin.fischer at bsz-bw.de

--- Comment #2 from Katrin Fischer <katrin.fischer at bsz-bw.de> ---
(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)

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.