"Release" Metadata Schema changes

[Stephen Brush]

Hi,

Just wondering what the preferred method of "releasing" metadata schema updates (e.g. new fields) along with say new versions of submission-forms.xml which may include references to those fields. Do people generally use flyway migrations, manually update the schema or is there another way?

Thanks,

Steve

[Tim Donohue]

Hi Steve,

By "Release" are you asking how we perform these updates in DSpace releases themselves?  Or are you talking about strategies for doing this in your own site (like pushing these changes from dev to production locally)?  I'm going to guess the latter.

Not sure if it helps here, but the DSpace Upgrade process somewhat helps with this.  When running "ant update" to redeploy the backend, you'd automatically update the copy of submission-forms.xml and/or any metadata schema XML files (in [dspace]/config/registries/). Part of that "ant" step is to copy over config updates.   

After that, you could run "./dspace registry-loader -metadata [full-path-to-metadata-schema.xml]" to tell DSpace to update it's database based on updates to that registry.  This command is triggered (for each metadata schema XML) automatically whenever other database updates occur (via a Flyway callback). But , it can also be run manually via the commandline.

Hopefully those give you some clues. If not, let us know if I misunderstood the question.

Tim

[Mark H. Wood]

This happens so seldom that I have to work it out every time. But I'd:

1. update the relevant document(s) in 'config/registries';
2. run the registry loader over the affected files;
3. update submission-forms.xml;
4. restart DSpace.

Since submission is affected, I'd do this first on a test instance to
make sure that everything connects up and the person requesting the
changes is satisfied.

--
Mark H. Wood
Lead Technology Analyst

University Library
Indiana University - Purdue University Indianapolis
755 W. Michigan Street
Indianapolis, IN 46202
317-274-0749
www.ulib.iupui.edu