2021-2022 Metadata Sub-team Work Plan
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
ANW-1174: MARC XML import shows linear feet as "1" regardless of actual extent in 300 $aClosed-Complete → 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
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
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