spotlight icon indicating copy to clipboard operation
spotlight copied to clipboard

upgrading from 0.34.1 to latest

Open davezuckerman opened this issue 6 years ago • 3 comments

Hi, I'm trying to upgrade our instance of Spotlight to the most recent version while maintaining all of our data. Is there a recommended upgrade path? There is an older ticket #1761 that Dan just closed that is very similar. For that we ended having to install the new version and manually migrate data into the new DB structure along with a whole lot of data manipulation etc.. It was not trivial at all.

What I've attempted so far is to jump to the next release 1.0.0 and ran into several problems.

I updated the Gemfile to reference spotlitght 1.0.0 along with other dependencies that needed to be upgraded

ran the migrations ran acts_as_taggable_on_engines:install:migrations ran spotlight:migrate_to_iiif[localhost] recompiled assets

The site comes up but several zoomable images are not found. It looks like some of the featured images were somehow pointing to non existent directories and image items within item pages are not even trying to look for the images.

Thanks, Dave

davezuckerman avatar Feb 08 '19 17:02 davezuckerman

Worth noting that there's no upgrade guide for 0.34.1 -> 1.1.0, which (to me) implies that it should "just work" — update the gemfile, bundle install, and go.

Do some tasks need to be run/re-run on every upgrade regardless of the release notes?

danschmidt5189 avatar Feb 08 '19 19:02 danschmidt5189

We try to be specific about particular migrations that you'll have to run on releases in the release notes (be-it traditional rails db migrations or custom data migrations that we've written).

FWIW, it will be best to upgrade from anything pre 1.0 to 1.0 first, and then migrate on from there. Sorry if that wasn't clear.

The data migration from pre-IIIF to IIIF compatible Spotlight is pretty tricky. I'm not 100% sure all the cases in which it might not work. The best advice that I can offer is to take a look over the code that is run during that migration as well as take a look at what things didn't get successfully migrated in your system to try and determine why. I would be happy to help you contribute work back to this migration script if you're able to uncover some cases that we've missed.

jkeck avatar Feb 08 '19 19:02 jkeck

We already (successfully) migrated to IIF as part of the 0.33.0 -> 0.34.1 upgrade. We also had to manually migrate some data — not 100% sure but IIRC some of the SirTrevor class hierarchies changed, so objects serialized pre-upgrade couldn't be unserialized post-upgrade.

RE: Release Notes — Good to know everything's doc'd. I suspected the 1.0 release was a major breaking point; sounds like we just need to get there. 😅

danschmidt5189 avatar Feb 08 '19 20:02 danschmidt5189