Omeka Workshop

Overview & Resource Links

Lehigh University, September 8, 2017

Why use Omeka instead of something else?

  • Collections based projects
  • Items as building blocks
  • Digital exhibitions curated from your items
  • Searchable database with metadata and tags
  • Plug-ins designed by digital humanists
  • Made for humanities and cultural heritage projects

Wait, which Omeka should I use?

Omeka (classic): This is the Omeka software that one needs to install on a server (“self-hosted”). It is the truly open source version, in that savvy users can tweak it to do with what they want.

Omeka.net: Omeka.net is “hosted” Omeka in that you work completely in the cloud and do not need to worry about having a server. It is less flexible than “self-hosted” Omeka and requires a annual subscription.

Omeka S: “Omeka S is a free & open source platform for institutions that want to publish linked open data; integrate their collections with the scholarly communications ecosystem; and manage many users & sites from one installation.”

Where should I host Omeka?

I highly recommend Reclaim Hosting for your server needs, especially if you do not have institutional support. Reclaim has designed their products with academia, students, and small organizations in mind. With one-click installation you can have Omeka or many other open source platforms up and running in no time, all for super low annual hosting rates. I have never experienced such supportive customer service.

Goin’ North: Stories from the First Great Migration to Philadelphia


Classroom/archive collaboration

Items “borrowed” from numerous regional repositories

Students created metadata

Students used items as building blocks

Students used items to curate exhibits

Embedded OHMS indexes on Simple Pages

Custom designed Simple Pages

Why should I NOT use Omeka

  • Less flexible design options than other options, unless you are willing to custom code
  • Steeper learning curve
  • Great for collections and items, but the equivalent of simple pages is achieved better elsewhere
  • Dublin Core metadata can be confusing for non-specialists
css.php