search

sul-dlss / FOLIO-Project-Stanford

Task management for Stanford’s analysis of FOLIO.
2 stars 0 forks source link

How should overlaying a MARC field work? #668

Open shelleydoljack opened 2 weeks ago

shelleydoljack commented 2 weeks ago

When we want to add a tag to a MARC record, should we account for possible existing tags in the MARC record that should be overlaid? An example use case is for a retrospective update to 979 fields in our existing records. The title for the bookplate fund_name ABBOTT was "The The Donald P. Abbott Fund for Marine Invertebrates" and the typo was corrected so it is now "The Donald P. Abbott Fund for Marine Invertebrates". When we add 979 fields to MARC records, should we use specific subfields to determine if the field should be added or overlaid? For bookplates, we could compare the 979 subfields f and b to determine what the incoming field data should overwrite the existing field data (so delete existing 979 that matches on subfields f and b and add new 979). 

{'979': {'ind1': ' ', 'ind2': ' ', 'subfields': [{'f': 'ABBOTT'}, {'b': 'druid:ws066yy0421'}, {'c': 'ws066yy0421_00_0001.jp2'}, {'d': 'The The Donald P. Abbott Fund for Marine Invertebrates'}]}}

Should we have a separate function for overlaying fields? Or do we create a delete a field function that can be used separately and in conjunction with adding a field?

shelleydoljack commented 2 weeks ago

In the requirements document, we have a requirement to not duplicate existing information when adding a 979 tag, so it seems like we should overlay or delete existing fields before adding one.