[Koha-bugs] [Bug 19287] Add ability to mark an item 'Lost' from 'Holds awaiting pickup ' list

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Tue Oct 24 18:15:54 CEST 2017


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

--- Comment #19 from Jonathan Druart <jonathan.druart at bugs.koha-community.org> ---
Hi Sally and Séverine,

(In reply to Sally Healey from comment #17)
> How does this interact with system preference
> ExpireReservesMaxPickUpDelayCharge/WaitingHoldCancelationFee ?

The pref ExpireReservesMaxPickUpDelayCharge is only used by the cronjob
cancel_expired_holds.pl. No cancellation fees are charged from this form.

> Also, this might be out of the scope of this bug (maybe a new bug?) but in a
> similar scenario:
> 
> Patron visits library to collect item.
> Item is missing.
> Staff marks item as lost.
> Patron still wants the item, so a new hold needs to be placed.  
> 
> Is it possible to retain the original hold so another copy can fill the
> request instead of cancelling it?

I would consider this as another enhancement indeed. However I do not think it
is linked directly to this one particularly.


(In reply to Séverine Queune from comment #18)
> I now have a button "Mark item as lost", thanks !
> 
> Behaviour is correct also for the "Holds waiting over" tab, except for the
> last and, to me, the main part of this patch : items are supposed to be
> marked as lost and not be available, but they are not.
> 
> This is one of the enhancement we ask for, as you can see on the third point
> of the description of this ticket :
> >- "set the field “items.notforloan” or “items.itemlost” (define in a system
> > preference) from “0” to a value from the same ‘authorized values list’ and set
> > in another system preference").
> 
> Dis I misunderstood something in you're comment #16 ?

Nope, I completely forgot that part sorry. I will try to provide a fix soon.

> I open ticket #19500 about the name of the module.

Thanks!

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


More information about the Koha-bugs mailing list