Trevor, thanks for sending out this draft.  I won't be on the call, so I wanted to send along my one comment re the list for consideration by the group --

I would like to see something about documentation of the migration process itself.  With government records, authenticity and audit trails go hand/hand, so any activity like this that touches the files should be documented with at least a basic set of metadata (e.g., when, who, what, etc.).  Also, under items #1, 2, & 3 after migration, any file/metadata migration failures/changes/restores should be documented as well.  Copies of this documentation could be stored with the files themselves.

I'm looking forward to seeing this checklist move forward --

Shawn Rounds
State Archivist
State Archives Department
Division of Library and Collections
Minnesota Historical Society
345 Kellogg Boulevard West
Saint Paul, Minnesota 55102

MNHS online:

On Mon, Aug 4, 2014 at 8:41 AM, Owens, Trevor <[log in to unmask]> wrote:

In advance of next Infrastructure call, I am distributing this rough draft of a guidance document/check list for us to work over on the call. As background, a subgroup of infrastructure folks took up the action item to draft this with the intention of bringing it back to the full group to discuss 1) if this seems to be going in a useful direction 2) if so, to identify some things to improve and revise in it. So if you can make time to give this a quick read in advance of the call great, if not no worries. If you see little things to tweak or fix in the doc just go for it. If you want to raise comments feel free to post those too.


Draft Title: Good Migrations: A Checklist for Migration from One Digital Preservation Stack to Another


Link to draft document:


Objective of the Document: The goal of this document is to provide a checklist for things you will want to do or think through before and after migrating components in your digital preservation system. This could entail switching from one system to another system in your digital preservation and storage architecture (Various layers of hardware, software, databases, etc.). Issues around normalization of data are out of scope for this document. This document is strictly focused on checking through issues related to moving fixed digital materials and metadata forward to new systems/infrastructures.


·         Call Date/Time: Tuesday 8/26/14, 2:00 PM EST

·         Dial in number: 877-299-5123