[Eagle-i-admins] 2.0-MS2.14 or 2.0-MS2.15?

[Tolmie, David A]

Thanks, Daniella.  So…  It turns out we're running 1.11, not 2.13.  So, I need to upgrade to 2.04, then 2.13, then 2.15.

Do I need to upgrade the repository at each step, or can I leapfrog the repository to 2.15, and just run the data migration from each incremental step?

If I were to treat this as a new install, with the URIs for all of our content changing, old ones vanishing, new ones appearing, would that break things on the Central side of things?

I'm just trying to wrap my brain around what I can and can't safely do.

Thanks!!

-Dave


From: <Bourges>, "Bourges, Daniela" <Daniela_Bourges at hms.harvard.edu<mailto:Daniela_Bourges at hms.harvard.edu>>
Date: Thursday, July 25, 2013 10:23 AM
To: David Tolmie <dtolmie at fhcrc.org<mailto:dtolmie at fhcrc.org>>, "eagle-i-admins at open.med.harvard.edu<mailto:eagle-i-admins at open.med.harvard.edu>" <eagle-i-admins at open.med.harvard.edu<mailto:eagle-i-admins at open.med.harvard.edu>>
Subject: Re: [Eagle-i-admins] 2.0-MS2.14 or 2.0-MS2.15?

Hi Dave,
In general data migration does not handle skipping a version – you need to get aggregate migration tables (which we usually prepare when people ask).

However, 2.15 is only a minor patch to 2.14 to correct a bug in central search. So in this particular case it doesn't matter – feel free to go from 2.13 to 2.15

Cheers
Daniela



Dr. Daniela Bourges-Waldegg
Lead Architect, Harvard Catalyst
Harvard Medical School

Daniela_Bourges at hms.harvard.edu<mailto:Daniela_Bourges at hms.harvard.edu>
skype: dbourgesw
phone: 617-432-3126


From: <Tolmie>, David A <dtolmie at fhcrc.org<mailto:dtolmie at fhcrc.org>>
Date: Thursday, July 25, 2013 12:37
To: "eagle-i-admins at open.med.harvard.edu<mailto:eagle-i-admins at open.med.harvard.edu>" <eagle-i-admins at open.med.harvard.edu<mailto:eagle-i-admins at open.med.harvard.edu>>
Subject: [Eagle-i-admins] 2.0-MS2.14 or 2.0-MS2.15?

Hi folks,

After I ran into issues with my first go of upgrading from 2.0-MS2.13 to 2.0-MS2.14, I rolled back to my pre-upgrade checkpoint.  I'm now going to make another go at upgrading, but I see a version 2.0-MS2.15 was released last week (7/18) and it's what's running on Central right now.

Does the data migration script handle skipping a version (i.e. Jumping from 2.0-MS2.13 to 2.0-MS2.15) cleanly?  Or, do I need to apply 2.0-MS2.14 before I can move to 2.0-MS2.15?

Thanks,

-Dave

________________________________
David Tolmie
Systems Librarian
Arnold Library | Fred Hutchinson Cancer Research Center | Seattle, WA
dtolmie at fhcrc.org<mailto:dtolmie at fhcrc.org>  |  tel 206.667.6852 |  fax 206.667.4737
[Description: Description: Description: Description: AL-Logo-color]<http://library.fhcrc.org/>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://open.med.harvard.edu/pipermail/eagle-i-admins/attachments/20130725/726be347/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 7FD5AC1E-A431-40DA-9401-C7BE8CFBB58C[10].png
Type: image/png
Size: 9103 bytes
Desc: 7FD5AC1E-A431-40DA-9401-C7BE8CFBB58C[10].png
Url : https://open.med.harvard.edu/pipermail/eagle-i-admins/attachments/20130725/726be347/attachment-0001.png