Check the configuration files for errors #260
Labels
Milestone
Comments
DenysShvorack
pushed a commit
to scopesolutions-ch/roda-in
that referenced
this issue
Mar 21, 2018
…h of metadata form fields; 3)Updated configuration loading logic; 4)Small update to metadata.xml. ------------------------------------------------------------ 1) Submission number is not mandatory anymore, Submission office and Records creator are. Made an appropriate update fo the ARELDA template. 2) Mainly mandatory status and length of fields are validated. 3) For the templates and schemas added logic which overrides older files in the configuration folder. Checking only if file exsist caused that some old templates stayed and there was old UI representation for metadata form, similar with schemas, old schemas caused metadata.xml validation errors. For other configuration files I'm not sure if they can be replaced in such way. There is an open issue in GitHub to validate configuration files, this approach could be better, but not sure about performance: keeps#260 keeps#314 4) Empty <schutzfrist> caused xsd validation erro for metadata.xml, now it is added only when there is a value from user. There could be similar places in metadata.xml generation, not sure if they need an update, at least no more errors.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Configuration files with missing or invalid configuration rules may cause unstable and unforeseen behaviour. To avoid this, the configuration files should be validated and appropriate error messages should be displayed to assist in fixing the config file.
The text was updated successfully, but these errors were encountered: