Skip to main content
v2026.11,986 entries · CC-BY 4.0

Omeka S: What It Is, Requirements and How It Works

Omeka S is an open-source platform for publishing digital collections as linked data across many sites. Requirements, install steps and how it is organised.

Written and maintained by CASRAI Editorial Board

Published

On this page

Omeka S is a free, open-source web publishing platform that lets libraries, archives, museums and university projects publish digital collections and connect them with other online resources. Unlike a single-site content system, one Omeka S installation can create and manage many separate public sites, each drawing on a shared pool of items described with linked-data vocabularies. It is developed by the Digital Scholar organization, which runs the Omeka project, and it is released under the GNU General Public License.

What is Omeka S?

The project describes Omeka S as a publishing platform that helps institutions connect digital cultural heritage collections with other online resources. In practice that means a team loads items (a photograph, a letter, an oral-history recording, an artefact record), describes them with metadata, and then presents selections of those items on public websites that look and navigate differently from one another.

Three design choices set it apart from a conventional website builder. First, one installation can create and manage many sites, so a university library can host dozens of faculty exhibits from a single administered system. Second, items can be published as linked open data, which makes the descriptive metadata machine-readable and reusable outside the site. Third, behaviour is extended through modules (for mapping, collecting, importing and connecting to other services) and appearance through themes, with each site free to choose a different responsive theme.

George Mason University’s library guide to Omeka S explains the motivation: the platform was developed after requests for a version that supported the needs of larger institutions, offering a single point of administration for installing, upgrading and extending the functionality and appearance of all the sites it hosts. For research offices and digital humanities centres, that central administration is the reason to prefer Omeka S when many project teams each need their own public site but the institution wants one system to maintain.

How Omeka S organises content: items, item sets, vocabularies and resource templates

The Omeka S user manual groups the resource side of the platform into five concepts. Understanding them before loading any data saves rework, because the choices made here govern how every record is described.

Items and media

An item is a single described object or record, and media are the files attached to it, such as images, audio, video or documents. Descriptive fields are filled in once on the item, not once per site.

Item sets

An item set is a group of items that belong together, for example a letters collection or a field-survey archive. Item sets are a way to organise the shared pool, and individual sites then choose which item sets or items to display.

Vocabularies

Descriptive properties come from vocabularies, the controlled sets of terms used to label metadata fields. Omeka S ships with common RDF vocabularies, and this is what makes linked-data publication possible: each field is tied to a published property rather than to a free-text label. If your project already follows Dublin Core, those properties are available out of the box, and the CASRAI guide to a worked Dublin Core metadata record shows how such a record is built.

Resource templates

A resource template is a reusable form that specifies which properties an item should carry. The project notes that resource templates help describe items so that they can be shared with aggregators such as the Digital Public Library of America (DPLA). A template enforces consistency across a team, which matters when several people catalogue the same collection.

Sites, pages, navigation and themes

The Sites section of the manual covers site pages, navigation, resources, site users and themes. Each site has its own pages and navigation menu, its own list of resources drawn from the shared pool, and its own set of users. Because site users are managed per site, a project team can be given control of its own exhibit without being given control of the whole installation. The theme can differ for each site, so a museum exhibit and a scholarly edition hosted side by side do not need to look alike.

Modules

Modules add capability. The manual’s Modules section lists, among others, Exports, Hierarchy, IIIF Presentation and CSV Import. Import modules matter most when a project already has data elsewhere: the Omeka Classic Importer, the Omeka S Item Importer and CSV Import are the documented routes for bringing in existing records. A team with a spreadsheet of catalogue entries typically prepares the sheet against its chosen vocabulary properties and loads it through CSV Import rather than keying records by hand.

Omeka S for digital humanities projects

Omeka S is most often chosen where a project needs a durable, citable public presentation of a curated collection and where metadata quality is part of the scholarly output. Typical research-practice questions it raises are the same ones a data management plan asks: who maintains the system after the grant ends, which metadata standard is used, how are items identified over time, and what formats are preserved. Funders that ask digital humanities applicants for data management plans, such as the programme described in the CASRAI guide to NEH data management plan requirements for digital humanities grants, expect those answers in writing. Using vocabularies that publish stable properties, and pairing items with a persistent identifier where your institution provides one, are the practical steps that connect an Omeka S site to those expectations. If the project will result in an article, the venue question is separate; see the guide to Digital Humanities Quarterly for one example.

Omeka S system requirements

