Versions Compared

Old Version 34

changes.mady.by.user Tim Donohue

Saved on

compared with

New Version 35

changes.mady.by.user Terrence W Brady

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Note
titleUpgrading database structure/data is now automated!

As of DSpace 5.0, the underlying DSpace database structure changes are now AUTOMATED (using FlywayDB). This means that you no longer need to manually run SQL scripts. Instead, the first time you run DSpace, it will auto-update your database structure (as needed) and migrate all your data to be compatible with the installed version of DSpace. This allows you to concentrate your upgrade efforts on customizing your site without having to worry about migrating your data!

For example, if you were running DSpace 1.4, and you wish to upgrade to DSpace 5, you can follow the simplified instructions below. As soon as you point your DSpace 5 installation against the older DSpace 1.4-compatible database, your database tables (and data) will automatically be migrated to be compatible with DSpace 5.

Note
titleDiscovery re-index

Note: the upgrade to DSpace 5.6 from a prior minor version (5.0-5.5) will also trigger an update to your database schema.

The FlywayDB migration will trigger a re-index of your Discovery search index after deployment. Some repository content will be not be discover-able until this process is complete. For large repository instances, this process could take some time to complete.

Note
titlePlease refrain for customizing the DSpace database tables. It will complicate your next upgrade!

With the addition of our automated database upgrades, we highly recommend AGAINST customizing the DSpace database tables/structure or backporting any features that change the DSpace tables/structure. Doing so will often cause the automated database upgrade process to fail (and therefore will complicate your next upgrade).

If you must add features requiring new database tables/structure, we recommend creating new tables (instead of modifying existing ones), as that is usually much less disruptive to our automated database upgrade.

...