Wishlist: Action to Delete Records from Item Status screen

Bug #2009857 reported by Mackenzie Johnson
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
New
Undecided
Unassigned

Bug Description

Evergreen 3.8.0

A staff member has suggested that an Action be added/re-added (it is possible this action was available in older versions) that allows -- with the right permissions and a very clear Warning pop-up before executing the action -- for the (bulk) deletion of the bib records scanned items are attached to, as opposed to just being able to delete the scanned items. While we recognize the option to create a record bucket and bulk delete from there exists, this staff member values the cumulative efficiency gained from handling the action right in the item status screen.

Revision history for this message
Elaine Hardy (ehardy) wrote :

While I understand the workflow desires for this, I think it is better to keep the focus of item status on items and not add bib record functionality.

I would prefer that the ability to batch load bib records into a record bucket be developed. See https://bugs.launchpad.net/evergreen/+bug/1784412

Revision history for this message
Terran McCanna (tmccanna) wrote :

I agree with Elaine. Even with appropriate permissions and warning pop-ups, I could see this causing a lot of inadvertent bib record deletions by staff who intended to just delete specific items. I feel that working with items and working with bib records are different enough functions that we shouldn't blur the lines.

Revision history for this message
Mackenzie Johnson (mtjohnsonupei) wrote :

Thank you both for your feedback -- While I'm sure the staff member will be disappointed that this wouldn't be prioritized/implemented save for a sudden and overwhelming outpouring of support and heat (if even that), that is sensible rationale.

Revision history for this message
Michele Morgan (mmorgan) wrote :

Could setting the following two library settings achieve what you want?

- Delete volume with last copy - TRUE
- Retain empty bib records - FALSE

We use these settings in our consortium so that when the last copy on a record is deleted, the bib is deleted also.

Bibliographic records can't be deleted when call numbers(volumes) are still attached, and call numbers can't be deleted with items still attached.

With the library settings set as above, deleting the last item on a call number will delete the call number. If there are no other holdings, the bib record will be deleted also.

Revision history for this message
Elaine Hardy (ehardy) wrote :

PINES has the same settings -- that should have occurred to me! Glad you caught it, Michele.

It is extremely helpful for database integrity to have those settings so that you don't have masses of empty bibs hanging around cluttering searches

Revision history for this message
Mackenzie Johnson (mtjohnsonupei) wrote :

Hypothetically speaking, that could work, except I expect that it would interact poorly with the records that we keep of our ebooks, as we don't create holdings/items for them in EG so they're technically "empty". So alas, I don't think this would work for us.

Revision history for this message
Elaine Hardy (ehardy) wrote :

It is the action of deleting the holdings that causes the bib record to auto delete and not the empty record.

With erecords, since you haven't added the items, you aren't deleting them, so the auto delete bib record doesn't apply.

Just like if you import a record and never add holdings, the record doesn't auto delete unless you have a script to do so. PINES has one that deletes empty bibs for just this reason. It doesn't delete records with located URIs, either

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.