Orient new sub-team members, review past and ongoing work, develop work plan.
Discussion items
Time
Item
Who
Notes
Roll call / introductions
all
Sub-team members introduced themselves and briefly describe role in institution and experience with ArchivesSpace
Establish regular monthly meeting time
all
Seems like 2nd Friday at 1pm, Eastern works. Noah will send recurring meeting invite
Discuss past / ongoing work of subcommittee
noah/brad/michael
To date, Nathan Stevens (AS Migration Specialist) has provided support for AT and Archon migrations with some consultation from the group. Phil Suda and Chris Prom have been working with Nathan on troubleshooting issues with the ARchon migration script.
Nathan will no longer serve as Migration Specialist after October and so Brad expects some of the support/responsibility for AT and Archon migration to shift to this sub-team. It's a little unclear what this will look like (helping troubleshoot bugs and create JIRA issues?).
The group should discuss at a future meeting and come to agreement about our specific role in supporting AT/Archon migration.
Over the past year or so the migration sub-team has focused primarily on testing various import/export pathways with particular attention on EAD import/export. Members of the sub-team have submitted several issues in JIRA related to import/export.
Brad and Cory Nimer have been doing some work on improving support for EAC import/export. They plan to update data maps and bring a revised specification to the membership along with user stories and some wireframes showing changes to the Agent record data model.
Review sub-team charge (skipped, whoops)
noah
The Migration Sub-team ensures successful migration from Archivists Toolkit and Archon to ArchivesSpace for members and non-members through testing, support, documentation, bug fixes and enhancement prioritization. The sub-team also tests import and export of various formats to ensure successful "migration" of legacy data not in AT or Archon.
The group did not discuss the charge, but will discuss at a later meeting
Discuss possible areas of work, priorities, and work plan
Ideas from Brad:
Schematron based import pathway
Support for EAD3 (export following by import)
METS export for Digital Objects (update to include events and rights)
Others?:
Serving as "first responders" to User Group messages re: migration, import/export
Develop Accession XML import schema (model after AT import schema)
Digital Object import (batch import, linking to archival objects)