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 On Tuesday, November 29, 2022 at 3:48:19 PM UTC-6 [email protected] wrote: > 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 > -- 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 Developers" 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-devel/01341247-5d61-4eef-afea-d43be51061d0n%40googlegroups.com.
