2016-01-08 Meeting notes

Update on batch EAD import testing to identify ASpace constraints

Update from Terry C:

• Using EAD3 testbed of 1500 EAD instances to test migration.
• Cannot do a batch import, because the import breaks / stops at the first error.
• Creates a barrier for establishing a set of problems
• Possibility of using a plugin developed by Mark Cooper, but am unable to find the plugin at this point. May inquire with Steve M. at UVa and Trevor at NCSU. Mark Cooper's plugin is here.
• Will survey and synthesize reports from others.
• Submit a feature request for building a batch import process. Build it on Mark Custer's schematron process.

Next steps:

• Use Mark Cooper's plugin for bulk import error collection test (https://github.com/lyrasis/aspace-jsonmodel-from-format)
• Develop schematron for known constraints and requirements, building off of Mark Custer's  (https://github.com/fordmadox/schematrons) and Dave Mayo's schematron (https://github.com/harvard-library/archivesspace-checker/blob/master/schematron/archivesspace_checker_sch.xml) work.
• Follow up with Chris about setting up prototype schematron based validation service

Guidelines from Maureen C. and Patrick G.: https://docs.google.com/document/d/1aIKCpExEaIvc_miEX8Eick1Ix2dsS9ayDQz9YLsSnoI/edit?usp=sharing

• Feedback/comments on this document?
• Status of container management migration testing - Will be taken up by testing group with larger call for testing by the community. There will likely be 2 or more release candidates available for testing.
  • Brad will put test protocol doc into a Google file.File is located here.
• Communication plan
  • Clarify that after release of ArchivesSpace v1.5.x, all AT/Archon migrations must be to ASpace v1.4.2, then upgraded - Yes, this is true, will make sure to communicate this in release notes, announcements, etc.
  • How to communicate potential container management migration issues / data cleanup required before migration?
    • Will distribute parts of Maureen's doc
    • Already a command line warning when you attempt to migrate to release with container mgmt.

Discussion of what should be included in a FAQ:

https://docs.google.com/document/d/1lR-Bwh5RItCXU-GuknZGWge9r615xmXRDHHyw4RBptU/edit?usp=sharing

What, if any, screencasts might sub-team members contribute?

• List of potential topics: Topics for the ArchivesSpace User Screencast Series
• Example screencasts: http://docs.archivesspace.org/screencasts/index.html
• Screencast guidelines: Instructions for Creating a Video for the ArchivesSpace User Screencast Series

What might be covered by an AT/Archon Migration or import/export screencast? Are there common problems that orgs encounter?

===============

Brad mentioned that screencasts emerged out of desire to create short tutorials based on content already in ArchivesSpace training manual. Screencasts can be created using Camtasia or any other tool.

The UAC's Documentation sub-team has ownership of the screencasts. If interested in creating a screencast, should contact them to claim a topic. There is some funding to provide $100 honorarium for screencast producers.

Possible Structure for AT/Archon Migration screencasts:

• Basic overview of process
• Setting up the environment
• Finding, downloading, installing tools
• Explanation of the tools / running the tools
• Explanation of configuration options
• Assessment
• Interpreting / fixing errors

Action items below

Next call, Friday, Feb. 12th at 1pm, ET.