Page tree
Skip to end of metadata
Go to start of metadata

Accomplishment: Shipped 1.0 and successive releases of CollectionSpace

Description:

Successfully shipped the 1.0 version, helped to transform the project development model to actually implement agile methodology, shipping successive releases roughly every 6 weeks. Added many new features, moved from MySQL to PostgreSQL to improve performance at scale, began implementation of model for community contributions. Detailed feature deliverables are documented on the project wiki roadmap.

Purpose/Importance:

The CollectionSpace project will provide a common, scalable solution for managing museum and research collections across the campus, and eventually across the system. This replaces a number of aging systems based upon obsolete technologies, and that require considerable overhead to support and maintain. It adds significant new functionality, provides accessible web-based interfaces, and leverages current enterprise technologies for security and stability.

Impacted areas:

This directly impacts the museums and research collections supported by IST, including:

  • Essig Museum of Entomology
  • History of Art Visual Resource Collection
  • Phoebe Apperson Hearst Museum of Anthropology
  • UC and Jepson Herbaria
  • UC Botannical Garden
  • UC Museum of Paleontology
  • etc.

Because of the broad impact of these research collections, the indirect impact spans much of the research and teaching mission of the University.

Strategic Alignment:

This project represents a considerable strategic accomplishment in aligning many campus collections on a single sustainable strategy. We have adopted a SOA based approach and a highly configurable model that allow the project to scale, and to adapt, to support a very broad range of needs. We implemented a multi-tenant approach allowing us to expose a SaaS model to the campus, to improve service provided while reducing the administrative overhead at scale.

We have had discussions with other campuses, with CDL, and with external partners to provide hosted services for other collections.

We are working actively with technology partners to leverage existing services wherever we can, in alignment with a strategy of smart-sourcing.

While we made technology choices before a strategy had emerged for alignment on a single SOA/ESB stack, we are working to port the application framework to the OSGi stack that is emerging as common model.

  • No labels