1. CollectionSpace for Technology Service Providers and Developers October 22, 2009 www.collectionspace.org

2. 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.

3. 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.

4. Funder Initial development: Andrew W. Mellon Foundation Funding opportunities for implementation and customization

5. Project Team The 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.

6. 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. Todays and tomorrows funding climate

7. 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

8. Why Now? Why Me? Vendor/service provider involvement critical to success and survival of project

9. 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)

10. CollectionSpace Architecture and Deployment Model Patrick Schmitz U.C. Berkeley IST/Data Services Co-Technical Lead, CollectionSpace

11. 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.

12. 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 model Support many museums on single instance Provides more cost-effective solution at scale Customization, extension a top priority!

13. 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 isnt 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.

14. Schema Extension Model Schema model for a customized service deployment

15. 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.

16. C-SpaceServices NuxeoPlatformServices Services Stack

17. CollectionSpace Application Dan Sheppard University of Cambridge, CARET Co-Technical Lead, CollectionSpace

18. Application Layer Why is it needed? What is it / isnt it? How does it work? Where does it fit?

24. CollectionSpace User Interface Colin Clark University of Toronto, Fluid Project Co-Technical Lead, CollectionSpace

25. The UI Layer is… Designed

27. The UI Layer is… Configurable

28. The UI Layer is… Web-Oriented

29. The UI Layer is… Flexible and Accessible

30. Q+A

31. Get Involved Email: talk@lists.collectionspace.org Call: Carl Goodman, Principal Investigator Museum of the Moving Image 718-784-4520 Project Website www.collectionspace.org Project Wiki wiki.collectionspace.org