2021-2022 Metadata Sub-team Work Plan

Owned by Valerie Addonizio
Last updated: Jun 16, 2022
2 min read

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

  • continue to develop pro-active processes to track code changes that affect metadata mappings

Themes

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

  • Theme 2: 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.

  • Theme 3: 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.

Specific Tasks

Ongoing ticket review as needed
Recommend and provide feedback on a workflow that alerts the Metadata Sub-Team to relevant tickets as they are submitted and reviewed
Retroactive review of the MARC importer to pull unsupported behavior @Elizabeth Roke as lead, with input from group
An extent review for the MARC importer concerning particular tickets (note that these tickets are fluid and still changing status at this time)

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

https://archivesspace.atlassian.net/browse/ANW-1174 → Note that this has moved on since we last looked at it.

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 the remaining issues from last term (2021-06-08 minutes)
343 ind 7: Expect @Elizabeth Roke will cover this in her review of supported behaviors. Support for this MARC field is being retracted, so this action item is moot (complete).
Addition of 099 as an identifier: mapping text: Current implementation is potentially misleading.
Issue 784 should be closed and comments should be added to 504.
Publish Tiers of Support@Valerie Addonizio

  • Additional discussion made this goal moot, but all that discussion did lead to conclusions and clarity, so the goal, while not complete, was useful in TAC-MD’s work this term

Begin review process for the EAD 2002 importer. Spreadsheet: Code: Note: There is no EAD3 importer at this time.
Gather ideas and themes to present at the next AS Online Forum
Create a holding pen for ideas @Valerie Addonizio
Select ideas
Present!

Not doing this term

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

  • Not recommending RiC mapping at this time

  • Don’t include $0 in export if there is a $v, $x, $y or $z subdivision