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
- Spec for dropping MARC import support:
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.
- Revisit Draft of Tiers of Support as a principles document instead of a statement on scope
- If we get Kevin’s ticket, ANW-1558 - Getting issue details... STATUS we should do an email announcement to the listserv and Google Group
- 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: https://web.archive.org/web/20150324043730/https://www.gliffy.com/publish/2269861/
Use Mermaid for creating the model
- NEW Pilot a Rotating group of ex officio’s from Metadata who sit in on Dev Pri meetings
3. New This Term
- EAD2002 import mapping
- EAC-CPF mapping…
- RiC review…
- 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.
- Did we do this already? – Bring up the retiring of MARC behaviors at the next joint UAC/TAC meeting, which will be in the fall. Elizabeth Roke nominated to handle that communication