Bug 2786 - Allow waiting holds to be diverted to different branch
Summary: Allow waiting holds to be diverted to different branch
Status: CLOSED FIXED
Alias: None
Product: Koha
Classification: Unclassified
Component: Hold requests (show other bugs)
Version: Main
Hardware: All All
: P3 enhancement (vote)
Assignee: Galen Charlton
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-15 06:58 UTC by Owen Leonard
Modified: 2021-03-04 15:31 UTC (History)
5 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 Chris Cormack 2010-05-21 00:55:51 UTC


---- Reported by oleonard@myacpl.org 2008-11-15 06:58:45 ----

We often get requests by patrons to send a hold to a different branch from the one that was selected when the hold was placed. This might be because they chose the wrong branch at the time (better in 3.0 now that it preselects your branch), or because they simply changed their minds.

Right now the only way to manage this is to cancel the hold, add it back in, and change the priority. This is less than ideal not just for the inconvenience but because of the poor interface for changing hold priority.



---- Additional Comments From gmcharlt@gmail.com 2008-11-17 06:38:28 ----

So the workflow would be something like this?

1. Patron requests an item.
2. Request is filled eventually and item is waiting at branch A.
3. Patron requests that item be transferred to branch B instead for pickup.  (Should it be possible to make that request via the OPAC, or do patrons just call the library?).
4. Circ staff at branch A initiates a transfer to branch B.
5. Circ staff at branch B receive the item and check it in.  Item is automatically sent to the hold shelf.



---- Additional Comments From oleonard@myacpl.org 2008-11-18 08:05:20 ----

Yes Galen that's exactly how I would expect it to work. It happens rarely enough that I don't think it needs to be possible via the OPAC.



--- Bug imported by chris@bigballofwax.co.nz 2010-05-21 00:55 UTC  ---

This bug was previously known as _bug_ 2786 at http://bugs.koha.org/cgi-bin/bugzilla3/show_bug.cgi?id=2786

Actual time not defined. Setting to 0.0

Comment 1 Mirko Tietgen 2012-12-17 01:10:19 UTC
Hey Owen & Galen,

is this still valid?
Comment 2 Owen Leonard 2012-12-17 17:49:29 UTC
(In reply to comment #1)

> is this still valid?

It is.
Comment 3 Marc Véron 2015-12-20 15:55:20 UTC
Still valid?
Comment 4 Lisette Scheer 2017-08-23 19:40:29 UTC
This would be great. We have 7 branches and still in 16.05 often have this problem, especially with new items.
Comment 5 Katrin Fischer 2019-05-04 18:35:43 UTC
Would this work with the new feature to revert the waiting status?
Comment 6 Lisette Scheer 2019-05-05 05:00:48 UTC
(In reply to Katrin Fischer from comment #5)
> Would this work with the new feature to revert the waiting status?

Yes, that does work! Once the hold is reverted we can change the pickup branch and check the item in to send it on. 
Lisette
Comment 7 Katrin Fischer 2019-05-05 08:32:14 UTC
(In reply to Lisette Scheer from comment #6)
> (In reply to Katrin Fischer from comment #5)
> > Would this work with the new feature to revert the waiting status?
> 
> Yes, that does work! Once the hold is reverted we can change the pickup
> branch and check the item in to send it on. 
> Lisette

Great, thx for checking!