Main Goals
...
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
...
- NEW Pilot a Rotating group of ex officio’s from Metadata who sit in on Dev Pri meetings
- Revisit Draft of Tiers of Support as a principles document instead of a statement on scope
...
- 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.
...