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
...
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)
- 111/611/711: $q missing from import as a ticket → Valerie Addonizio will submit a ticket.
- Don’t include $0 in export if there is a $v, $x, $y or $z subdivision→ Valerie Addonizio will submit a ticket.
- 343 ind 7: https://github.com/archivesspace/archivesspace/blob/96aee7faf4c14aab6441aadca2ce2df29fd78681/backend/app/converters/lib/marcxml_bib_base_map.rb#L916 Expect Elizabeth Roke will cover this in her review of supported behaviors.
- Addition of 099 as an identifier: mapping text: https://docs.google.com/spreadsheets/d/1jU6MYF7UI7a-UKdd5XhYCV6W1UyrMMCzYDFlgb8iNW8/edit#gid=1527709562&range=F25https://github.com/archivesspace/archivesspace/blob/96aee7faf4c14aab6441aadca2ce2df29fd78681/backend/app/converters/lib/marcxml_bib_base_map.rb#L749
- https://archivesspace.atlassian.net/browse/ANW-784 Issue 784 should be closed and comments should be added to 504.
- Ongoing ticket review as needed
- Begin review process for the EAD 2002 importer. Spreadsheet: https://docs.google.com/spreadsheets/d/1jU6MYF7UI7a-UKdd5XhYCV6W1UyrMMCzYDFlgb8iNW8/edit#gid=1669916495 Code: https://github.com/archivesspace/archivesspace/blob/master/backend/app/converters/ead_converter.rb
...
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 this term:
...
Determine if new mapping documentation is needed for EAC-CPF
Not recommending RiC mapping at this time