Bug 17662 - Patron can have more than one hold when records are merged
Summary: Patron can have more than one hold when records are merged
Status: RESOLVED DUPLICATE of bug 16766
Alias: None
Product: Koha
Classification: Unclassified
Component: Cataloging (show other bugs)
Version: 3.22
Hardware: All All
: P5 - low enhancement
Assignee: Galen Charlton
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-11-18 23:29 UTC by Christopher Brannon
Modified: 2020-01-11 16:40 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christopher Brannon 2016-11-18 23:29:38 UTC
We had a patron that placed a hold on two different records, one was an item level hold, and the other was a first available hold.  These records were merged, and the system held on to both holds!

I am not sure how you would go about preventing this from happening, except maybe check if any kind of hold exists on both records with the same borrower number and stop the merge so the staff member could go and remove one.  Or perhaps it could show both holds and the staff member choses to delete either or both holds.
Comment 1 Marc Véron 2017-04-17 06:35:50 UTC
Valid on current master?
Comment 2 Katrin Fischer 2020-01-11 16:40:20 UTC

*** This bug has been marked as a duplicate of bug 16766 ***