1. CollectionSpace: Collaborations in support of UC museum collections Chris Hoffman Patrick Schmitz Research Information Technologies UC Berkeley

2. Introduction Who we are Collection management systems defined CollectionSpace: Dimensions of collaboration What we are learning about collaboration

3. Collection management systems defined

4. The core of a scholarly information ecosystem Controlled Vocabularies Data Sharing Digital Assets & Digitization Repositories and Preservation Education Outreach Mapping and Visualization Exhibitions Field Data Collection Archives and Libraries … a platform for research, education, and public service

5. The domain Supporting the research community Working with museum culture What can central IT do to help this community?

6. Dimensions of collaboration CollectionSpace Project Across Campus Beyond Berkeley

7. Dimensions of collaboration CollectionSpace Project Across Campus Beyond Berkeley

8. CollectionSpace is an open-source, web-based software application for the description, management, and dissemination of museum collections information – from artifacts to images, from Art History to Zoology Initial development funded by the Andrew W. Mellon Foundation

9. Technology and architecture Open source web-oriented technology stack – HTML, CSS, and JavaScript – Open source: Java, PostgreSQL, Tomcat, jQuery – Web services (REST) and plug-in architecture: Enable data sharing and interoperability – Accessible: Works great with keyboard and assistive technologies ECM as a platform CollectionSpace-as-a-Service: Hosting models

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

11. Organization and methodology Partnership organization Tools and methodologies Open source business development Foundation planning and building

12. Learning to collaborate Multi-year partnerships will evolve (plan for changes in partners) Multi-institutional software development is hard. Technology direction and leadership must be clear though flexible. Plan for scale early (whether considering SaaS or not) Cyclical soft money projects

13. Dimensions of collaboration CollectionSpace Project Across Campus Beyond Berkeley

14. Collection management systems at UC Berkeley Phoebe A. Hearst Museum of Anthropology University & Jepson Herbaria UC Botanical Garden History of Art Visual Resource Collection College of Environmental Design Visual Resource Center BAMPFA (PFA Library CineFiles) Essig Museum of Entomology UC Museum of Paleontology Museum of Vertebrate Zoology Biocode Specimen Database Human Evolution Research Center Berkeley Language Center Plus … Bancroft Special Collections and many others

15. UC Berkeley deployments Launched – University and Jepson Herbaria – Phoebe A. Hearst Museum of Anthropology In progress – UC Botanical Garden Customization, data migration, training, and support Thanks to campus funding and an IMLS National Leadership Grant

16. University and Jepson Herbaria Adapted CSpace to specimen management Hid many fields and procedures Modified loans out and media handling Renamed fields Added scientific taxonomy and identification Migrated 370K specimen records plus vocabulary records from legacy system Developed reports and extracts

17. Phoebe A. Hearst Museum of Anthropology Adapted CSpace to Anthropology collections Made major changes to field names and layout Added many fields Added Claims procedure Modified Movement/Inventory procedure Migrated 725K object records, plus 2M procedural records (inventory, accession, loans) plus vocabulary records from legacy system Developed reports Building web apps to support specific workflows

18. UCB Deployment versions Schema extension model Domain/Community of Practice versions PAHMA Bot Garden UCJEPS CSpace Core Platform HAVRCCEDVRC BAM/PFA

19. Learning to collaborate Partnerships take work. Plan for change. Keep partners engaged in community decision- making (or unique demands will overwhelm) Keep people on board while 85% common functionality is built Work in faculty-driven R&D style Build a team that can be successful collaborating with academic research stakeholders

20. Dimensions of collaboration CollectionSpace Project Across Campus Beyond Berkeley

21. Communities of practice Collaboration and community-building are key to CollectionSpace and to UC Berkeley Community design workshops IMLS workshops Developer community – Deployer workshop – Code contribution model Hosting community

22. Learning to collaborate The importance of museum leadership and vision Recognize that coalitions are often stronger outside your own university Community-building takes time – set expectations accordingly Nurture your developers and keep them communicating across traditional boundaries

23. Conclusions Learning how to collaborate How to learn more – http://wiki.collectionspace.org/ http://wiki.collectionspace.org/ – http://wiki.collectionspace.org/display/deploy http://wiki.collectionspace.org/display/deploy – http://www.collectionspace.org/ http://www.collectionspace.org/ How to get in touch with us – chris.hoffman@berkeley.edu chris.hoffman@berkeley.edu – pschmitz@berkeley.edu pschmitz@berkeley.edu