A CollectiveAccess Community

User-generated tips, tools, and shared strategies for using CollectiveAccess

Other Resources

Do you have a resource you’d like to suggest we add to this page? Let us know! Post it as a suggestion in the CollectiveAccess community GoogleGroup.

Documentation written by Whirl-i-Gig
User-Created Workflows
CollectiveAccess On Github
  • CollectiveAccess: A Walkthrough. A Github page that offers a user-friendly guide to the structure and mechanisms that drive CollectiveAccess. The document explains, in accessible language, how to install CA, how to import data, and how to manipulate fields. It uses Chicago Film Archives as an example case, and makes available a set of sample data that users can practice with, as well.
  • Omeka_Sync. A  tool for syncing data from CollectiveAccess to Omeka, created by folks at the University of Leuven in Belgium.
  • Interference Archive’s Github Page.  Where Interference Archive volunteers post scripts for managing their CollectiveAccess database. Currently there is a CollectiveAccess API client with more to come soon.
  • Rhizome’s ArtBase CollectiveAccess Profile on Github. This is a Collective Access configuration profile developed for the Rhizome ArtBase.
  • Official CollectiveAccess Github page. This is where the CollectiveAccess development team manages project source code.
  • Ansible Provisioning for CollectiveAccess. A guide to using Ansible for  installation and configuration of a CollectiveAccess instance.
Video Instructionals
A Selection of Sites Built on CollectiveAccess
CollectiveAccess User Groups
Essays about CollectiveAccess
  • Rhonda L. Clark, “Challenges in Representing Local Image Collections: The Case of the Titusville Historical Society,” Cases on Electronic Records and Resource Management Implementation in Diverse Environments, ed. Janice M. Krueger (Hershey, Pennsylvania: Information Science Reference, 2014). Discusses the decision-making process in selecting software for presenting local history and genealogical collections. The institution discussed in the article ultimately selected Omeka over CollectiveAccess.
  • Sven Decabooter, “Case Study: James Ensor: An Online Museum” March 2, 2011. Describes the author’s experience deploying Drupal as a front-end for CollectiveAccess.
  • Juliet L. Hardesty, “Exhibiting Library Collections Online: Omeka in Context,” IUScholarWorks  This article primarily discusses Indiana University’s use of Omeka. It briefly discusses CA and compares it with other software used for exhibiting collections. A chart compares several existing pieces of software including Archivists’ Toolkit, Islandora, and ContentDM.
  • Kehan Harman, “Adding Australian National Species List Names to CollectiveAccess” November 4, 2015. This article describes a project for the Commonwealth Scientific and Industrial Research (CSIR) in Australia completed by Gaia Resources (an environmental technology consultant). CSIR configured CollectiveAccess to reference external authoritative data sources. The article includes screenshots that demonstrate how to configure fields.
  • Ruben Alcaraz Martinez, “Collective Access: A Collections Management and Presentation System for the Digital Collections of Museums, Archives and Libraries,” BiD: Textos Universitaris De Biblioteconomia i Documentació, no. 33 (2014).  An article about CollectiveAccess written in Catalan. Describes  the main features of CollectiveAccess, explains how to install and configure the package, examines CA’s internal structure, and gives examples of how it can be used. The system analyzed in the paper uses Version 1.4 of Providence and Version 2.0 of the public web-access tool Pawtucket.
  • Isabel Pedersen and Jeremiah Baarbe, “Archiving the ‘Fabric of Digital Life’,” IEEE International Symposium on Mixed and Augmented Reality – Arts, Media, and Humanities (ISMAR-AMH), (2013), 1-6. Discusses using CA to create a database that “tracks, catalogues, and in some cases, stores artifacts that imply future invention.”
  • Dean Rehberger, “Getting Oral History Online: Collections Management Applications,” Oral History Review, no. 1 (2013). This article discusses using CA as a digital asset management system.
  • Andres Solano, “GVSU Art Gallery Meets iOS: How to Cram 10K+ Works of Art into Your Pocket” (Masters Thesis, Department of Computer Information Systems, Grand Valley State University, 2011). Describes the creation of an iOS app to grab data from a CA server for use in a mobile phone app. (For more about the mobile app, visit the info page on GVSU Art Gallery’s website.)
  •  Lisa Spiro, Archival Management Software: A Report for the Council on Library and Information Resources (2009).  Discusses the role of software in providing access to previously “hidden” collections. Compares several pieces of archival management software (both commercial and open source) including CollectiveAccess, Archon, and Archivists’ Toolkit. It also provides advice on how to select appropriate archival management software.
  • Elizabeth Surles, “‘Exploring’ CollectiveAccess at the American Alpine Club Library.” From Practical Technology for Archives, an open access, peer reviewed journal. This article describes the work of the American Alpine Club Library to implement CollectiveAccess for their institution and using CA as a Digital Asset Management (DAM) system. It also includes a review of the existing literature on CA.
  • Julia J. Weist, “Implementing CollectiveAccess at the Bruce High Quality Foundation University Archive.” Visual Resources Association Bulletin, (2010), 37(2), 23-26. An article about the work of creating a Bruce High Quality Foundation University (BHQFU) Archive. Topics addressed include cataloging archival materials, software features of the project, and the use of CollectiveAccess software.