2021-06-08 Metadata meeting notes

5 min

Welcome

30 min

MARC to AS mapping doc

https://docs.google.com/spreadsheets/d/1jU6MYF7UI7a-UKdd5XhYCV6W1UyrMMCzYDFlgb8iNW8/edit#gid=1527709562

• Outstanding decisions

  • MARC fields ignored by MARC importer. Do we document these? No. Add note to the top of the spreadsheet warning that fields not in the spreadsheet may not be imported.

  • We had talked about only maintaining certain fields in the MAP. Do we still want to make this decision or push to next term? We will push this to next term with the goal of reducing the total number of fields the importer will support.

• Remaining tickets/issues:

  • ANW-784: MARC import reordering family/corporate creatorsClosed-Will Not Do Push to next term (added to 2021-2022 plan). Issue 784 should be closed and comments should be added to 504.

  • 7xx second indicator ignored. Is this something we care about? MARC 21 Format for Bibliographic Data: 700: Added Entry-Personal Name (Network Development and MARC Standards Office, Library of Congress) This is not an issue as it does not apply to 1xx/7xx

  • 111/611/711: $q missing from import. Just delete from spreadsheet?MARC 21 Format for Bibliographic Data: 111: Main Entry-Meeting Name (Network Development and MARC Standards Office, Library of Congress) There is a need for this field to be handled. Address next term (added to 2021-2022 plan).

  • 300 fields: what should the default behavior be? https://github.com/archivesspace/archivesspace/blob/96aee7faf4c14aab6441aadca2ce2df29fd78681/backend/app/converters/lib/marcxml_bib_base_map.rb#L861 . Address next term (added to 2021-2022 plan). Added note to the spreadsheet that the field is under review by the Metadata Standards Team and users should proceed carefully.

  • 343 ind 7: https://github.com/archivesspace/archivesspace/blob/96aee7faf4c14aab6441aadca2ce2df29fd78681/backend/app/converters/lib/marcxml_bib_base_map.rb#L916 . Address next term → Expect that we will not support (added to 2021-2022 plan). Add note to spreadsheet that the field is under review by the Metadata Standards Subteam and users should proceed carefully.

  • Addition of 099 as an identifier: mapping text: https://docs.google.com/spreadsheets/d/1jU6MYF7UI7a-UKdd5XhYCV6W1UyrMMCzYDFlgb8iNW8/edit#gid=1527709562&range=F25 https://github.com/archivesspace/archivesspace/blob/96aee7faf4c14aab6441aadca2ce2df29fd78681/backend/app/converters/lib/marcxml_bib_base_map.rb#L749 Address next term (added to 2021-2022 plan). Current implementation is potentially misleading.

  • Don’t include $0 in export if there is a $v, $x, $y or $z subdivision. Address next term (added to 2021-2022 plan).

• Publication of the MAP: Create a production level spreadsheet and send to Christine. Add note at top of spreadsheet with revision information.

15 min

Retrospective and chair selection

2020-2021 Metadata Standards retrospective

5 min

Next steps

Thank you for all of your work this term!