Community & Open Source Software in Cultural Heritage Institutions
Kuali OLE – Molly Tamarkin, Duke
OLE – Enterprise library management system – backend for technical processes in library. Not the interface to the collection.
Funded by Mellon – just received year 3 final grant from Mellon. Goal is to have v 1.0 out by then. Early adopters are Chicago and Lehigh.
PM and core team based at Indiana, HTC (commercial firm) doing the coding.
Shared implementation community with academic libraries.
Shared vendor community with Kuali Commercial Affiliates
Commercial and possible shared hosting – local cloud/hosted cloud
Shared expertise in integrations with other Higher Ed information systems (SAP, Peoplesoft)
Shared ERM in GOKb
Enables workflow and queues for siloed systems.
Base stack includes Kuali Financial System, Apache Jackrabbit, Kuali Rice 2.0
V 0.8 coming Q2 2013. Ready for libraries to load data into system for early adopters. Version 1.0 Q4 2013, includes cloud hosting scenarios, final integration with full RICE 2.0 and KFS 5.0.
GOKb – Global Open Knowledgebase – freely available data repository that will contain key publication information about electronic resources (for library management) as it is represented within the suppy chain from content publishers to suppliers to libraries. Designed with JISC in the UK. A separately funded Mellon project.
Sustainability
Need community big enough to sustain development. Now it’s 8 schools. Don’t need to take over the whole market.
Collectionspace
Angela T. Spinazze
Open source, web-based software app for the description, management, and dissemination of museum collections information – from artifacts and born digital works to loans and acquisitions. An institution-wide support system. Supports registrars, collections managers, curators, educators, administrators and more.
Marketplace – Heritage Health Index, 2007: ALmost 30% of historical societies, 25% of museums, and 20% of archaeological repositories have no catalog records at all. 50% of collecting institutions in the US have none of their collections available online. This information gap represents a lost opportunity for museums and points to a core community need.
Landscape – served by over 20 different commercial providers and a vast array of ‘home-grown’ solutions. Museums have been producing innovative visitor-facing apps that take advantage of the latest tech for years. While many of these apps include information drawn from collections management systems, the collections management system itself is rarely improved as a result.
Came out of Museum of the Moving Image, funded by Mellon. Team includes Walker Art Center, Caret, SMK, Fluid. Using agile approach, pushing software every 4-6 weeks. Doing 2 public releases a year, with full regression testing.
Project ethos – open, inclusive, transparent – gather information about functional reqs from museum standards and domain-specific guidelines.Schemas based on Spectrum, a documentation standard from the UK.
Flexible application: Services-oriented architecture. Can use a whole or in smaller implementations. Two deployment options: stand-alone and SaaS. Designed to play well with others including digital asset management and web-based publishing platforms. Data schema based on SPECTRUM documentation standard.
Schema extension model – 3 tier. Common entity schema (common semantics); Domain-community specific extensions (common across multipe institutions); deployment specific extensions.
Built on top of Nuxeo Core.
Encouraging community to develop features and functions that meet local needs then contribute back.
Sustainability – museum-centric, but not only museums. Broad, deep and sustained are the terms they’re thinking of. Working on six profiles: Historical artifacts and popular culture, art centers/contemporary art, fine art, anthropology, and two more.
http://saas-demo.collectionspace.org
ArchivesSpace: Katherine Kott, David Millman
Funded by Mellon to build a next gen archives management tool. Community effort led by libraries of NUI, UIUC, and UCSD.
Technical framework – separate UI and back end, with REST service interface.
Scheduled for initial release in June 2013.
Important to balance different kinds of communities: the community of archivists, and also archival developers. Using open forums to keep in touch. What kind of interoperability should they plan for? Migration needs are forcing thinking about APIs that help understand interoperability.
Sustainability – Organizational home at LYRASIS (largest membership organization serving libraries and info professionals in the US), known for its “local touch.” Provides sustanability through archivespace membership, hosted solutions, help desk services, software upgrades, and training.
Governance through memberships – charter memberships available soon, regular available fall of 2013.
Looking for an organizational home for the effort.
Oren Sreebny 