Appearance
Choose Omeka Classic when you want one self-contained, exhibit-led website with the gentlest learning curve, and choose Omeka S when you need multiple sites from a shared item pool, native linked-data modelling, or institutional-scale reuse. They are separate products, not versions of each other: Classic descends from the original 2008 platform, while S was rebuilt from scratch around RDF and multi-site publishing. The decision hinges on whether you are building one story or one data layer feeding many stories.
What is the core architectural difference?
Omeka Classic is single-site: one installation equals one public website with its plugins and theme. Omeka S inverts this. One installation contains a shared pool of items, and you compose any number of public sites that each query that pool. If your department runs five small collections that should share authority records and media, S avoids five duplicate datasets. If you run exactly one project, Classic's simplicity is an advantage rather than a limitation.
How do their metadata models compare?
Classic uses the Dublin Core element set, extensible with item-type metadata, and stores values as plain text. Omeka S is RDF-native: every property comes from a named vocabulary, and you can mix Dublin Core, Bibliographic Ontology (Bibo), FOAF and custom vocabularies on a single resource template. That makes S far stronger for linked open data and crosswalking, at the cost of more upfront modelling.
text
Classic value: dc:creator = "Ada Lovelace"
Omeka S value: dcterms:creator -> URI https://viaf.org/viaf/76327385
(typed as foaf:Person, label "Ada Lovelace")Which is easier for building exhibits?
If your deliverable is a narrative exhibit with sections and captioned pages, Classic's Exhibit Builder plugin is purpose-built and intuitive. Omeka S assembles pages from configurable blocks (media embed, browse preview, HTML, item showcase). Blocks are more flexible and reusable across sites, but new users often find the narrative flow harder to picture at first. For a one-off story-led teaching exhibit, Classic still wins on speed-to-publish.
How do plugins and modules differ?
| Aspect | Omeka Classic | Omeka S |
|---|---|---|
| Extension term | Plugins | Modules |
| Multi-site | No | Yes, native |
| Data model | Dublin Core + item types | RDF, mixed vocabularies |
| API | REST (read-focused) | Full REST read/write |
| Exhibits | Exhibit Builder plugin | Page blocks |
| Active feature focus | Maintenance | Primary development |
The ecosystems do not share code, so a Classic plugin does not run on S and vice versa. Check that the specific extensions you depend on (Geolocation, CSV Import, Mapping) exist for your chosen platform before committing.
When does migrating from Classic to S make sense?
Migrate when you outgrow a single site, need linked-data URIs instead of text strings, or want an institution-wide shared pool. There is no automatic upgrade: you export items via CSV or the REST API and re-import into Omeka S, mapping each Classic field to a property in an S resource template. Budget time for cleaning Dublin Core values that were free text in Classic but should become reconciled URIs in S.
What is the decision in one paragraph?
One project, exhibit-first, small team, minimal modelling: choose Omeka Classic. Several projects sharing data, linked-data ambitions, an API-driven workflow, or institutional reuse: choose Omeka S and accept the steeper start. Both are open-source and free, so the real cost is the time you invest in the data model you commit to.
Key Takeaways
- Classic is single-site and exhibit-led; S is multi-site with a shared item pool.
- Omeka S is RDF-native and mixes vocabularies; Classic uses a fixed Dublin Core element set.
- Classic's Exhibit Builder is faster for one narrative site; S blocks are more flexible.
- Plugins and modules are not interchangeable between the two platforms.
- Migration is a CSV/API export-and-remap, never a one-click upgrade.
- New active development targets Omeka S, but Classic remains maintained and stable.
Frequently Asked Questions
Is Omeka Classic discontinued?
No. Omeka Classic is still maintained and receives security updates, but new feature development is concentrated on Omeka S. Treat Classic as stable-but-mature rather than dead.
Can one Omeka S install host several distinct project sites?
Yes. Omeka S is multi-site by design: a single installation holds one shared item pool and you build many independent public sites from it, which Classic cannot do natively.
Does Omeka S support linked open data better than Classic?
Yes. Omeka S is built around RDF and lets you mix vocabularies like Dublin Core, FOAF and Bibo per property, whereas Classic uses a fixed Dublin Core element set with extensions.
Which platform has the simpler exhibit builder?
Omeka Classic, through its Exhibit Builder plugin, offers the gentler narrative-exhibit experience. Omeka S builds pages from blocks and is more flexible but has a steeper learning curve for storytelling.
Can I migrate an existing Omeka Classic site to Omeka S?
There is no one-click upgrade. You migrate by exporting items to CSV or via the API and re-importing into Omeka S, remapping Classic's Dublin Core fields to S resource templates.
Which one should a single small archive choose today?
If you need one narrative-driven public site and minimal setup, Classic is fine. If you expect multiple sites, linked data, or institutional reuse, start on Omeka S.