Mark for Deletion - Detecting and Resolving Conflicts Requirements

Requirements

• Define requirements for behavior in Inventory - responsible Charlotte Whitt  
  
  • Use cases 

1. 1. 1. A title has been withdrawn and should be completely removed from the catalog; before it can be deleted, information from the record needs to be communicated to external services (e.g. discovery, WorldCat)
      2. Duplicate records were created for a title; one needs to be deleted, but before that can happen someone needs to update information in orders
      3. Staff members in collection management are working on a weeding project; they need to be able to set the deletion process in motion, but they should not have permissions for full deletion (it’s common for many staff not to have deletion permissions)

• • Features:
    • UXPROD-3621 1st iteration
    • UXPROD-3742 2nd iteration
  • Via FOLIO user interface
  • Via backend system/service/process
• Define requirements for resolving solution in mod-search - responsible Mikhail Fokanov   
  • Use cases:

1. 1. 1. Inventory - default search result must exclude instances being marked for deletion
      2. Instance look up component - default search result must exclude instances being marked for deletion

• • Story: MSEARCH-386
  • Via FOLIO user interface
  • Via backend system/service/process
• Define requirements for resolving dependencies with MARC records in Source Record Storage - responsible Ann-Marie Breaux (Deactivated)  
  • Use cases
  • Feature: UXPROD-3092
  • Via FOLIO user interface
  • Via backend system/service/process
• Define requirements for resolving dependencies with quickMARC - responsible Khalilah Gambrell 
  • Use cases
  • Feature:
  • Via FOLIO user interface
  • Via backend system/service/process 
• Define requirements for resolving dependencies with MARC Authorities - responsible Khalilah Gambrell
  • • NOT relevant until we get to have linking between authority data headings and bibliographic records
  • Use cases
  • Feature:
  • Via FOLIO user interface
  • Via backend system/service/process 

• Define requirements for resolving dependencies with Data Export - responsible Magda Zacharska  
  • • NOT relevant for the existing implementation of data export
  • Use cases
  • Feature:
  • Via FOLIO user interface
  • Via backend system/service/process
• Define requirements for resolving dependencies with Export Manager- responsible Magda Zacharska  
  • • NOT relevant for Export Manager assuming that the dependencies for Circulation logs and acquisition data is handled correctly 
  • Feature:
  • Via FOLIO user interface
  • Via backend system/service/process
• Define requirements for resolving dependencies with Bulk edit - responsible Magda Zacharska  
  • Instances bulk delete is not currently implemented and is not planned for several releases.  However, if the Mark for deletion will ignore dependencies then Bulk edit will need to revisit this functionality again as the volume of the removed data will exacerbate the problem of orphaned records.

• Define requirements for resolving dependencies with OAI-PMH - Magda Zacharska 
  • OAI-PMH impact will depend on the selected approach:  
  • Approach 1:  instances marked for deletion  have source=FOLIO - no impact on the current implementation of OAI-PMH.
  • Approach 2:  instances marked for deletion  have source=MARC and underlying  SRS record has LDR05 set to "d" - no impact on the current implementation of OAI-PMH
  • Approach 3:  instances marked for deletion  have source=MARC and underlying  SRS record has additional flag added but LDR05 is not changed
    • If instances marked for deletion need to be suppressed from discovery:
      • Additional logic will need to be implemented on OAI-PMH side to handle the new flag.  
  • Feature:  Will depend on selected approach
  • Via FOLIO user interface
  • Via backend system/service/process 
• Define requirements for resolving dependencies with Z39.50 - Charlotte Whitt 
  • • NOT relevant when choosing the solution that all records being Marked for deletion will automatically be marked both Suppressed from discovery and Staff suppressed
  • Use cases
  • Feature: -
  • Via FOLIO user interface
  • Via backend system/service/process 
• Define requirements for resolving dependencies for OPAC/Discover - Charlotte Whitt for VuFind, ?? for EBSCO (EDS) solutions
  • Use cases
  • Feature:
  • Via FOLIO user interface
  • Via backend system/service/process 
• Define requirements for resolving dependencies for edge-rtac/edge-patron - Khalilah Gambrell  
  • Use cases
  • Feature:
  • Via FOLIO user interface
  • Via backend system/service/process 
• Define requirements for resolving dependencies with Z39.50 - Charlotte Whitt 
  • Use cases
  • Feature:
  • Via FOLIO user interface
  • Via backend system/service/process 
• Define requirements for resolving dependencies with Request - Currently no Product owner  
  • Use cases
  • Feature:
  • Via FOLIO user interface
  • Via backend system/service/process 
• Define requirements for resolving dependencies with INN-Reach - Brooks Travis  
  • Use cases
  • Feature:
  • Via FOLIO user interface
  • Via backend system/service/process 
• Define requirements for resolving dependencies with SIP2 - Brooks Travis  
  • Use cases
  • Feature:
  • Via FOLIO user interface
  • Via backend system/service/process 
• Define requirements for resolving dependencies with Acquisition - Dennis Bridges   
  • Use cases
    • Is there any circumstance when a user would want a newly created order to match and be connected to an instance that is marked for deletion? If not then a new instance would be created in this situation.
    • Is there any use case for making users aware that an existing order is currently connected to an instance that is marked for deletion?
  • Via FOLIO user interface
  • Via backend system/service/process
• Define requirements for resolving dependencies with Circulation log - Stephanie Buck   

IF an instance record marked for deletion cannot have any item records attached, there is no impact on Circulation log

• • Use cases
    • Viewing and/or exporting circulation actions tied to an item barcode
  • Consideration
    • Item barcodes in the circulation log are active whether an item record has been deleted or not
  • Via FOLIO user interface
  • Via backend system/service/process

Architectural Requirements for the SA 

• Define permission solution - responsible Raman Auramau  
  • The App Interaction SIG has begun spec of the use of field based permissions. This work is still in a very early phase. 
    • Meeting minutes from the App Interactions discussion of field based perms: 2022-05-09 Meeting notes: Field based permissions.
  • Marc Johnson has suggested that the chosen design is by it’s very nature an example of a field level permission, in that the ability to alter the marked for deletion field is controlled by permissions separate to those which control access to the record.
• Define robust dependency check across apps; - responsible Raman Auramau
  • This should both support Mark for deletion, and also support the coming work when we must be able to handle the actual deletion of instances
  • Deletion of instance can either be performed by a human action or an automatically job 

Use cases - Must test to validate functionality (wip)   

Documentation:

Slide deck presented for MM-SIG: 6/30/2022 (updated)

Slide deck presented for POs and developers: 7/8/2022

Related Features 

Jira feature for Inventory implementation in Nolana: 

Road map: ROAD-125 - Getting issue details... STATUS

Prokopovych: UXPROD-3621 - Getting issue details... STATUS

Foljiet: UXPROD-3092 - Getting issue details... STATUS

Spitfire: UXPROD-3702 - Getting issue details... STATUS

Vega: ?

Other: ?

Draft/blocked awaiting until Mark for deletion work is implemented, and we start on Instance deletion:

Prokopovych: UXPROD-1624 - Getting issue details... STATUS

Foljiet: MODSOURMAN-292 - Getting issue details... STATUS

Firebird: MODOAIPMH-268 - Getting issue details... STATUS