Improve validation report layout and schematron rules compilation

Date	2009/11/13
Contact(s)	Francois
Last edited	Timestamp
Status	Proposed for vote
Assigned to release	2.5
Resources	GéoSource, geocat.ch projects
Ticket	#172

Overview

Main goal of this proposal is to improve validation report layout and schematron compilation rules. It allows to define different validation levels, grouping rules by level. For an ISO 19139 records, editor could clearly identify XSD errors, ISO rules or any other validation level defined for the schema (eg. Profil specific rules, INSPIRE rules).

Proposal Type

• Type: Core Change & Editor
• App: GeoNetwork
• Module: Validation

Links

• Email discussions:
• IRC discussions:

Voting History

• Vote proposed November 13th 2009
• Votes:
  • +1 Jeroen
  • +1 Simon
  • +1 Patrizia
  • +1 Francois

---

Motivations

The motivations for these changes are :

• A better layout,
• Allow to define multiple validation levels (XSD, ISO rules, Profil specific rules, INSPIRE rules, ...)
• Schematron compilation made by ant script : clean temporary generated XSL files

Proposal

Main changes:

• display validation report on a popup on the editor
• allows to filter errors only or all (errors and rules),
• define different levels of validation. Instead of having 2 levels (XSD and Schematron), catalogue administrator could define XSD and N Schematron levels (eg. ISO rules and Profil specific rules).
• MetadataSchema registers schematron rules on startup.
• do not stop on XSD errors, continue and generate full report.
• ant script to compile schematron rules and deploy to schema directories (remove temporary files and make easier to update schematrons).
• improve some schematron rules to take into account @gco:nilReason.
• add INSPIRE schematron rules (not available by default)
• add German translation for schematron rules (Thanks Annina)
• improve validation process (store validation report in session like the current metadata in edit mode)

Feature removed :

• XML view of schematron rule errors report

Backwards Compatibility Issues

none

Risks

Participants

• As above