Skip to end of metadata
Go to start of metadata

Introduction

Phase III of the CollectionSpace project began in January 2012. The focus of the work in Phase III will be the development of CollectionSpace as a sustainable enterprise using an approach based on the software as a service (SaaS) model. Activities undertaken to accomplish this will include development of a business model and strategic plan; development and deployment of CollectionSpace as a hosted service in two trial environments; and completion of the initial core software development cycle. Through these activities, the CollectionSpace organization, whether stand-alone or ultimately housed within an existing not-for-profit organization, will emerge as a viable community support organization, capable of supporting a growing and heterogeneous population of museum, academic, and scholarly end-users in need of collections management software and services.

Work Plan (software development)

January 2012 – March 2012

CollectionSpace as a Service
Trial One: UC Berkeley test-bed environment:

  • Set up multi-tenant platform on virtual server in IST data center
  • Import data from three campus collections
  • Perform functional, performance, and security tests
    Trial Two: CollectionSpace organization proxy environment:
  • Map data-sets from participant museums

End-user Functionality Development

  • Core development team and implementers: Review existing design and scope documentation (functional requirements) and all reported functional issues for location tracking and movement control processes, advanced search, media handling, and vocabulary control.
  • Development sprint to complete outstanding work: Test and release internal releases v2.1, v2.2, and v2.3

Early Adopter Support

  • Provide technical support and issue resolution to existing early adopters.
  • Engage and support community developers providing extensions and customizations.

April 2012 – June 2012

CollectionSpace as a Service
Trial One: UC Berkeley test-bed environment:

  • Evaluate test results and document gaps in service provision
  • Integrate, adapt, develop, and test tools required to support service provision
  • Define goals and requirements for SaaS scaling (e.g., the ability to bring on more museums within an existing multi-tenant environment and to ensure proper application performance)
    Trial Two: CollectionSpace organization proxy environment:
  • Set-up multi-tenant platform on virtual servers
  • Load data from Museum of the Moving Image, Walker Art Center, Balboa Park
  • Perform functional, performance, and security tests

End-user Functionality Development

  • Core development team and implementers: Review existing design and scope documentation (functional requirements) and all reported issues related to configuration and upgrade path
  • Development sprint to complete outstanding work: Test and release internal release v2.4, external release v2.5, and internal release v2.6

Early Adopter Support

  • Work with early adopters to refine functional requirements, identify and fix bugs.
  • Engage early adopters in quality assurance testing and evaluation of version 2.5
  • Engage and support community developers to ease implementation of schema extensions and local configurations.

July 2012 – September 2012

CollectionSpace as a Service
Trial One: UC Berkeley test-bed environment:

  • Develop and test additional SaaS hosting tools
  • Document SaaS hosting tools
  • Author guidelines and best practices for providing CollectionSpace as a Service
    Trial Two: CollectionSpace organization proxy environment
  • Evaluate test results and document gaps in service provision
  • Adapt and/or develop tools required to support service provision
  • Test, evaluate, and document tools

End-user Functionality Development

  • Core development team and implementers: Develop design and scope documentation (functional requirements) for wizards (1) upgrade, (2) configuration, and (3) installation.
  • Development sprint to complete outstanding work.
  • Development sprint to complete outstanding work: Test and release internal releases v2.7 and v2.8, and external release v3.0

Early Adopter Support

  • Engage early adopters in quality assurance testing and evaluation of version 3.0
  • Provide technical support to community developers, and functional support to end-users to ensure that local implementations are meeting their needs.

October 2012 - December 2012
No-cost extension period

  • No labels