Good afternoon Tech Council,

Back in May we raised the need for having to have DB migration support whenever there are schema changes.  This is a critical need when deploying new versions to production for live clients.

At the time, Hongwei has worked on a spike to investigate how to implement db migration using RMB.  We then discussed and agreed that starting with Q3 release, module developers will provide DB migration support whenever there are module schema changes.  Unfortunately this was not enforced and fell by the wayside. Could we revisit this topic and agree to start enforcing this, for example by including DB migration support as acceptance criteria (meaning that in order for a PO to accept a story, they would need to verify that DB Migration support was developed).

As we were working on preserving data in our production sites, most specifically for Chalmers, we found quite a few problems that would have been avoided had we had db migration support.

For the upcoming TC meeting, could we please add this to the agenda so that we can cover the following:

• Request all module developers to provide DB migration support OR at the very least, flag those modules that had schema changes (include in the definition of done and ensure compliance by having POs only accept a story if there is db migration support)
• Support cross version upgrade, for example from version 8 to version 10 directly (sort all schema.json elements by modVersion first?)
• Support downgrade (or backwards compatible?) ---  could prob be deferred
• Support actual jsonb data migration (or as is by sql?)
• Potential support for other databases --- could prob be deferred
• Non-RMB DB modules

-- 

Mark Veksler

Director, FOLIO Development - EBSCO Information Services

mveksler@ebsco.com | +1-978-356-6500 x2349 (O) | +1-617-470-5453 (m)