[Koha-bugs] [Bug 19288] Holds placed on a specific item after a next available hold will show varied results

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

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

Nick Clemens <nick at bywatersolutions.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|In Discussion               |Signed Off

--- Comment #11 from Nick Clemens <nick at bywatersolutions.com> ---
(In reply to Katrin Fischer from comment #10)
> I am not sure here if less information is better. Maybe the original message
> should just be phrased a bit better?
> 
> We switch from:
> 
> Item-level hold (placed 05/11/2019) for delivery at Centerville. Hold for:
> katrin koha (42) 
> 
> To:
> 
> There is a hold on this item 
> 
> I am also not sure how this related to the initial bug report, where Kelly
> reported that sometimes the item level hold would be filled first, even if
> not first in the queue. Can you explain?
> 
> While the first message is very 'talkative', maybe we can find some middle
> ground? Something like:
> 
> Item-level hold for .... (priority x) (similar to how we display the
> priority in the OPAC)
> 
> And I would leave out the hold placed and pickup location.

As I understand the main issue, the problem is that Koha shows one hold on the
details page, and triggers another at checkin.

Different factors can affect which hold will be triggered at checkin, and we
don't want to do too many calculations to show the item details, so we are
getting a simple 'what's in the queue' and showing the wrong name.

Trying to show the correct name is the issue. Until the hold is actually
waiting it can fluctuate. I think this solution gives the library the info they
need "Check this item in to trigger a hold" without adding info that may be
wrong

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