2019-2010 Work Plan Tasks and Goal
...
Task | Notes | Timeline/Assignment |
---|---|---|
List existing mappings (in rough priority order) |
| Done |
Getting some sample imports and exports | Kevin - MARC (for November) Jared - EAD (for November) | |
Find workspace to store records | ||
Determine test process for import | 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 | |
Determine test process for export | Create a sample record (records?) with every field filled out, with the content being the fields name. Make sure we cover expected cases (dates, extents) that might need multiples of repeated fields. | |
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
| |
...
Task | Notes | Timeline/Assignment | ||||||||
---|---|---|---|---|---|---|---|---|---|---|
Review existing tooltips for DACS compliance | To be reviewed at Nov meeting | |||||||||
Look at new DACS fields or suggestions |
Ticket about new DACS rights field? |
34. Reviewing metadata-related dev. tickets and to what extent a request to improve a feature will be rewarding to the community
...
→ To be a standing agenda item; 10 min of every monthly call for review, discussion, and if necessary a volunteer to draft a comment
45. Offer a mechanism to provide feedback
...