Migrating from Omeka.net to Omeka on Reclaim Hosting


#1

Omeka.net is a hosted platform for running Omeka. Due to the managed nature of that environment it’s not possible to run your own plugins and themes on that platform and so you may wish to get an account at Reclaim Hosting and run Omeka here. This guide is on how to take the work you’ve done at Omeka.net and migrate.

The first step is to install Omeka on Reclaim Hosting and we have a guide here that walks you through that process. This guide assumes you have installed Omeka on your hosting account and want to now migrate information from Omeka.net over.

It’s a good idea to make sure your ImageMagick path and PHP-CLI path are both setup properly.

ImageMagick in Omeka

Setting the PHP-CLI path in Omeka

You can also take this opportunity to update some of the general settings and theme of your new Omeka installation. The import will only bring over Items, Collections, Exhibits but not other settings or theme information. For the import process you’ll need the Omeka API Import plugin installed. You may also want to install any other plugins or themes you might wish to use. Here is a guide to installing plugins in Omeka Uploading Plugins to Omeka.

On your install at Omeka.net, go to the admin area and click Settings > API. Here you will need to check a box to enable the API and click Save Changes which will allow the export to work.

You’ll then need to navigate to the Users area (still on your Omeka.net install) and click API Keys under a user with super-admin privileges. Here you will create an API Key giving it a recognizable label (this can be anything). You’ll need this API Key for the import process.

You’re now ready to import your Omeka.net site over to your Omeka install at Reclaim Hosting. Make sure the Omeka API Import plugin is activated and that you’ve followed every step in this guide prior to this point. You’ll see the API Import menu item in the lefthand sidebar of your Omeka install in the admin area. Navigate there and you’ll find two settings to enter, an API URL and an API Key, along with the option to override data.

Your API URL takes the format of https://yoursiteon.omeka.net/api so enter that along with the API Key created on your Omeka.net install previously. Since this is a new install we don’t have override anything so I’ll leave the last box unchecked. As the import progresses you’ll get messages on the same page with the option to click to refresh:

The time it takes to import will be wholly dependent on how much content is being migrated. When the import completes you should have all of the content from your Omeka.net site within your install at Reclaim Hosting.


#2

Thanks for this documentation. I’m having trouble with the import process stalling at seemingly random places. I have about 3000 items on my omeka.net site, and though the API import starts well, it just hangs at somewhere between 30% and 65% of the total items.

ImageMagick and PHP-CLI paths are both set up properly, and I’ve tried both increasing and decreasing the API results per page on the origin site, as well as removing all other plugins on both sites.

I’d be grateful for any ideas on how I can get it running better.


#3

I actually ran into a similar issue where I was importing a large library and had a conversation with an Omeka developer and this was the fix they provided that worked for me, maybe it will work for you? (I don’t know if line numbers have changed on the file as this was a year and a half ago)

In OmekaApiImport/libraries/ApiImport/ImportJob/Omeka.php around line 79 it sets the first page of responses to $page = 1;

From what you describe, setting that to something higher might help. Hard to know exactly what page to start at – there might be info in the log for guidance. My import got to page 18 before my network connection crapped out, and that was about Item 907.

So, maybe hacking to start with page 18 or 20 or so would get around the timeout would work.


#4

Thanks for the quick response; I’ll give it a try and report back.


#5

This worked for me, too — thanks very much!