For those of us using Oracle as a database, we cannot upgrade beyond v.5.10 without altering the source release code of v.7.x, which carried over a Flyway bug from v.6.x that impacts Oracle users. In my academic library, we have no in-house developers who can alter the code, are hosted on-prem, and central IT does not support PostgreSQL, so a database migration is not an option for me.
Is my only option to migrate to a vendor-hosted DSpace v.7.x instance? Regardless, I know I have a migration of some kind in my future. I just want some bright-line confirmation here to report to my leadership. My understanding of the Flyway bug that has been part of the DSpace source release code since 2018, when v.6.0 was released (if memory serves, or at least, that's when I attempted to upgrade from v.5.4 to v.6.0 and ran into the Flyway bug), is that: (1) IF I could migrate my Oracle database to a PostgreSQL database, then I could upgrade to v.7.x. (2) BUT because central IT maintains the DSpace infrastructure at my institution and they support only Oracle databases, that means I must migrate to a hosted DSpace instance if my institution wishes to remain on DSpace for its IR. Please confirm my understanding above or tell me if I am overlooking a third option. Also, if anyone else is in the same boat as me--Oracle database user without in-house developers who can alter the Flyway part of the code, i.e., stuck on v.5.x, please let me know what you are doing or what steps your institution is taking to remedy your IR situation. Thanks very much! Karlen Chase Head of Institutional Repository Services UB Libraries State University of New York at Buffalo (University at Buffalo) On Tuesday, May 31, 2022 at 10:14:28 AM UTC-4 Tim Donohue wrote: > > > > > > > > > > > > > > * Dear DSpace Community, The DSpace Steering Group announces that security > support for DSpace 5.x and 6.x will end on the following dates: - DSpace > 5.x: Support ends on January 1, 2023 - DSpace 6.x: Support ends on July 1, > 2023 This means that after those dates: - That version of DSpace will be > considered “end-of-life” (EOL) - Future minor releases of that major > version will not occur - Bugs affecting those releases will not be > addressed - Security vulnerabilities affecting those releases will not be > addressed We recommend all institutions upgrade to DSpace 7 as soon as > possible. As we realize that both DSpace 5.x and 6.x are still in wide > usage throughout the community, we’ve attempted to answer all questions you > may have on our wiki > at > https://wiki.lyrasis.org/display/DSPACE/Support+for+DSpace+5+and+6+is+ending+in+2023 > > <https://wiki.lyrasis.org/display/DSPACE/Support+for+DSpace+5+and+6+is+ending+in+2023> > > If your question is not yet answered on that page, please add it in the > wiki page comments and we will ensure it is answered. Sincerely, The DSpace > Steering Group * > > -- All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx --- 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 view this discussion on the web visit https://groups.google.com/d/msgid/dspace-community/c42fc344-21a5-4312-b257-ea2fa60b00aen%40googlegroups.com.
