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

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

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

--- Comment #3 from Jonathan Druart <jonathan.druart at bugs.koha-community.org> ---
Created attachment 68228
  -->
https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=68228&action=edit
Bug 19287: Add ability to mark an item ‘Lost’ from ‘Holds awaiting pickup’ list

This is the main patch of this new enhancement.
The goal to this enhancement is to add the ability to mark items as lost
from the ‘Holds awaiting pickup’ page.
A new pref is added to control the behaviour, default is off
To enable it, you need to set the new pref CanMarkHoldsAwaitingPickupAsLost to
one of these two values:
- "Allow to mark items as lost"
=> The item will be marked as lost and the hold will be cancelled
- "Allow to mark items as lost and notify the patron"
=> Same as previously but the patron will be notified as well.

The notification is done using a new notice template
(code=CANCEL_HOLD_ON_LOST).
Feel free to suggest another default wording.

Test plan:
You need to clearly know how this page is working currently to make sure
this patch does not break existing behaviours
1/ Check 2 items out
2/ Add a hold on one of the items
3/ Add 2 holds on the other item
4/ Return the item to mark the hold as waiting
5/ From here you will be able to see entries in the "Circulation › Holds
awaiting pickup" page
6/ I suggest to make a backup of this table, to avoid to repeat the
previous steps. You will need to test the following steps using the
different values of the pref
7/ Cancel the hold
8/ Mark the items as lost
=> You will receive feedback messages depending on different situations:
* The CANCEL_HOLD_ON_LOST does not exist
* The patron does not have an email address (but the notice has been
enqueued! It is the current behaviour with other notices)
* The notice has been enqueued
* The hold has been cancelled

QA Notes:
1/ C4::Circulation::LostItem is usually called with the second parameter
set, which will mark the issue as returned. It is weird that this
behaviour cannot be controlled by a pref.
2/ From which library do we want to pick the notice? This patch use
reserves.branchcode

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