The install page of the user manual sets out the server environment. The data table below compares each requirement with its stated minimum. Three points deserve emphasis for anyone planning hosting. The manual specifies a Linux server for production, with Windows and Mac described only for development and training through packages such as WAMP and MAMP. Apache must allow overrides (AllowOverride All) and have mod_rewrite enabled. Thumbnail generation depends on an image library: ImageMagick (through the imagick extension) handles more than 200 formats, while the GD library handles JPEG, GIF and PNG only, so collections with TIFF or other archival formats need ImageMagick.

For a research office assessing a project proposal that names Omeka S, the table translates into a short set of questions for the hosting team: whether the server runs Linux with Apache and the rewrite module, whether the database version meets the stated minimum, whether PHP is at 8.1 or later with the listed extensions, and which image library is installed. Answering these before a grant is submitted avoids budgeting for a hosting environment that cannot run the software. The version lines also matter over time, since a server that meets the minimum today may need a PHP upgrade before a later Omeka S release can be installed.

How to install Omeka S

The documented installation sequence is short, and each step is a point where institutional IT support is usually needed.

  1. Download a release of Omeka S.
  2. Create a dedicated MySQL or MariaDB database and a database user for it.
  3. Edit config/database.ini with the database connection details.
  4. Upload the files to the web server and make the files/ directory writable by the Apache user.
  5. Visit the /admin address of the installation to create the first user and set the installation title, time zone and locale.

The manual also notes that Softaculous and Installatron, the one-click installers offered by many shared hosts, support both Omeka Classic and Omeka S. Releases are listed on the project’s GitHub releases page, where the most recent entries at the time of the last check were versions 4.2.1, 4.2.0 and 4.1.1. Version 4.2 is the first release the manual lists as supporting PHP 8.4.

Omeka S compared with Omeka Classic

The same organisation maintains the original Omeka, usually called Omeka Classic. Omeka S is the version aimed at institutions that need many sites and linked-data publishing under one administration, and the platform provides an Omeka Classic Importer module so that existing Classic collections can be moved across. Because the two products are separate installations with their own themes and add-ons, a project should confirm that any theme or plugin it depends on exists for the version it chooses before committing.

Common planning mistakes

  • Choosing a vocabulary after loading records. Properties are attached to items, so changing the metadata model late means editing records in bulk.
  • Treating the installation as a single project. Because one installation hosts many sites, retention, backup and upgrade responsibility should be assigned to the institution, not to the first project team.
  • Planning thumbnails without checking the image library. A server limited to GD will not derive thumbnails from formats outside JPEG, GIF and PNG.
  • Skipping resource templates, which leaves each cataloguer to decide which fields matter and produces uneven records.

Sources

Data: Omeka S server requirements and stated minimums

Server-side requirements for installing Omeka S, compiled from the project's official user manual install page and reduced to one row per component with its stated minimum or constraint.

Omeka S server requirements and stated minimums
ComponentStated requirementNotes
Operating systemLinuxWindows and Mac are described for development and training only (WAMP, MAMP)
Web serverApacheAllowOverride All and mod_rewrite enabled
DatabaseMySQL 5.7.9 or later, or MariaDB 10.2.6 or laterA dedicated database and user are created during installation
PHPPHP 8.1 or laterPDO, pdo_mysql, mbstring and xml extensions; PHP 8.4 supported from Omeka S 4.2
Image library: ImageMagickImageMagick 6.7.5 or later via imagickHandles more than 200 formats
Image library: GDGD extensionJPEG, GIF and PNG only
Writable directoryfiles/ writable by ApacheRequired for uploaded media and thumbnails

Sources

Compiled by CASRAI from the sources above. Free to reuse under CC BY 4.0 with attribution.

Follow CASRAI

Research-administration guidance, standards updates and independent tool reviews.

Ask CASRAI · free to try

Ask about Omeka S: What It Is, Requirements and How It Works

2 free questions a day, no account.

An AI assistant for research: funder rules, compliance, methods and publishing. It links the sources behind its answers and labels answers that come from a web search.

Answers draw on CASRAI's guides and dictionary plus the federal and funder documents we index: Federal Register, Grants.gov, Regulations.gov and UKRI.

Works on this site and inside Claude, Cursor and the AI tools you already use.

Everything CASRAI publishes — this page, the dictionary, the guides and the news — stays open to read, with no account and no card.

Referenced across the research world

University of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logoUniversity of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logo
  • University of Cambridge logo
  • Columbia University logo
  • Crossref logo
  • University of Edinburgh logo
  • Harvard University logo
  • University of Oxford logo
  • Princeton University logo
  • Stanford School of Medicine logo
  • University College London logo
  • ORCID logo

View CASRAI adoption →