(post go-live) batch deleting bibliographic records in the NZ

Legend: not started IN PROGRESS STALLED decided

Recommendation

Campuses will add a 902 note to any NZ record that can be deleted

CDL will gather a set of records with this 902 note and filter out any records with a 910 indicating that the record has other related records (most commonly bound-withs).

CDL will run the delete job against this filtered set and will not delete any records that still have inventory attached.

Reasoning

This process is the safest way to ensure that records aren’t deleted accidentally by either campus staff or CDL. Adding the 902 note also serves as an indication to other campus staff that the record has already been reported for deletion.

Background

RMFG reviewed documentation from other consortia and a consistent issue was the way the NZ views inventory for bound-withs and other “related records.” Within an IZ, the delete job is able to view inventory that is associated with a “related record” and will prevent the record from being deleted. At the NZ level, however, that isn’t possible. After signfiicant sandbox testing, RMFG and CDL determined that even when the options to retain “related records” were selected, the NZ delete job will delete bibliographic records that lack inventory, even if they are connected to another record in the system.

RMFG has created processes for labeling bound-with and other related records in the NZ: https://uc-sils.atlassian.net/wiki/spaces/RMF/pages/1782480901

Dependencies

How to ensure that bound-withs and other records that appear in the NZ to lack inventory but are related to other records do not get deleted accidentally

Questions to consider

Action Log