Page History

...

• 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 - Brooks Travis   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   

...