Update SRS MARC Authority records via Data Import

Add link for the Jira Feature

• Ann-Marie Breaux (Deactivated)and Khalilah Gambrell
• Then review with Data Import subgroup 8 Dec 2021 
• Likely that Spitfire will do the development work during Lotus dev

Developer research spike details 

Problem(s):

• Existing Data Import UI and logic mainly focuses on updating MARC Bibliographic records during Data Import. Review all UI screens and logic to determine what adjustments are needed for updating MARC Authority records via Data Import

UI Screens to review

• Settings
  • Job profiles
    • No changes needed
  • Match profiles
    • What match parameters are needed?
      • 010 $a to 010 $a (to do)
      • 001 to 001 (already in place, but see note below about slashes and spaces; test numeric only matching?)
      • 999 ff $s to 999 ff $s (already in place, but probably won't be used as much as 010)
    • Notes about matching
      • Leeda: Authority vendor (Marcive) sends 2 files: Bib records, and then Authority records in a separate file; LCNA is in 010 and 001; Authority file is a mix of updated authority records, plus records that would be new to Duke's catalog; also get a separate delete file 4x/year   
      • Jennifer E: match: 001 to 001; also have a label in bib record's 928 field, flagging records that need to be sent out for authority work; not currently loading authority, but planning to in the future
      • Autumn (Mich State): match on 010, using Backstage for authority work; used a 9xx field to mark Bibs that need to go out for processing; MARC Auth file is a mix of Adds and Updates; not sure if separate delete file or just reports of which records need to be deleted
      • 001 to 001
        • Marcive includes slashes where spaces
      • 010 to 010
        • for 010, only match on $a? For now, yes; revisit if use case identified for matching on $z
        • spaces between prefix and number; just match on number?, e.g. 001  sh\97006185\, vs 010 showing hard spaces
      • 001 to 010 or 010 to 001: would fail, due to the difference in how spaces and subfields are handled in the two fields
      • 999 ff $s to 999 ff $s - would not really be helpful since external vendor doesn't know about internal library numbers
      • Any others? 010? (spaces between prefix and number; just match on number?), e.g. 001  sh\97006185\, vs 010 showing hard spaces
        
      • Note that MARC-MARC only matches on 001 and 999 ff right now

Old Backstage record (courtesy of Mark A.): 

=LDR  00809cz   2200241n  4500
=001  n\\91103388\
=003  DLC
=005  20191130073201.0
=008  911010n|\azannaabn\\\\\\\\\\|a\aaa\\\\\\
=100  1\$aNolen, Jerdine
=400  1\$aNolen-Harold, Jerdine
=400  1\$aHarold, Jerdine Nolen-
=370  \\$cUnited States$2naf
=372  \\$aChildren's literature$2lcsh
=374  \\$aAfrican American women authors$2lcsh
=375  \\$afemale
=377  \\$aeng
=670  \\$aHer Harvey Potter's balloon farm, 1993:$bCIP t.p. (Jerdine Nolen Harold) bk. t.p. (Jerdine Nolen)
=670  \\$aMomma's kitchen, 1994:$bCIP t.p. (Jerdine Nolen) data sheet (Nolen-Harold, Jerdine)
=010  \\$an  91103388
=035  \\$a(OCoLC)oca03038353
=040  \\$aDLC$beng$erda$cDLC$dDLC$dIAhCCS$dOCoLC$dMnMN$dICrlF$dNN
=053  \0$aPS3564.O396

• • • Incoming records:
      • Enable MARC Authority
    • Existing records:
      • Enable MARC Authority, remove FOLIO Authority
  • Action profiles
    • Enable MARC Authority
    • Remove Authority, since it will always be implicit when MARC Authority selected
  • Field mapping profiles
    • Remove Authority (For Lotus, no non-MARC fields in the FOLIO Authority record)
    • MARC Authority
      • MARC Modification: not needed for v1
        • Lisa R/Raegan: made local mods once, but wuld be very rare
        • Leeda: make a modification to MeSH auth records to manipulate the NLM number to copy from 001 to 016; workaround: ask vendor to change or update in MARCedit
      • MARC Updates
        • Center section of the headers fill in based on the type of MARC record selected above 
        • Would you ever need to update specific fields instead of all fields? No use case identified yet
        • No need for protected fields in authority records; leave out unless use case identified
        • Maybe keep 644, 645, 646 for series analysis decisions; maybe set all as checked, and then library unchecks the $5 protection?
        • Use the same field protections and overrides as MARC Bibs? Would be best for v.1. Any reason for the protections to be different for MARC Authorities? 
  • File extensions
    • Any additional default file extensions needed? No
  • MARC field protection
    • Any adds/edits to the text? PNo
• Data Import
  • Landing page - no changes
  • Choose jobs page - no changes
  • Log view all page - no changes
  • Individual job log summary page
    • Additional Authority column not needed
    • Review the header for the Title column: change to something else? maybe Heading?
    • When click title, opens the tab and shows MARC JSON 
    • When click Authority Created/Updated, will not be a separate link to the Authority app record (different from Inventory and Invoices)
    • Maybe MARC column's Created/Updated is a hotlink to the MARC Authority app view of the record?
  • Log JSON detail page for MARC Authority
    • 999 ff $i will need to be added (999 ff $s already exists)
    • Separate tab for Authority is not needed
• Anything for Inventory, Authority, or quickMARC app UIs?

Use Cases & Requirements:

Links 

SME Questions:

Basic workflow

What Backend stories are needed?

What UI stories are needed?

Developer Questions: