Hello, while preparing to upgrade to 4.2 I thought about the upgrade process and registries. There have been a couple of new registries since 1.4.2: * worklfow-types.xml * sword-metadata.xml * dcterms-types.xml
Registries [dspace-src]/dspace/config/registries/* are only loaded during ant fresh_install. Sometimes the upgrade installation included an extra step to load the registry (for sword-metadata.xml not for the others). So the new registries are usually not taken into account while doing an upgrade of an existing instance, unless they are loaded via the registry loader. So how can we avoid a discrepancy here, either bei adding an import descripion to the upgrade documentation or adding the new metadata values to the database upgrade scripts? Furthermore I think it would be best to have only one registry for metadata fields in order to avoid double declarations of fields like in dc-types.xml and sword-metadata.xml. Have a sunny day Claudia -- Claudia Juergen Eldorado Technische Universität Dortmund Universitätsbibliothek Vogelpothsweg 76 44227 Dortmund Tel.: +49 231-755 40 43 Fax: +49 231-755 40 32 claudia.juer...@ub.tu-dortmund.de www.ub.tu-dortmund.de ------------------------------------------------------------------------------ _______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
