2019-2010 Work Plan Tasks and Goal
...
Task | Notes | Timeline/Assignment |
---|---|---|
Tier definitions | 1st tier: ArchivesSpace strives for an optimal support of standard. For structural standards, import and export. (NB This is not 2nd tier: ArchivesSpace strives for compliant support. For structural standards, export. | Agreed, 10/17/19; can be revisited as we work through mappings |
Determine what belongs in which tier | 1st tier: EAD2002, MARC, and DACS 2nd tier: Dublin Core, EAD3, EAC-CPF (to be re-evaluated once Agent module work is done), OAI-PMH | Agreed, 10/17/19; can be revisited as we work through mappings |
Support for Emerging Standards | Monitoring standards changes, and commenting on behalf of AS community as warranted, e.g. RiC | As needed |
2. Maintaining published metadata mappings
...
Task | Notes | Timeline/Assignment |
---|---|---|
List existing mappings |
| |
Which mapping to update / who / how | 1. Getting some sample imports and exports in a workspace 2. Set up some sort of process to document checks. 3. Dividing up elements to check 4. Check fields that can be easily checked a. We should be able to check a lot of the exports in sandbox.archivesspace.org 5. Isolating import fields that are more challenging to check a. (I’m thinking some of the more long tail things, with <colspec> or odd <fontmatter> elements to check how that imports) b. I did not know that <ptrloc> was a thing, for example (https://www.loc.gov/ead/tglib/elements/ptrloc.html) 6. Finding/creating records to test with long-tail elements | |
Ensuring that code changes impacting metadata mappings are communicated would be a great contribution | Instructions to community members in how to create JIRA tickets for review Questions/Comments
| |
...