2020-12-08 Metadata meeting notes

5 min

Welcome

15 min

Technical documentation strategy

• Per last TAC meeting, decision to consolidate documentation and rework AS landing page

• Metadata to dos/questions:

  • Transform excel mapping docs to markdown or leave as is? Volunteer to do this?

    • Also, should it wait until 3.0? Agent-related mappings will change, but nothing will change for MARC for resources or spreadsheet importing or exporting. So there will be changed but they will be limited.

    • Import and Export are different, so we have to deal with both separately

    • Side note: Mapping for agents before 3.0 differs from NAF importer right now, but will match in 3.0

    • Suggest splitting everything up and assigning some tags to each individuals. Refer to this for some past work: Import/export mapping review process

    • Using this spreadsheet, let’s start with MARC to ASpace: https://docs.google.com/spreadsheets/d/1jU6MYF7UI7a-UKdd5XhYCV6W1UyrMMCzYDFlgb8iNW8/edit#gid=1527709562

      • Link to where MARCXML to ArchivesSpace Resource converter lives: https://github.com/archivesspace/archivesspace/blob/master/backend/app/converters/lib/marcxml_base_map.rb

      • Homework: Assign ourselves a section or a number of tags and , like 2xx, 5xx (@Valerie Addonizio will take 1xx, 6xx, 7xx for Agents), and just start seeing how possible this is

      • Only going to focus on what the code already does

  • Other metadata documentation that needs to be visible? (for instance, our metadata tiers of support)

    • Like the tiers of support? Agree this would live well on the ASpace.org side and not the GitHub side. To do: Get that on GitHub and get that link to Christine.

    • Nothing other than tiers of support was suggested

15 min

MARC metadata mapping issues

• One outstanding Jira ticket: https://archivesspace.atlassian.net/secure/RapidBoard.jspa?rapidView=15&modal=detail&selectedIssue=ANW-320

  • We are the body who can make these calls. So we can discuss and then post back to the ticket this is what we think and why.

• ERR feedback from Temple / User feedback on MARC mappings; can we guide this process somehow?

  • If there are multiple questions, Christine shared that ideally it should be as granular as possible unless there’s a set that needs to be decided together. Essentially thinking of this from the work side.

    • How to Report a Bug
      How to Request a New Feature

15 min

Mapping development for metadata tiers of support additions

• Schema.org

  • Agree this should be listed in the tiers; don’t need two documents, but add a new context to the existing tiers to say it applies to the SUI or PUI

• Wikidata?

  • Keep our eye on it, feel it’s not stable enough

5 min

Homework check-in

• Research using Github actions to notify TAC-metadata of changes in the code that affect mappings

  • No real update except to say let’s revisit this exact point once we start looking directly at the code as part of new homework

• Addition of JSON API mappings to XML mappings (conversation with API group)

  • No update

5 min

Next steps/homework