Presentation on theme: "Introducing CollectionSpace"— Presentation transcript:
1Introducing CollectionSpace A collection management system and foundation for researchHoffman, Christopher R.,Doran, Andrew,Moe, Richard,McGrath, Patrick,Mishler, BrentUniversity of California, Berkeley
2AgendaUC Berkeley’s collection management systems and the BNHM-IST PartnershipIntroducing CollectionSpaceHow to learn more
3UC Berkeley’s Collection Management Systems Specimen Management System for California Herbaria (SMASCH) (University & Jepson Herbaria)PAHMA Collections (BNHM Consortium, Phoebe A. Hearst Museum of Anthropology)SAGE (UC Botanical Garden)UCMP Specimen Database (BNHM Consortium, UC Museum of Paleontology)Essig Specimen Database (BNHM Consortium, Essig)MVZ/Arctos Specimen Database (BNHM Consortium, MVZ)Biocode Specimen Database (BNHM Consortium)HERC Specimen Database (BNHM Consortium, HERC)History of Art Visual Resource Collection (HAVRC) (Department of History of Art)Slide & Photograph Image Retrieval Online (SPIRO) (Architecture Visual Resources Library)CineFiles (Pacific Film Archives)Berkeley Language Center’s Archival Catalog & Circulation System (Berkeley Language Center)Plus … Bancroft Special Collections and many othersMany collections, from Zoology to Art, many domains…Centrality of collections to mission. Collections include:Historical and cultural artifacts, specimens from many life science domains, VRCs from art history, etc., archival materialsAcross museums, archives, research, and faculty collectionsHere we show a list that is primarily but by no means exclusively Museums. Boundaries are fuzzy.
425 Year Technology Legacy Campus supports a broad range of collections, from Art to Zoology, but …Too many aging legacy systemsMillions of objects, artifacts, specimensManaged in about 20 different collection management systemsRunning on about 15 hardware platformsMaintained by about 10 different technology groups, with various degrees of technical experienceInconsistent decision-makingInsufficient and inadequate funding models in a time when university funding is challengedCampus-wide enterprise pictureDoes this sound familiar?
5BNHM-IST PartnershipPartnership formed between a consortium of natural history museums and central information technology provider to take on this problemBecoming a model for broader campus collections planning and decision-makingBNHM is a leader in biodiversity collections-based research and has built or partnered in numerous systems and partnerships: Numerous collection management systems, BerkeleyMapper, CalPhotos, BioGeomancer, AmphibiaWeb/OrnisNet. Moorea-Biocode (FIMS, LIMS integration). Also a model for collaboration: Canadensys-UCB, Arctos, Moorea-Biocode, VertNet, and so on.Informatics Services: MIP + BSCIT, part of IST Data Services, an IT organization created to focus on Data and Content Management Technologies and Services for campusOne of 4 major central IT departmentsBoth Administration and ResearchStrong engagement with e-research & shared services – technically, programmatically
6Collection Management Systems – the center of a scholarly ecosystem Taxonomy and ThesauriOutreach and Data SharingDigital Assets and ContentEducationArchives and LibrariesField Data CollectionField Station Sensor NetworkExhibitionsMolecular Lab Information ManagementGeospatial ServicesCollection Management SystemsHub applications and platforms
7CollectionSpace is an open/community-source, web-based software application for the description, management, and dissemination of museum collections information – from artifacts and archival materials to exhibitions and storage.So what is CollectionSpace?
8CollectionSpace design features Web-basedHighly customizableInteroperableLocal or hosted deploymentsCommunities of practiceA platform for sharing collections informationDesigned to address the needs of cultural heritage AND biodiversity natural science collectionsWhat do we like about CollectionSpace? Functionality; business case and sustainability emphasis; technology and architectureCan support a range of hosting and deployment models, from dedicated servers, to cloud-based virtual machines, to robust data center environmentsDesigned for small standalone museums and large multi-museum universitiesDesigned for simple installs by small museums as well as enterprise-wide deployments and custom configurationsFrom minimal technical support at a museum to enterprises with access to IT professionals.
9CollectionSpace Sustainability Focus on sustainability at all levels & scalesConsortial fund-raisingCommunities, collaboration, and consortiaWorking with vendors and service providersAn emerging foundation-like partnershipExploring boundaries (libraries, archives, museums)And beyond higher educationUC Berkeley and CollectionSpace project participating in a wide range of conversations about higher education and research cyberinfrastructure sustainability.
11Schema Extension Model HerbariaUCJEPSAnthro-pologyPAHMAMust support extension, customizationCan add additional information beyond the core set for a given serviceJust edit the XML schema for a service to add these – the system manages the restBy dividing the extensions into two groups, we will facilitate sharing and re-use within sub-domains.Longer term, if a domain community standardizes their common extension schema, we can then consider adding domain-specific functionality that takes advantage of this.Schema model for a customized service deployment
12Future: Publish to Cloud Current & Existing publishing models for museums using Darwin Core (DwC)The University andJepson HerbariaDwCOld/Current Portals:TAPIR, DiGIR,ABCDFuture: Publish to CloudDwCAnother example of our domain-based approach, this will facilitate data sharing and interoperability. CollectionSpace will have built-in common services for data extracts and interoperability. In our deployments, we are building extensions for natural history collections to accommodate data sharing standards (legacy, emerging, and future).DwC + + Paleo ExtensionDwC+ Cultural Extension
13Sample Mapping between Darwin Core (DwC), CollectionSpace, and University & Jepson Herbaria DwC DescriptioncatalogNumberobject_numberaccession.accession_idAn identifier (preferably unique) for the record within the data set or collection.institutionCodecollectionCoderesponsible_departmenti.inst_nameThe name (or acronym) in use by the institution having custody of the object(s) or information referred to in the record.?The name, acronym, coden, or initialism identifying the collection or data set from which the record was derived.decimalLatitudefield_loc_lat_decimalaccession.loc_lat_decimalThe geographic latitude (in decimal degrees, using the spatial reference system given in geodeticDatum) of the geographic center of a Location. Positive values are north of the Equator, negative values are south of it. Legal values lie between -90 and 90, inclusive.decimalLongitudefield_loc_long_decimalaccession.loc_long_decimalThe geographic longitude (in decimal degrees, using the spatial reference system given in geodeticDatum) of the geographic center of a Location. Positive values are east of the Greenwich Meridian, negative values are west of it. Legal values lie between -180 and 180, inclusive.year month dayfield_collection_date_earliestaccession.early_jdate (calc)The four-digit year, month, or day in which the Event occurred, according to the Common Era Calendar.And so on……DwCUniv. & JepsonHerbariaThis slide demonstrates how during our schema mapping and data migration planning, we are modeling a Darwin Core mapping that can be shared across natural history collections (and extended as needed) to support data sharing and interoperability from the core.Darwin Core and IPT as a framework for data sharing from BNHM deployments of CollectionSpace
14CollectionSpace Status CollectionSpace Release 1.0: Summer 2010Pilot deployments: Ongoing nowCollectionSpace 2.0: July 2010 – November 2011Goals: Stability, usability, and sustainabilityDevelop the larger consortium for sustainabilityUC Berkeley deploymentsStarting with Anthropology (PAHMA) and Herbaria (UCJEPS) collectionsIntegrated with CollectionSpace 1.1 through 2.0 planningDocumenting our experience and developing templates for other museumsCheck with Megan!CS1:Core procedures: object entry, acquisition, cataloging, loans in, loans out, and retrospective documentation. Vocabulary control, media handling, customization, security, and documentation.Pilot deployments: Domains from Anthropology to Life Science to Cultural Heritage; Community-driven templates and experience (data migrations…)CollectionSpace 2.0Goals: Stability, usability, and sustainabilityExpand baseline functionality- Increase documentation- Optimize software for service providersImplement CollectionSpace sustainability planPilots are proceeding already, maximize testing, feedback, and experience with tools for porting collectionsMore deployments in 2010 will provide a good set of schemas and templates for others to use, along with a community of practice to support one another, which will also support further adoption.14
18So why CollectionSpace? Campus-wide efficienciesExcellence for core missionsTrue community-source and open-source solutionConsortial community-based approach to funding and financial sustainabilityCampus-wide efficiencies: Best combination of functionality, business case for sustainability, and technology/architectureCore mission excellence: A framework and platform for research, education and outreach to support the missions of the museums and the university
19Getting Involved We would like to: Learn more about your institution’s needsHelp you gain support for implementation of CollectionSpace within your organizationBuild a sustainable community of users and contributorsWe are looking for partners to help us make this a success!
20BNHM Consortium and CollectionSpace https://wikihub.berkeley.edu/display/istds/Ber keley+Natural+History+Museum+and+IST+P artnership