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]. 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.
