Omeka

One of the nice features of a dynamic website—the kind of thing that’s often driven by databases—is the ability to run a search feature. Search is a feature across the various content management systems we use (or once used) at RRCHNM – Omeka, Drupal, and Wordpress. But once a site is flattened and no longer reliant on a database for serving content, the built-in ability of search goes away. For many of our sites, the loss of this feature can be dismaying to users. So, a goal this summer was to figure out a way to implement search on a static site.

As part of RRCHNM’s sustainability efforts, we are flattening websites built with content management systems (CMS). In this context, “flattening” refers to the conversion of dynamic, database-based websites to static, simplistic versions. A flat website is built only with HTML, CSS, and JavaScript. Flattening websites involves accepting different trade-offs. While the flattened versions save server space and reduce security threats, they lose dynamic features such as queries or user-input. A search function is a key site feature that is lost with flattening. A static site search remedies this.

The Bracero History Archive was an early Omeka site built by RRCHNM. The project itself was a collaboration between multiple institutions. It brings together artifacts and oral histories from the Bracero program of the mid-twentieth century. In addition to being a significant digital history project in terms of collaboration, the official curriculum of the state of California requires students to learn about the Bracero Program and teachers frequently use this project for that purpose. This is a site that needs to stay live and functional.

One of the projects which came to the sustainability team was The September 11 Digital Archive. Although I (Megan) had not previously been officially involved with the project, I had been part of projects and conversations which touched on or included the site (specifically the Omeka Classic plugins for topic modeling). I also had some experience with other community collecting projects, including concerns over privacy and harmful language in relation to contributions.

Some of the older sites – orphaned and not – which we had to deal with fell into a category which can loosely be called “Antique Omeka sites”. These sites were created mostly before 2011, and ran versions of Omeka Classic from 0.8 through 1.2.

The challenge with these sites was that they could not be easily upgraded to current versions of Omeka Classic. As of 2022, sites running Omeka Classic 1.2.1 or higher can be upgraded straight to the latest version, but earlier versions of Omeka Classic need additional work because of changes in the database and file structures.