2022-2023 Metadata Sub-team Work Plan

Owned by Regine Heberlein
Last updated: Jun 12, 2023
2 min read

Main Goals

  • support user communities, especially those without back end access or deep technical expertise

  • track changes in related standards and ensure those changes are reflected in ArchivesSpace mappings

  • support developers of ArchivesSpace on metadata issues, particularly through Jira ticket review

  • continue to develop pro-active processes to track code changes that affect metadata mappings

Specific Tasks

1. Ongoing Tasks

Ongoing ticket review as needed

2. In-Progress Tasks from Last Term

If we get Kevin’s ticket, ANW-1558: Importer reportingReady for Implementation we should do an email announcement to the listserv and Google Group
Spec for dropping MARC import support (depends on ANW-1588):

Pull all the non-core fields (2xx, 3xx, 754, 856) except the 5xx’s; for the 5xx’s, everything that is a core field gets mapped, but everything that is a 5xx just gets a mapping to a local note, like a 590. We know this a relatively big change, maybe put this in the roadmap, so that it doesn’t happen quietly. Elizabeth volunteers to write that spec, including the justification. You’ll get a list of what was imported.

ad hoc taskforce to update the ASpace data model

Google doc: https://docs.google.com/document/d/1-4E1BYAGT-GCAWLZaWwtsPgeGJqnt6y04e6r82EYxCY/edit?usp=sharing

Old (pre-container and location modeling) entity relationship model archived in the Wayback Machine: Gliffy Public Diagram - ASpace ERD

Suggestion: use Mermaid for creating the model

(syntax: Mermaid | Diagramming and charting tool

editor: Online FlowChart & Diagrams Editor - Mermaid Live Editor )

NEW Pilot a Rotating group of ex officio’s from Metadata who sit in on Dev Pri meetings

3. New This Term

Test current import behavior node by node, starting with DACS elements. Map to related standards. This will be the main focus of this term and is expected to extend well beyond this term.

EAC-CPF mapping: solicit community feedback; take further action as time allows
Discuss retiring of MARC behaviors at the fall 2022 joint UAC/TAC meeting. @Elizabeth Roke nominated to handle that communication
Don’t include $0 in export if there is a $v, $x, $y or $z subdivision (this is from last term’s “not this term” list)
Recommend and provide feedback on a workflow that alerts the Metadata Sub-Team to relevant tickets as they are submitted and reviewed
Invite Brian Hoffman (ASpace Dev) to present on the EAD importer. Key to this would be preparing a few concrete questions or asking for a demonstration of how he himself would fill out the spreadsheet. Early efforts to de-mystify the code would benefit the whole group.