CollectionSpace for Technology Service Providers and Developers
October 22, 2009
www.collectionspace.org
CollectionSpace is an open-source, web-based software application for the description, management, and dissemination of museum collections information – from artifacts and archival materials to exhibitions and storage.
Project Partners•Museum of the Moving Image in New York
•Information Services and Technology division of the University of California, Berkeley
•Fluid Project, led by the Adaptive Technology Resource Centre at the University of Toronto
•Centre for Applied Research in Educational Technologies at the University of Cambridge.
Funder Initial development: Andrew W. Mellon Foundation Funding opportunities for implementation and customization
Project TeamThe CollectionSpace project team is composed of domain experts, designers, architects, and developers from each partner organization.
Development teams work in cycles to issue regular software releases.
Drivers Growing interest in hosted applications and SAS New open architectures, technologies, standards, and licensing
models Cyclical reevaluation of existing collections management systems
Requirement for wide access to collections information
Need to leverage collections information across a wide range of uses.
Today’s and tomorrow’s funding climate
Benefits Beyond the one-off
Beyond one-size-fits-all
Leveraging of existing human/financial resources
Leveraging development work across many projects and institutions
Choice of service providers
Why Now? Why Me?
Vendor/service provider involvement critical to success and survival of project
Initial Releases
0.2: released October, 2009. Allows user login, creation of intake record, and auto-fill intake and object identification numbers.
0.3: November, 2009. Includes ID service with choice of sequential identification; vocabulary service, to provid access to controlled lists; and support for acquisition.
Etc., etc., etc. (regular monthly releases through 2010)
CollectionSpace Architectureand Deployment Model
Patrick Schmitz
U.C. Berkeley IST/Data Services
Co-Technical Lead, CollectionSpace
UCB and CollectionSpace Dozens of world-class museums and research collections.
Range from small to very large Cover a very broad set of domains
IST/DS supports many of them Many existing systems aging, brittle Solutions must integrate with the enterprise Solutions must support research, teaching, and public
service. Team combines enterprise architecture expertise with
museums domain experience.
Planned deployment models Must support individual museums that
want to run their own systems.Single package runs on server/VM slice
Must support hosted, SaaS modelSupport many museums on single instanceProvides more cost-effective solution at scale
Customization, extension a top priority!
Services, SOA, and the project How does our piece fit into the whole? Why SOA
Enterprise standard for integration, reuse Scales well to support many instances, SaaS Exposes information as Web Services for re-use,
enabling mashups and new applications What SOA is and isn’t
Note: SOA != SOAP. We like ROA/REST. Services model common entities, and relations, but are
extensible to provide a flexible “data model”, for each collection.
Schema Extension Model
Schema model for a customized service deployment
Services technology stack All open-source software
No vendor lock-in, source code available Core layers have broad community Commercial consulting available
Base layers built to support ECM Document+Image management and processing tools Currently using Nuxeo (with abstraction layer);
could move to Alfresco, or other CMIS-compliant base. Our layers provide CollectionSpace-specific services:
CMS entities+relations (CollectionObject, Loans, Location, etc.) Authentication/authorization, workflow, multi-tenancy, etc.
C-S
pace
Serv
ice
s
Nu
xeo
Pla
tform
Serv
ices
Services Stack
CollectionSpace Application
Dan Sheppard
University of Cambridge, CARET
Co-Technical Lead, CollectionSpace
Application Layer
Why is it needed? What is it / isn’t it? How does it work? Where does it fit?
CollectionSpace User Interface
Colin Clark
University of Toronto, Fluid Project
Co-Technical Lead, CollectionSpace
The UI Layer is…
Designed
The UI Layer is…
Configurable
The UI Layer is…
Web-Oriented
The UI Layer is…
Flexible and Accessible
Q+A
Get InvolvedEmail:[email protected]
Call:Carl Goodman, Principal InvestigatorMuseum of the Moving Image718-784-4520
Project Websitewww.collectionspace.org
Project Wikiwiki.collectionspace.org