Transitioning from Omeka classic to Omeka S

edsilv 2016-07-09 13:44:34 UTC #1

Hi,

I’m evaluating whether to use Omeka S or ‘classic’ for an archival project.

Omeka Classic (2.x) and Omeka S will exist and be maintained side-by-side for the foreseeable future.

As ‘S’ is alpha software, I’m thinking that classic is the realistic choice right now. However, before investing in the platform I’d like to know for certain that there is a planned upgrade path from classic to ‘S’. ‘S’ seems to be the future direction for Omeka. Are classic and ‘S’ compatible long term?

patrickmj 2016-07-09 18:58:48 UTC #2

For a new project, Classic is the way to go right now. Classic and S will be maintained separately, in part because there will be no direct upgrade path from Classic to S. Their code and data model are completely different. So, if by ‘compatible’ you mean a direct upgrade (like there was from Omeka 1 to Omeka 2), that will not happen. On the other hand, if by ‘compatible’ you mean that both will be maintained, then yes, both will see development work.

There will, however, be a module for Omeka S to import content from an existing Omeka Classic site via its API. That’s not a true direct upgrade, but it will grab large parts of the data from an Omeka Classic site and duplicate it in a new Omeka S site.

edsilv 2016-07-10 13:58:55 UTC #3

That’s great to know, thanks!

JorisLambrechts 2016-07-25 09:53:32 UTC #4

Hello,

We’re having the same issue, we were waiting for a stable omeka s (to make use of the new features) to start one of our newer projects but are now considering to just use classic instead since time is running short.

But can you guess when a stable version of omeka s, fit for production, is going to be released? Or is it still to early for that.

schultzmgvsu 2016-08-05 17:19:49 UTC #5

I would just like to echo a request for a rough timeline on a beta launch. Any information that the core contributors can add to the forum or websites would help sites with their local testing/implementation planning.

https://omeka.org/blog/2015/10/15/get-your-fresh-omeka-s-alpha-here/
http://omeka.org/about/roadmap/

sharonmleon 2016-08-05 18:59:59 UTC #6

We’re targeting October for a beta release, but we do package a monthly alpha that you can get started with:

ives1227 2016-09-27 15:22:58 UTC #7

We currently have a few exhibits set up in Omeka classic and are looking at Omeka-S.

Will the plugins that currently exist in Omeka Classic be moved to modules eventually? I see the list of projected module releases for October and November but I do not see the OAI-PMH Harvester as one potential module.
Furthermore, how will theming work? We developed a custom theme for our current exhibits/collections and will want to bring it over as well. Will this be possible?

patrickmj 2016-09-27 17:58:52 UTC #8

Many of them will be, or the functionality will be incorporated into the core. I don’t think OAI-PMH Harvester is on the short- or long-term plans right now, though. The list you cite is the best guide.

Theming (like everything else) will work on a very different system, so your custom theme would need to be rewritten.

Omeka Classic and Omeka S will both continue to exist alongside each other for the foreseeable future.

LibbyS 2016-12-12 03:08:10 UTC #9

Hi Patrick

We are really impressed by the enhanced features of Omeka S however we need to import records into Omeka from our other systems - AtoM and Eprints

We love how easy the Omeka Classic OAI-PMH plugin makes this process.

I think we could import items from AtoM and Eprints using the Omeka S, CSVimport module, however I was wondering if there is an easier way that I am missing?

Thanks for any advice. Libby

patrickmj 2016-12-13 19:59:42 UTC #10

If you can get the data into CSV, the CSVImport module will be your best bet,