Bram- Thank you for your response! This is very helpful. Our DSpace instance is not yet live, so we're thinking this is a good time to learn about the upgrade process and get up to the latest version.
1) Could we ask a followup question: What should we be worrying about in terms of backing up our instance pre-upgrade? Since we don't have to worry about going offline we're planning on creating a restore point, then reverting back if we run into anything we can't tackle. Given this approach, are there any hazards in particular we should take care to avoid? 2) The customizations one has made to the config file must be manually merged with the new version's config file, correct? What is the best way to do this? Just replace the old file completely. Forgive me if I'm misunderstanding something. Again, thank you for your help. -Gabe - On Monday, February 4, 2019 at 11:43:29 AM UTC-5, Bram Luyten wrote: > > Hi Gabe, > > not a trivial question and likely what I'm about to write will only > provide a partial answer at best. > In very short, bumping up to a new minor release should be doable, and the > sooner you get the hang of this, the better. I would recommend to > persevere, so you can ideally re-play the process once 6.4 or 6.5 comes > along. > Generally, no major feature changes are introduced in minor releases, only > fixes. Security related fixes, depending on severity, can be key to keep > your repository safe. > > *DSpace upgrade documentation* > > If the upgrade page at > https://wiki.duraspace.org/display/DSDOC6x/Upgrading+DSpace looks > daunting, it's because it's written from the perspective to allow anyone to > upgrade from any previous MAJOR version of DSpace. > That's the main reason why there are so many steps and things to check. > > If we were to write a page, specifically on bumping to a new minor > version, I imagine we could simplify it substantially. > > *What you need to do depends on how you did your installation and > customizations* > > If you started from the binary release (Zip download > dspace-6.2-release.zip), you should have less individual files locally, > compared to an installation from the SOURCE release > (dspace-6.2-src-release.zip) or by forking GitHub. > If you are working with the source release, and made customizations in > different places, one view that could be useful is the compare view, that > allows you to see all changes between 6.2 and 6.3, on a per file basis: > https://github.com/DSpace/DSpace/compare/dspace-6.2...dspace-6.3 > > When it comes to configuration, we keep our server/environment specific > variables in maven profiles, instead of filling them out in the actual > configuration files. > A guide that covers this to some extent is available here: > https://youtu.be/mrLl1qPsy6I This was originally for DSpace 5, but most > principles apply to DSpace 6 as well. > > Overall, when your config and code changes are managed in Git, you can > re-base these changes on the 6.3 branch, and redeploy. > > Hope this helps, > > Bram > > [image: logo] Bram Luyten > *250-B Luci*us Gordon Drive, Suite 3A, West Henrietta, NY 14586 > Gaston Geenslaan 14, 3001 Leuven, Belgium > atmire.com > <http://atmire.com/website/?q=services&utm_source=emailfooter&utm_medium=email&utm_campaign=braml> > > > On Fri, 1 Feb 2019 at 22:01, <[email protected] <javascript:>> wrote: > >> Group- >> >> We're building out a new DSpace IR (which isn't yet live) and are >> considering an upgrade from 6.2 to 6.3 >> <https://wiki.duraspace.org/display/DSDOC6x/Upgrading+DSpace>, mainly >> because we want ORCID integration >> <https://wiki.duraspace.org/display/DSDOC6x/ORCID+Integration> as an >> option. We're weighing the pros and cons, but finding it hard because >> we're not sure how much of our site's external integrations and internal >> customizations we'll lose or need to redo post-upgrade. Most of these >> required troubleshooting when initially configured, and we're working with >> a small team with no dspace experience, so we're not eager to have to >> reconfigure them. Forgive my ignorance! >> >> Will the following, all of which we've enabled, break post upgrade? >> >> --SWORDv1 connection to ProQuest through which ETDs are delivered >> --SWORDv2 through which objects from Symplectic Elements are delivered. >> --OAI endpoint >> --Will our config file need to be redone? >> >> *A concrete example:* will we need to manually reinstall the SWORD >> endpoints, or will they remain in place? If we do need to reinstall them, >> how would we port over the local configurations we've made to >> swordv2-server.cfg? >> >> Thank you for any insight you can provide. Sorry if these questions are >> misguided or a bit stupid! Any insight you can provide would be much >> appreciated. >> >> -Gabe >> >> -- >> All messages to this mailing list should adhere to the DuraSpace Code of >> Conduct: https://duraspace.org/about/policies/code-of-conduct/ >> --- >> You received this message because you are subscribed to the Google Groups >> "DSpace Community" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> Visit this group at https://groups.google.com/group/dspace-community. >> For more options, visit https://groups.google.com/d/optout. >> > -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- You received this message because you are subscribed to the Google Groups "DSpace Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-community. For more options, visit https://groups.google.com/d/optout.
