Review and discuss feedback from initial testing of new 'Set record for deletion' action for Instances. See notes from DI Lab sessions here: Previous discussion notes:
Expand |
---|
- Ryan has reviewed the spreadsheet of feedback and shared some already with the dev team.
- MODSOURCE-756 : newly submitted ticket
- Folijet is reviewing the ticket and options for addressing it
- Hoping to address with a simple BE update
- In some instances, neither 'suppress' or 'delete' covers all needs.
- Advocation for a separate section in the 'Actions' button for the deletion actions.
- Lots of open questions concerning dependencies (outlined on the spreadsheet). Important for future phases of this project (not part of Phase 1).
- Note : ensure that item status is accounted for in reviewing dependencies ; i.e. items on loan
- Should the default behavior be that the user is expected to delete holdings and items before the instance? i.e. dependencies aren't as important
- Use case could be that holdings and items are marked for deletion separately; last step is to mark instance for deletion and clean all of them out at that point
- Discussion on various internal procedures for withdrawing and deleting records
- Practices in place in FOLIO to address the current inability to delete records leads some libraries to prefer the idea of deleting instances, holdings, and items in one step.
- Practices can vary between libraries based on type of material: physical vs. electronic
- No consensus on when to use a 'hard' vs. 'soft' delete.
- Discussion on ability and need to delete the SRS & Instance separately.
|
|