CollectiveAccess

CollectiveAccess
Name	CollectiveAccess
Programming language	PHP, MySQL, JavaScript
Operating system	Cross-platform
Genre	Collections management, Digital asset management
License	Open-source (GPL)

CollectiveAccess CollectiveAccess is an open-source collections management and digital asset management system designed for museums, archives, libraries, galleries, and cultural heritage projects. It provides tools for cataloging, metadata management, digital preservation, and public discovery, supporting institutional workflows across organizations such as Smithsonian Institution, British Library, Library of Congress, Metropolitan Museum of Art, and Museum of New Zealand Te Papa Tongarewa. The software has been used in projects involving standards and institutions like Dublin Core, Encoded Archival Description, Getty Research Institute, Europeana, and Digital Public Library of America.

Overview

CollectiveAccess is a configurable web-based application that combines cataloging back-end features with front-end public access, enabling interoperability with systems such as Omeka, AtoM, Islandora, Fedora Commons, and Drupal. It supports standards and vocabularies applied at institutions including Getty Vocabulary Program, Library of Congress Subject Headings, MARC 21, EAD 2002, and CDWA Lite. Cultural heritage projects at organizations like Yale University, University of Oxford, Harvard University, Princeton University, and Cornell University have used CollectiveAccess for digital exhibitions, research portals, and archival access.

History and Development

The project originated in the early 2000s, influenced by initiatives at institutions like The New York Public Library, National Archives and Records Administration, Australian National Library, and Canadian Museum of History. Development milestones reflect contributions aligned with standards bodies such as International Council on Archives, CIDOC Conceptual Reference Model, OCLC, and JSTOR. Funding and partnerships have involved organizations like Andrew W. Mellon Foundation, Institute of Museum and Library Services, National Endowment for the Humanities, Wellcome Trust, and regional consortia including DPLA Hub Network members. Implementations and customization efforts have been documented alongside projects at University of British Columbia, University of Toronto, University of Melbourne, University of Sydney, and National Library of Scotland.

Architecture and Technical Features

The application is built with PHP and relies on databases such as MySQL and MariaDB running on platforms including Linux, Windows Server, and macOS Server. Its architecture emphasizes modularity with components similar to patterns in Model–View–Controller frameworks and tools aligned with Apache HTTP Server, NGINX, and Composer (software). Technical integrations have been implemented with services such as IIIF Image API, OAI-PMH, SRU/SRW, and authentication systems like LDAP, OAuth, and Shibboleth. Scalability and deployment practices reference infrastructure used by Amazon Web Services, Google Cloud Platform, Microsoft Azure, and containerization approaches like Docker.

Data Model and Metadata Support

CollectiveAccess provides a flexible data model supporting object types, relations, persons, organizations, places, and events, interoperating with standards such as Dublin Core, EAD, MARCXML, MODS, METS, and PREMIS. Controlled vocabularies from sources like Getty Thesaurus of Geographic Names, Library of Congress Name Authority File, FAST, and Union List of Artist Names can be integrated. Implementations have used mapping workflows similar to those in projects at Europeana Data Model adopters and repositories managed by Scholarly Publishing and Academic Resources Coalition members.

User Interface and Workflows

The interface includes an administrative back-end and configurable public front-end with templates for cataloging, batch editing, and media management. Workflows accommodate roles and permissions modeled after practices at Smithsonian Institution Archives, The National Archives (UK), British Museum, and Victoria and Albert Museum. Features such as bulk import/export, batch digitization support, and editorial review align with digitization projects run by National Gallery of Art, Tate Modern, Guggenheim Museum, and Los Angeles County Museum of Art.

Deployment, Customization, and Integration

Deployments range from small heritage organizations to large research libraries, with customization layers for branding, discovery, and APIs. Integrations have been performed with content management systems like WordPress, Drupal, and Joomla!, and with discovery platforms such as Blacklight, VuFind, and Solr. Preservation and storage integrations reference LOCKSS, Archivematica, DSpace, and cloud storage providers used by Internet Archive collaborations.

Use Cases and Implementations

CollectiveAccess has been used for museum collections, photographic archives, oral history projects, and university special collections at institutions including Getty Museum, Museum of Modern Art, Royal Ontario Museum, National Museum of Korea, and Smithsonian Institution Libraries. Notable projects have incorporated workflows from World Digital Library, Europeana Collections, Digital Public Library of America, National Digital Information Infrastructure and Preservation Program, and consortia such as HathiTrust.

Licensing, Community, and Support

Released under open-source licensing compatible with initiatives like Free Software Foundation principles, CollectiveAccess has an ecosystem of developers, implementers, and vendors. Community support and training have come from professional networks such as Society of American Archivists, International Council on Museums, Museum Computer Network, Association of Research Libraries, and regional groups like Digital Libraries Federation. Commercial support providers and open-source contributors collaborate in code repositories and at conferences including Code4Lib, MuseumNext, ALA Annual Conference, and IACR.

Category:Open-source software