BAMPFA Art CollectionSpace Migration Timeline

Owned by Chris Hoffman
Last updated: Oct 11, 2014
1 min read

Note: 10/11/2014 - This is the original schedule but was updated later during the project.

DRAFT 2/17/2014

March: Form team, finalize requirements, finalize data mapping, finalize initial user interface designs, and set up dev server.

April: Build initial data extraction and transformation scripts, and begin customizing CollectionSpace code.  Sign final agreement about gaps and workarounds.

May: Continue customizing CollectionSpace code, begin any deeper level programming (e.g., media handling workflows), and continue data extraction and transformation.

June: Continue Data ETL (extract, transform, load), customization and deeper programming. Mid-June, deliver first prototype with subset of data, customizations, and functionality.  BAM/PFA tests first prototype. 

July:  Perform design work on two to three web applications to support move (based on PAHMA web applications).  Make revisions to CollectionSpace customizations and functionality. Begin work on web applications. Adjust schedule as needed based on planning for move.  Set up prod server.

August: Beginning of month, deliver second demo with more complete set of data, customizations, and functionality.  BAM/PFA performs testing.  Make final tweaks and bug fixes (no new functionality or schema changes). BAM/PFA helps with documentation, workflows, and training.

September:  First week. Launch and transition to CollectionSpace.  Finalize image workflows (media handling) and data feeds to Drupal web site.

October to December: Post-launch support