Develop a schematron import pathway (for EAD, possibly extend to other import formats)
- Move working schematron file to ArchivesSpace github: https://github.com/archivesspace
- Identify and include additional ASpace constraints in schematron file (get the major ones; might be impossible to get everything)
- Is Mark's the most comprehensive?: https://github.com/fordmadox/schematrons/blob/master/ArchivesSpace-EAD-validator.sch
- Document the ASpace constraints and publish for the community. Include with other import/export documentation at: http://www.archivesspace.org/migrations
- Develop / publish documentation for community on how to run schematron batch-validation in Oxygen (see Mark Custer's post: http://campuspress.yale.edu/yalearchivesspace/2015/07/22/validation-scenarios/)
- Explore options for providing schematron validation as a web service or part of the application. See examples below:
- Nathan Stevens' pilot site: http://128.122.90.55:8083/SchemaMap/
- Harvard's archivesspace checker: https://github.com/harvard-library/archivesspace-checker
Archon Migration script testing
- Continue testing Archon migration script, report issues back to developers
Support for EAD3
- Document changes to the ASpace data model needed to support import/export of EAD3
- Make changes to data model and import/export code
Review data import/export mapping documents for accuracy (http://www.archivesspace.org/importexport)
- EAD
- MARCXML
- Accession CSV
- Digital Objects
"Background Work"
- Monitor ASpace user list, serve as first responders for migration and import/export related posts
- Serve as a resource for members migrating data to ASpace from various legacy systems/formats (Access, FileMakerPro, etc.)