|
Current situation or problem:
Holdings records need to be deleted manually one by one as there is no mechanism to delete a group of records that can be identified either by a submitted list of identifiers or by a simple query.
In scope:
- Identify records for the deletion by submitting a list of identifiers.
- Identify records for the deletion by submitting a query
- Preview the records that will be deleted. The preview can be exported in the .csv format
- Errors encountered while identifying records are reported and can be exported in the .csv format. The log contains information about affected record (identifier) and the short description of the encountered problem
- Before the records are deleted, the user will have a chance to review them again before committing.
- Once committed records without outstanding dependencies are removed from the system (hard delete) and user is notified about the number of deleted records
- Records that cannot be removed due to the existing dependencies are reported in the error log. The log contains information about affected record (identifier) and short description. The list can be exported in the .csv format
- All other errors encountered during the deletion are reported with the list of record identifiers and description of the problem. The list of errors can be exported and the .csv format
- Bulk delete of holdings records requires a separate permission that is independent of the other bulk edit permissions and holdings delete permissions granted for the deletion of a single record.
- Accessing matching record files, preview files and error messages through Bulk edit logs
Use cases: https://folio-org.atlassian.net/wiki/display/BULKEDIT/Bulk+Edit+Use+Cases
Mockups:
TBD
|