Category «Technical Information»

Documentation

Link to Google Doc pages describing this implementation. Link to the project’s GitHib.

There’s four five different ways to get your repository’s EAD files to us: Submit via a Google form (a Google account is required) – https://forms.gle/XXBvqoesmtztdCgQ7 For non-Google users, here’s an alternative (must submit one file at a time) – https://wcsu.libwizard.com/f/EAD_nonGoogle Set up a drag and drop folder using WebDav – CAO network folder set-up ArchivesSpace …

Analytics

CAO utilizes Matomo to monitor usage of the site. It, like ArcLight, is open source. If you’d like to see usage statistics, just let us know, and we’ll send you a report. Privacy policy

Add a CAO search box to your site

Simply insert the above code into your site to add a search box for CAO! Where the code above says: “Western Connecticut State University Archives and Special Collections”, paste your repository’s name exactly as it appears on the CAO’ repository list (http://archives.library.wcsu.edu/arclight/caoSearch/repositories/) This will create a search box that searches your finding aids in CAO.

Create EAD

CAO offers participating repositories for no fee the option of using our instance of ArchivesSpace. ArchivesSpace is a tool that will export EAD and its fairly easy to use even if you don’t know what EAD is. https://archives.library.wcsu.edu/cao_archivesspace If you would like to take advantage of this service, just let us know and we will …

Coding Conventions

CAO has a few simple required coding conventions for the EAD finding aids that it searches. The requirements below ensure that CAO functions as intended. None of these coding conventions run contrary to best practices for DA:CS or EAD. EADs that are indexed in CAO must be “well-formed” and valid (either against the 2002 schema …

Helpful archival support software