Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

2019-2010 Work Plan Tasks and Goal

  1. Defining our level of commitment to various standards
TaskNotesTimeline/Assignment

First tier of compliance and documentation: EAD2002, MARC,DACS



Next tier: Dublin Core, EAD3, EAC-CPF (?), OAI-PMH

Q: What does this mean in practice? E.g., 1st tier is import and export; 2nd tier only export, or we might just offer the mapping


Support for Emerging StandardsMonitoring standards changes, and commenting on behalf of AS community as warranted, e.g. RiC


2. Maintaining published metadata mappings

(this will need to be broken down into tasks, and we will need to ensure that we clearly define our level of commitment)

TaskNotesTimeline/Assignment

List existing mappings

  • Accession CSV Import
  • Digital Object CSV Import
  • Digital Objects MODS Export
  • Digital Objects METS Export
  • Digital Objects DC Export
  • EAD 2002 Import
  • EAD 2002 Export
  • EAD3 Export
  • MARCXML Import (Q: Are resource, accession, agent imports mapped differently?)
  • MARCXML Export
  • OAI-PMH MODS
  • OAI-PMH DC
  • OAI-PMH DCTerms

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


  • How DACS integration is supported and how tooltips are in sync




3. Reviewing metadata-related dev. tickets and to what extent a request to improve a feature will be rewarding to the community



4. Offer a mechanism to provide feedback


Ideas and Tasks For the Future

  • No labels