Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

2019-2010 Work Plan Tasks and Goal

...

TaskNotesTimeline/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

...

TaskNotesTimeline/Assignment

List existing mappings (in rough priority order)

  • EAD 2002 Export
  • EAD 2002 Import
  • EAD3 Export
  • MARCXML Import
    • (Q: Are resource, accession, agent imports mapped differently?)
  • MARCXML Export
  • Accession CSV Import
  • Digital Object CSV Import
  • EAC-CPF export
  • Digital Objects MODS Export
  • Digital Objects METS Export
  • Digital Objects DC Export
  • OAI-PMH MODS
  • OAI-PMH DC
  • OAI-PMH DCTerms
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

  • Is there any point of intersection with labors of the Development Prioritization subteam?  Specifically the development roadmap? 




...