<https://lh3.googleusercontent.com/-0A8hT-AF-6I/V3_NEAjXqRI/AAAAAAAAAUQ/oJzxN1DXLH8KW5XDEF-rAjeQe7d9I1jJgCLcB/s1600/newfield.jpg> Ηi Claudia,
so, if I undestand correctly, adding a new metadata field to an existing schema (say dc for example) is a 3 step process? 1. Addition of the field in the following admin form <https://lh3.googleusercontent.com/-0A8hT-AF-6I/V3_NEAjXqRI/AAAAAAAAAUQ/oJzxN1DXLH8KW5XDEF-rAjeQe7d9I1jJgCLcB/s1600/newfield.jpg> 2. Addition in the input-forms.xml 3. Addition in the registries, i.e. in our case dublin-core-types.xml? Is that correct? (In my case I carried out the first 2 steps, and the field was indeed added...I just wanted to know how the db migration will take place so someone who checks out my code has the new field in his db instance) Thanks, P.K. On Friday, July 8, 2016 at 5:07:17 PM UTC+3, Pantelis Karamolegkos wrote: > > When adding a new metadata field through the respective admin form (in an > existing schema. e.g. dc), do we also have to manually add the respective > flyway migration script under org.dspace.storage.sqlmigration.<dbtype> ? > Otherwise how will the new field be added to the database of someone who > checks out our code from the branch we are working on? > -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
