Wishlist: Indicating records with holds when batch deleting

Bug #1913322 reported by Elaine Hardy
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Evergreen
Confirmed
Undecided
Unassigned

Bug Description

The new error message warning of holds present on a deleted bib record (see https://bugs.launchpad.net/evergreen/+bug/1398107) is very helpful. However, when batch deleting items it would be good to pair the error message with an indication of which bib record has the hold stopping the deletions so that catalogers can resolve the hold and proceed.

The presence of a hold or holds that can only be filled with the item being deleted stops the batch process. There is currently no way to determine which bib record has the offending hold without checking records for it. (Work around is to divide the batch into smaller numbers until you isolate the record.). Having the system identify the record or records with those holds would smooth the process out

Revision history for this message
Chelsea (ckovalevskiy) wrote :

No indication of which record is causing the error causes significant delays to what should be a quick process. The work around of dividing the batch into smaller numbers can take upward of 10 minutes for each issue.

Changed in evergreen:
status: New → Confirmed
Dan Briem (dbriem)
tags: added: circ-holds
removed: holds
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.