[Koha-bugs] [Bug 34473] "Holds Waiting Over..." is not matching the ReservesMaxPickupDelay syspref

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

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

Emily Lamancusa <emily.lamancusa at montgomerycountymd.gov> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |emily.lamancusa at montgomeryc
                   |                            |ountymd.gov

--- Comment #2 from Emily Lamancusa <emily.lamancusa at montgomerycountymd.gov> ---
Our staff and customers find this confusing too. I believe Koha did used to
consistently give customers the same amount of time (also 10 days in our case)
to pick up a hold once it is filled, and folks in our system came to expect
that.

(I know in theory the expiration date is supposed to mean that the customer
doesn't want it at all after that date, but you'd be surprised how many people
don't actually use the expiration date that way, no matter how we label it.)

Our hold policies are also very lenient in general, so in practice when a hold
expires "early", it usually just leads to staff starting the process over with
a new hold, which isn't a good use of anyone's time.

It would be awesome if this could be a syspref, so that libraries could choose
whether they wanted waiting holds to expire after exactly the number of days
defined by ReservesMaxPickupDelay, or to expire after whichever comes sooner -
ReservesMaxPickupDelay or the manual expiration date.

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