Versions Compared

Old Version 1

changes.mady.by.user Valerie Addonizio

Saved on

compared with

New Version 2

changes.mady.by.user Valerie Addonizio

Saved on

Key

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

This version copied from last term, currently under revision, to be discussed in the 2021-2022 term.

Main goals:

  • support user communities, especially those without back end access or deep technical expertise

  • track changes in related standards and ensure those changes are reflected in ArchivesSpace mappings

  • support developers of ArchivesSpace on metadata issues, particularly through Jira ticket review

  • develop processes to track code changes that affect metadata mappings and automatically update documentation

Specific tasks:

  •  Develop a plan to make ArchivesSpace metadata documentation more discoverable
  •  Reach out to ArchivesSpace developers to brainstorm about automating metadata documentation
  •  Update the list of prioritized mapping standards
  •  Track the upcoming release of ArchivesSpace 3.0 and create new documentation/mappings if necessary, especially for agent metadata
  • Recommend and provide feedback on a workflow that alerts the Metadata Sub-Team to relevant tickets as they are submitted and reviewed (Goal: More proactive before-the-fact review than reactive catch-up when relevant mappings are touched by Devs)
  •  An extent review for the MARC importer concerning two particular tickets

https://archivesspace.atlassian.net/browse/ANW-1260

https://archivesspace.atlassian.net/browse/ANW-1174

300 fields: What should the default behavior be? https://github.com/archivesspace/archivesspace/blob/96aee7faf4c14aab6441aadca2ce2df29fd78681/backend/app/converters/lib/marcxml_bib_base_map.rb#L861

  •  Address outstanding issues from last term documented here
  •  Review the EAD 2002 import mappings, update, and publish to the web

Goals and Themes

  • More proactive before-the-fact review than reactive catch-up when relevant mappings are touched by Devs.

  • Decisive decision making on what is and is not supported by ArchivesSpace import mappings ; pulling behaviors deemed out of scope out of the mappings ; being explicit that these behaviors are not in scope.

  • Solicit direct community feedback on some tickets relevant to Metadata Standards, but with special attention the balance of not supporting edge cases weighed against the realities of smaller institutions with few resources and options.

Not doing:

  •  Determine if new mapping documentation is needed for EAC-CPF