| 67 | | This proposal is to run validation (XSD+Schematron) every time a metadata is inserted or changed. The result of validation is persisted in the DB. |
| 68 | | Validation status is either "valid", "not valid", or "not determined". This last status is the initial validation status when validation has not yet run. |
| 69 | | A validation report is also stored in the DB. It contains any XSD or schematron validation messages, a reference to the schematron file that was used, a timestamp, and if applicable a message saying that the metadata profile could not be determined. |
| | 67 | This proposal is to run validation (XSD+Schematron) every time a metadata is inserted or changed. The result of validation is persisted in the DB. Persistence is required to show the validation status directly (or maybe query on it later, but this is not implemented at this time). This way we can always show the current "validation status" of metadata, e.g. in the search results page.[[BR]][[BR]] |
| | 68 | Validation status is either "valid", "not valid", or "not determined". This last status is the initial validation status when validation has not yet run. Currently the statuses "valid" and "not valid" are shown in the search results. Showing "not determined" as well is a minor change.[[BR]][[BR]] |
| | 69 | A validation report is also stored in the DB. It contains any XSD or schematron validation messages, a reference to the schematron file that was used, a timestamp, and if applicable a message saying that the metadata profile could not be determined. There is basic support for multiple metadata profiles, using different Schematron rules for different profiles.[[BR]][[BR]] |
