Bug 31698 - Add ability to move a hold to a new biblio/item
Summary: Add ability to move a hold to a new biblio/item
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Hold requests (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement with 60 votes (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-10-06 13:22 UTC by Nick Clemens (kidclamp)
Modified: 2024-06-05 10:06 UTC (History)
14 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 Nick Clemens (kidclamp) 2022-10-06 13:22:25 UTC
Sometimes a library gets a new edition, or a new copy of an item and would like to be able to directly provide this to a patron with an existing hold.

We propose add a new action on the holds table on request.pl 'Move hold'

For an item level hold it would provide a modal with a barcode entry box so librarians can scan a new copy in hand, and move the hold to that specific item

For a biblio level hold it would provide a modal with a search box - entering keywords would search the catalog, and add a 'Move hold' button to the results - similar to 'Add to basket form existing record' search in acquisitions
Comment 1 Kristi 2023-10-18 19:10:29 UTC
We would love to see this capability! It would be ideal if moving all holds on the bib at once were built in. This would be helpful for bibs with many (over 50) holds on them.
Comment 2 Felicity Brown 2024-01-16 19:30:13 UTC
This would be a fantastic solution to a problem we've been having with re-orders of older titles, where we get the newer edition as a replacement. Our current workaround creates some pretty yucky metadata.
Comment 3 Kristi 2024-01-16 19:38:01 UTC
(In reply to Felicity Brown from comment #2)
> This would be a fantastic solution to a problem we've been having with
> re-orders of older titles, where we get the newer edition as a replacement.
> Our current workaround creates some pretty yucky metadata.

Same for us.
Comment 4 Rhonda Kuiper 2024-05-20 22:00:55 UTC
This function would be fantastic for our library.  Currently, our processes to move holds is time consuming and prone to errors.  This would be great!  
One thing to specifically note is that the date that the hold was placed on the original item would be preserved.  This was the order of the holds queue could be preserved and sorted in the the holds on the new item.
Comment 5 Piia Semenoff 2024-06-05 10:06:15 UTC
This sounds good! I totally agree that currently the transfer of the holds takes time and the possibility of errors is high. 

I think these are the things that can go wrong now while doing the hold transfer and should be considered when building this function:

- It should be taken into account whether the hold has been suspended or whether it is a itemlevel hold or a non-urgent hold. 

- In addition, you must choose the right pick-up location for the hold, change the hold date and priority of the hold.