Introduction

An expansive list possible functional requirements was compiled in 2009 and informed our point of departure for the identification and prioritization of functionality that would be developed. Since then, functional requirements and priorities have been refined based on community feedback and end-user needs. The project team is always interested in institutional use cases which help us expand our functional requirements, create inclusive designs, and develop services that accurately reflect our community's needs. We welcome you to add your institutional use-case to any of the pages listed below. 

Development activities have been on-going since 2009.  CollectionSpace Phase One (2009-2010) centered on a subset of eight SPECTRUM procedures (workflows): Object Entry, Acquisition, Location and movement control, Cataloging, Object exit, Loans in, Loans out, and Retrospective documentation. Functional requirements for the eight procedures, along with requirements for functionality that supports the procedures, are below. Phase Two (2010-2011) focused on support for media handling, hierarchical vocabularies, delete, import, export, and groups and Phase Three (2012) provided additional support for advanced search, structured objects, locations, movements and inventory, as well as for management of thesauri and controlled vocabularies.

The first development milestone, reached in the spring of 2009, represented a significant integration effort of various tools and technologies around the core procedure of object entry. This work established the groundwork for ongoing development, and included: resolving technology stacks; developing and testing tools and workflows; designing and implementing the testing strategy; setup of the code repository and commit standards; installation and experimentation with development platforms; finalizing service families and detailing the initial service contracts; establishing lightweight governance mechanisms for services shared with other projects such as Kuali Student Services (KSS); designing the configuration and customization language and tools; and prototyping the application's user interface with Fluid/Infusion tools.

Requirements

As the system design and development process moves along, the language used by the CollectionSpace team will change and evolve. Below is a list of commonly used terms/concepts in the functional requirements, all of which are subject to change as a result of testing and user feedback.

• Objects: Used as shorthand for single objects, groups of objects, objects with physical and digital form, parts of objects, and so on. An object record may describe a box of unidentified sherds, or a single painting.

• Organizational records: Used to capture and manage information with extrinsic relationships to object records, such as authority files, thesauri, storage locations, and support media. Support media records are used to capture and manage information about images, documents, audio, video, and other media added to support or represent object, procedural, and organizational records.

• Procedural records: Used to capture and manage information that revolves around a specific collections management workflow such as intake, acquisition, loans, or cataloging.

Schema

Standards and Guidelines

Use Cases

User Story Repository

Sample Collections Data