[Koha-bugs] [Bug 9253] If an item is reserved, at the opac it is marked as available

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

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9253

Paul Poulain <paul.poulain at biblibre.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |paul.poulain at biblibre.com

--- Comment #4 from Paul Poulain <paul.poulain at biblibre.com> ---
(In reply to comment #3)
> I am a bit worried about the consequences of this. I think this can only
> work for item level holds.
You're right and wrong. This work only when the *item* is on hold. So either :
 - a "1st available" has been placed, and an item has been checked in (to the
reserve is now attached to an item)
 - a item level hold has been placed

> Also, when does the status change? 
The onhold flag is set by
      if( $reserve_status eq "Reserved"){ $itm->{'onhold'} = 1; }

$reserve_status is defined by 
     my ($reserve_status) = C4::Reserves::CheckReserves($itm->{itemnumber});

However, one thing that worry me is that the rules for opac-detail.pl display
are not the same as the rules for staff detail.pl display:
In staff display, it seems that the items.reservedate is used to have a display
of hold-er & hold status. Jonathan, am I right ? Why use a different method in
the staff interface ?

> When the item is placed on hold or when the item is checked in and waiting
> for the patron? I feel like it should be the latter.
> I think libraries allow patrons to check out the item as long as it has not
> been pulled from the shelf, but not quite sure here.
I think we must :
 * be consistent between staff & opac
 * can display that an item is reserved as soon as possible. use case = 9AM,
patron A places a hold, 10AM, patron B check OPAC and see the document is
"available", 11AM, the item become "waiting" for patron A, 11:10AM, patron B
arrives at the library and becomes angry because the item is no more
available... We can't warn an item is reserved when the hold is "1st
available", but as soon as we've an item, we should.

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