Batch Importer (Bib/Acq) (UXPROD-47)

[UXPROD-3092] Corresponding Data Import & SRS MARC Bib work required for Instance "Mark for deletion" - DRAFT Created: 27/May/21  Updated: 28/Dec/23

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: TBD
Parent: Batch Importer (Bib/Acq)

Type: New Feature Priority: P3
Reporter: Ann-Marie Breaux (Inactive) Assignee: Ryan Taylor
Resolution: Unresolved Votes: 0
Labels: cataloging, data-import, delete_record_functionality, epam-folijet, needs-be-estimate, needs-ui-estimate
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Gantt End to End
has to be finished together with UXPROD-3621 Spec and planning. Inventory. Mark in... Closed
has to be finished together with UXPROD-3742 Mark instance for deletion. 2nd itera... In Refinement
Relates
relates to UXPROD-3702 Enabler : Marking an instance record ... Open
relates to UXPROD-1624 Deletion. Implement action menu in to... Blocked
relates to UXPROD-4024 Bulk delete SRS Bib records Open
relates to UXPROD-2350 Support for the Delete action during ... Draft
Release: Not Scheduled
Epic Link: Batch Importer (Bib/Acq)
Development Team: Folijet
PO Rank: 91
Rank: Cornell (Full Sum 2021): R3
Rank: GBV (MVP Sum 2020): R5

 Description   

Very rough - very preliminary

In UXPROD-3621 Closed , Inventory will add functionality to mark Instances for deletion. Several things still need to be decided:

  • Via an action menu option?
  • Displayed as a checked checkbox, but not editable on the Instance?
  • If marked, does that suppress the instance from regular search results?
  • Are any dependency checks done at the point the Instance is marked for deletion, or not until some future point, when the system actually starts deleting instances
  • Figure out how existing Instances will be handled (required or optional field)

For source = MARC instances, Folijet will need to accomplish some or all of this work in the same release as UXPROD-3621 Closed . Some may be delayed until a future feature for "hard" deletes, but still TBD

  • Allow the user to set this in the Instance field mapping profile, like the other checkboxes at the top of the Instance?
  • Add as a new data element in the Instance schema?
  • When set in the Instance, should that flow over to SRS, like Suppress from discovery?
  • Does SRS need to add as an additional element in the SRS MARC Bib schema, like Suppress from discovery?
  • If added as a new data element, should SRS also set the MARC Leader position 5, as per best practices for OAI-PMH? Per Magda Zacharska, most helpful for OAI-PMH if SRS
    • Adds a field that stays in sync with the Instance Mark for deletion flag (parallel to the Suppress from Discovery flag) AND
    • Sets the MARC Leader byte 5 to "d" if the Instance is Marked for deletion
  • Can a user set/unset the mark for deletion flag by doing an import?
    • If yes, might need to add Field mapping logic that
      • If flag is set, the other 2 suppress flags are set
      • If flag is unset, the other 2 suppress flags are NOT unset
    • Like export a batch of records, and then re-import them just to change the flag?
    • And then when it has been marked in Inventory, the flag flows back to SRS MARC and changes the Leader byte 5
  • How does this relate to the DI Delete action, which we have not yet implemented? Should we hide it?
  • If DI is blocked from affecting these records, that is significant scope
  • Can some of this wait until the Instance soft deletes become Hard deletes?
    • When hard deletes, do we delete all versions of the SRS MARC? What would that do to logs?

SME Slack channel (open): https://folio-project.slack.com/archives/C03KPLWJBLM
Dev/PO Slack channel (private): https://folio-project.slack.com/archives/C03LB2VGRRU



 Comments   
Comment by Charlotte Whitt [ 29/Jun/22 ]

Ann-Marie Breaux - Marked for deletion should be marked not just in Instance source = FOLIO but also in Instance source = MARC. We should avoid having a situation where the source of truth is not marked for deletion, when the display in inventory is marked for deletion. Inconsistency here can cause serious confusion and potential data corruption.

In the notes to the slide deck Magda Zacharska suggest that if the instance has source set to MARC, and is marked as deleted, then the LDR 05 of the underlying record should be set to "d".

When checking https://loc.gov/marc/bibliographic/bdleader.html the LDR 05 d then that means deleted (and not marked for deletion). But I differ to you to define the correct value.

Comment by Ann-Marie Breaux (Inactive) [ 13/Sep/22 ]

Moving prep to Orchid, for development in Poppy

Comment by Ann-Marie Breaux (Inactive) [ 06/Dec/23 ]

Ryan Taylor This is a Folijet feature from when Prokopovych was going to do the work for marking instances for deletion. Please review when you have a chance, and see if there's any of the description that we would want to move into the Folijet Quesnelia feature. If there's any that doesn't fit, let's talk about whether it's needed or not. Once that's done, we can probably delete this feature. Thank you!

Generated at Fri Feb 09 00:29:17 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.