Versions Compared

Key

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

2019-2010 Work Plan Tasks and Goal

...

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
  • EAC-CPF export

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

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





3. How DACS integration is supported and how tooltips are in sync

TaskNotesTimeline/Assignment
Review existing tooltips for DACS compliance
To be reviewed at Nov meeting
Look at new DACS fields or suggestions

Jira Legacy
serverSystem JIRA
serverId36c489e2-4fb0-353a-985b-64038401be2f
keyANW-883

Ticket about new DACS rights field?


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

A new label for metadata-standards-related tickets has been created: https://archivesspace.atlassian.net/browse/ANW-918?jql=labels%20%3D%20metadata%20order%20by%20created%20DESC

→ To be a standing agenda item; 10 min of every monthly call for review, discussion, and if necessary a volunteer to draft a comment

4. Offer a mechanism to provide feedback

...