Bug 34458 - It should be possible to change the pickup location for in transit holds
Summary: It should be possible to change the pickup location for in transit holds
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Hold requests (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on: 30500
Blocks:
  Show dependency treegraph
 
Reported: 2023-08-02 14:41 UTC by Tomás Cohen Arazi
Modified: 2023-08-17 08:26 UTC (History)
6 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tomás Cohen Arazi 2023-08-02 14:41:35 UTC
Bug 30500 introduced a way to change the pickup location for in transit holds, in the OPAC. And now bug 34024 highlighted we don't have a feature on the staff interface. I open this bug so we discuss possible implementation details.

Questions:
- Does it need any workflow?
- Should this be reported somewhere? (e.g. in transit holds report highlighting those that changed)
- Should it be notified.
Comment 1 Emily Lamancusa 2023-08-09 20:30:55 UTC
My understanding is the OPAC feature didn't add any new workflows or reporting under the assumption that, once the item was in transit, it wasn't going to be touched until it got to its destination anyway. Then when the item is checked in at its destination, the check-in function already handles checking the hold pickup location, initiating a new transfer, and notifying the staff member while they have the item in their hand so they can send it along to its new destination.

It seems to me like doing this in the staff interface wouldn't need any new workflows for the same reason (other than perhaps a confirmation modal). A patron notification would be a good idea to minimize the chances of the patron looking for their item at the wrong branch.

I'm not sure about reporting. I don't think we have a use case for it, but I can't speak for anyone else.

The OPAC feature has a syspref that allows libraries to decide which statuses (Pending, Suspended, and/or In-Transit) permit pickup location changes via OPAC, so there should probably be a similar syspref for the staff-side feature for consistency.

I see a couple of folks from libraries following this bug - any of you want to weigh in? :)
Comment 2 Rebecca Coert 2023-08-11 18:26:06 UTC
I was excited to see the OPACAllowUserToChangeBranch in 22.11 but immediately wondered why there wasn't also an option for this in the staff interface.  Thanks for opening this bug and discussion!

I agree that this should be made available on the staff side, and I'd like to request that it be available for adjustment on the Holds tab of the borrower's record, as well as on the Holds tab of the Bib record.  Staff here would appreciate not having to jump between screens to accomplish this task.

I think adding re-routing information to the /transferstoreceive.pl page would be useful, especially if things went missing while in transit.
Comment 3 Sally 2023-08-17 08:26:40 UTC
(In reply to Emily Lamancusa from comment #1)
> I see a couple of folks from libraries following this bug - any of you want
> to weigh in? :)

Yes, I agree with the points here:

- The staff need the feature; anything the patrons can do, the staff should be able to do
- As in the OPAC feature, a syspref to choose which statuses permit pickup location changes should exist
- The staff should also be able to modify the pickup location using the Holds tab in the patron account (when a record has 100+ holds on it, it's too easy to accidentally modify the wrong hold)

For reporting:

- I'd like to see the change recorded in the action logs 
- I think this should be the same for both this staff feature and the OPAC feature

Suspend/resume are already recorded in the action logs, including when a patron performs the action - and we use this data when reporting on how long it takes us to fill holds.

Changing location whilst in transit will impact fill times, so it would be important for us to be able to see how much the feature was being used and how much of an impact it was having.

Having the change in action logs would also mean we could run reports where intervention is needed.  For example, if an item is in transit to a library with few collections (i.e. high cost on the Transport Cost Matrix), we might decide that we'd be better reverting the in transit status and selecting an alternative copy, instead of waiting for the original copy to arrive at the original location and be sent onwards.