Set instance/bib record for deletion
Description
Priority
P2Fix versions
Development Team
Assignee
Solution Architect
Parent Field Value
Parent Status
Attachments
blocks
is continued by
is defined by
is duplicated by
relates to
Checklist
hideTestRail: Results
Activity
Jennifer Eustis April 11, 2024 at 5:47 PM
There is a also a spreadsheet where the community has ongoing comments in particular for ongoing enhancements, . One aspect that is highlighted there is that we need to distinguish an instance that is set for delete versus one that is just suppressed from discovery and staff. One idea is to have a status or another administrative field with DELETE. This would mimic what is happening in the srs marc bib record. it would also facilitate filtering and searching instances set to delete. It could perhaps also facilitate any export of records that are set to delete as data export could check for that status and then add the “d” in the LDR pos 5.
Charlotte Whitt April 11, 2024 at 5:35 PM
- originally it was planned to be able to filter on these records - see: UIIN-1094 Filter instance records by Mark for deletion
Brooks Travis April 11, 2024 at 4:42 PM
How would one perform a search ONLY for records that are marked as deleted? There seems to be a missing piece here (either a system-defined statistical code OR a system-defined instance status type).
Jennifer Eustis January 5, 2024 at 8:41 PM
Thank you for pointing this out. This is fantastic! I'll share with the folks here at the 5C.
Charlotte Whitt December 20, 2023 at 7:05 PM
Hi and - there is already this story for filtering on instances which are marked as deleted:
UIIN-1094 Filter instance records by Mark for deletion
Reporter
Khalilah GambrellPO Rank
Front End Estimate
Front End Estimator
Mariia AloshynaFront-End Confidence factor
Back End Estimate
Back End Estimator
Kateryna Senchenko
Summary
There are several features related to deleting inventory records. This feature relates to applying a platform-wide solution to allow users to set for deletion the following records:
FOLIO instance
corresponding SRS MARC bib record
Feature includes:
Add instance action for marking instances for deletion and staff suppress
Do not pay attention to any dependencies (orders, receiving, holdings, items)
When marked for deletion
Set instance flag for Staff suppress
Set instance flag for Suppress from discovery
If source = MARC, set Leader byte to d
Change search logic so that staff suppressed instances are not shown in normal searches and staff suppress facet is hidden
Adjust existing permission for staff suppress, so that users who have that permission see the facet
Add permission for the new instance action for mark for deletion and suppress
Allow the instance flags to be manually edited by users with permission or by Data Import
Allow the MARC Leader byte to be manually edited by users via quickMARC or by Data Import
Review stories linked to and determine if they are still needed, can be closed as duplicates, can be closed as Won't do, or if that feature needs to be re-described to reflect any remaining work
Feature does not include:
Dependency checks
Pushing instance suppression updates to associated holdings & imports (To be looked at in the future via UIIN-2712)
Actual deletion of instances from inventory-storage
Actual deletion of MARC Bibs from SRS
Any review/automated cleanup of instances that already have one or both flags marked
Any review/automated cleanup of MARC Bibs that already have Leader/05 = d
Dependencies:
Majority of work will be owned by Folijet, but the following support stories will be owned by Spitfire:
UIIN-2596 Inventory - Staff suppress facet - default settings
UIPFI-133 Find Instance Plugin - Staff suppress facet - default settings
Developer notes
Keep the dev work as UI-oriented as possible; minimize the BE work