Page Comparison

Establish regular monthly meeting time

Seems like 2nd Friday , early afternoon?at 1pm, Eastern works. Noah will send recurring meeting invite

• 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)

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)
• Review data import/export maps (esp. MARC): http://www.archivesspace.org/importexport
• Archon Migration script?

Schematron work:

• Nathan's Schematron validation service: http://128.122.90.55:8083/SchemaMap/
• Mark Custer's Schematron file: https://github.com/fordmadox/schematrons/blob/master/ArchivesSpace-EAD-validator.sch
• Harvard's ArchivesSpace Checker: https://github.com/harvard-library/archivesspace-checker
• Harvard's schematronium (gem that runs schematron over 1 or more xml): https://github.com/harvard-library/schematronium

The group had a spirited discussion about issues surrounding the development of a schematron-based import pathway for EAD:

• Chris P. asked if we should consider removing some of the EAD import constraints imposed by ASpace
• Terry C. noted that AS will likely always support only a subset of all "valid" EAD for import
• Brad noted that DACS is the underlying ASpace data model, not EAD and that we shouldn't remove constraints imposed by DACS.
• Terry C. suggested the group could focus on:
  • 1) documenting AS constraints (while developing schematron).
  • 2) Providing guidance to AS community for fixing ASpace-invalid EADs
• Phil noted that constraints should be noted in Migration guidelines or alongside import/export maps: http://www.archivesspace.org/importexport
• Terry also suggested the group could provide documentation to community for how to run schematron validation using Oxygen
  • Mark Custer wrote a blog post (shared on the AS user-list) about using schematron w/ Oxygen: http://campuspress.yale.edu/yalearchivesspace/2015/07/22/validation-scenarios/
• The group seemed to agree that the schematron file should be maintained in the ASpace github repo