This feature will continue work started in to enhance usability of the ‘Set record for deletion’ action and other aspects related to deleted Instances.

In Scope:

1.) Add ‘Set for deletion’ indicator field (for mapping & Instance display) & visual marker on Instance-level view in Inventory (Will require update to Instance schema)

• Create new ‘Set for deletion’ flag to display on Instance view

  • When ‘Set for deletion' flag is invoked, an exclamation mark icon should show next to it (similar to ‘Suppressed from discovery’ & ‘Staff suppressed’) on the 3rd pane Instance view

  • When ‘Set for deletion’ flag is invoked, a warning message should display at the top of the 3rd pane Instance view which states “Warning: Instance is set for deletion, suppressed from discovery, and staff suppressed”. (Based on existing behavior for ‘Suppressed from discovery’ & ‘Staff suppressed’)

  • Mockups:

    •  

       

• Create new ‘Set record for deletion’ checkbox to display on Edit Instance view (similar to ‘Suppress from discovery’ & ‘Staff suppress’)

  • Selecting ‘Set record for deletion' checkbox should automatically select & grey-out ‘suppress from discovery’ & ‘staff suppress' checkboxes (i.e. make them uneditable/disabled) if Set for deletion has been checked off. In other words, if ‘Set record for deletion’ is chosen, then the system should ensure that ‘Suppress from discovery’ & 'Staff suppress’ are selected too.

  • If Source=MARC and user checks the ‘set record for deletion field and saves their changes, then the Leader 05 of the underlying SRS should be updated to ‘d’ and deleted set to 'true’

  • If Source=MARC and user un-checks the ‘set record for deletion field and saves their changes, then the Leader 05 of the underlying SRS should be updated to ‘c’ and deleted set to 'false’

  • Mockups:

    •  

       

       

• Update existing ‘Set record for deletion’ action & endpoints to include new ‘Set for deletion’ field

  • If source=FOLIO:

    • Set for deletion flag is set to ‘true’ for the instance (*NEW*)

    • Staff suppressed flag is set to 'true' for the instance

    • Suppress from discovery flag is set to 'true' for instance

  • If source=MARC:

    • Instance updated:

      • Set for deletion flag is set to ‘true’ for the instance (*NEW*)

      • Staff suppressed flag is set to 'true'

      • Suppress from discovery flag is set to 'true'

    • SRS updated:

      • Suppress from discovery flag is set to 'true'

      • deleted set to true

      • Leader 05 is set to "d"

• ECS Note: Same functionality should be applied to Shared Instance (Central tenant) in case of Shared records in ECS.

2.) How to handle ‘Deleted’ bib/instance records being loaded through Data Import

• Proposal: If MARC Bib is loaded through Data Import with Leader 05 set to "d", then all ‘set for deletion’ indicators (see above) should be placed upon resulting Instance and underlying SRS, regardless of how any related fields are mapped for Job profile used.

• Expect same functionality whether Create or Update job.

3.) Update “deleted” markers when Leader 05 is updated via QuickMARC (Spitfire)

• Proposal: If MARC Bib is edited via QuickMARC so that the Leader 05 is set to "d", then all ‘set for deletion’ indicators (see above) should be placed upon resulting Instance and underlying SRS.
  
  

4.) Consider migration to new ‘Set for deletion’ flag for source=MARC Instances

• Idea: For Source=MARC Instances, can a migration script be made to apply ‘set for deletion’ indicators to all Instances with Leader 05 'd' in underlying SRS.

  • Expect to be manually run. Need to consider how long it would take to execute. Info would be need to be pulled from SRS first, and then update appropriate Instances and SRS.

KS note: this can be covered by migration service (), however in such case the whole Instance will be remapped including the new logic for mapping Leader 05 value

5.) Consider options for ‘un-delete’ (stretch goal)

• Idea: For Instances that already have all ‘set for deletion’ indicators applied, can Inventory offer an action to undo the deletion and essentially apply an inverse of the ‘set record for deletion’ action

  • e.g., If a user clicks “Set record as active” action (need to confirm wording), then the below indicators should be updated as follows:

    • If source=FOLIO:

      • Set for deletion flag is set to ‘false’ for the instance (*NEW*)

      • Staff suppressed flag is set to 'false' for the instance

      • Suppress from discovery flag is set to 'false' for instance

    • If source=MARC:

      • Instance updated:

        • Set for deletion flag is set to ‘false’ for the instance (*NEW*)

        • Staff suppressed flag is set to 'false'

        • Suppress from discovery flag is set to 'false'

      • SRS updated:

        • Suppress from discovery flag is set to 'false'

        • deleted set to false

        • Leader 05 is set to "c"

  • Mockups:

    •  

       

    •  

       

      
      
      

Out of scope:

• “HARD” deletes

• Holdings & Items deletion

Additional information:

• Mockups: