during testing of the Inventory migration for Nolana, we're seeing an error when trying to POST instance records due to (I believe) a specific mapping for certain fields in the marc-bib map. For the Main Entries (100, 110, 111) and Added Entry (700, 710, 711) Fields, there is a mapping for the contributor.authorityId field that pulls from the subfield 9:
{'target': 'contributors.authorityId',
'subfield': ['9'],
'description': 'Authority ID that controlling the contributor',
'applyRulesOnConcatenatedData': True}
We don't have a subfield 9 in these fields (and I wasn't able to find any documentation on this subfield at either https://www.loc.gov/marc/bibliographic/bd100.html or https://www.oclc.org/bibformats/en/1xx/100.html) so an empty string is being added to the Instance JSON causing an error when trying to do a POST to okapi.
Can/should we remove this particular mapping for now and revisit when we start migrating Authorities? Or another option would be remove the authorityId property from the JSON record as a step in the DAG.
Mapping was updated to revert to earlier versions of the 1xx and 7xx mapping to keep data migration moving but we still need to figure out why this was happening. We will need to leverage the authority related mappings at some point.
ahafele
commented
1 year ago
Slack conversation here - https://stanfordlib.slack.com/archives/C02CWRMBMT8/p1674503629968039
Per Jeremy -
Mapping was updated to revert to earlier versions of the 1xx and 7xx mapping to keep data migration moving but we still need to figure out why this was happening. We will need to leverage the authority related mappings at some point.
Epic for linking auth with bib - https://issues.folio.org/browse/UXPROD-2965 Potentially relevant ticket - https://issues.folio.org/browse/MODDICORE-281
Further info on auth functionality https://wiki.folio.org/display/FOLIJET/Linking+Bib+field+to+Authority+1XX#LinkingBibfieldtoAuthority1XX-$9Requirements https://wiki.folio.org/display/FOLIJET/Authority+control+development