Import/export mapping review process

The 2019-2020 Metadata Standards TAC subteam moved the MARC and EAD mappings to a Google doc, and began reviewing the published mappings. The most up-to-date import/export mappings for MARC and EAD are found here:

https://docs.google.com/spreadsheets/d/1jU6MYF7UI7a-UKdd5XhYCV6W1UyrMMCzYDFlgb8iNW8/edit#gid=1527709562

In addition to the mappings themselves, the subteam is "showing its work" by leaving the review columns in place.  These indicate when the mapping was reviewed, whether it works as described, and what test record and AS version were used. This is an ongoing project.


Details of Review Process

Steps taken by the 2019-2020 TAC Metadata Standards subgroup in reviewing the published import/export mappings.

Import testing: Import test records (sandbox, test instance) and confirm behavior/note discrepancies.

Export behavior: Post full records via API, export records and confirm behavior/note discrepancies.

Desired outcomes:

*An updated set of MARCXML and EAD import/export mappings

*A process for more easily keeping these more up-to-date 

Github repository for test records: https://github.com/ASpace-Metadata-Standards

Existing published standard: https://archivesspace.org/using-archivesspace/migration-tools-and-data-mapping

Google sheet with copy of published standard and review tracking fields: https://docs.google.com/spreadsheets/d/1jU6MYF7UI7a-UKdd5XhYCV6W1UyrMMCzYDFlgb8iNW8/edit#gid=1527709562

ArchivesSpace sandbox: http://sandbox.archivesspace.org/ (admin/admin)

Server for metadata testing: http://metadata.lyrtech.org/staff/ (admin/admin)

Import Testing

Log in to sandbox. Create a repository if necessary. Create a background import job, choose the record type, and the test file. Run the import. Review the desired field. If needed, modify the test file to add/subtract/edit fields, commit to repo, and re-import.

On the export mappings google doc, fill in the review columns as follows:

ReviewerDateAS versionTest record usedWorks as described? (Y/N)Notes / Further Actions

Links


(your initials)(today's date)(version, and if applicable instance, e.g. sandbox)(github link to specific version of record used)(did the fields import as described in the mapping?)(if not, or if there are other issues, describe them)(links as needed; to tickets, standards, etc)