201311analytics

Due to a multitude of reasons metadata can get invalid over time or links in the metadata can get lost (404). Last summer it was suggested to implement a background process that constantly checks metadata records. Tasks performed on a record are based on plug-ins. So an administrator should be able to select which plug-ins he would like to activate and how he wants to be notified of a potential error along with links that will assist in fixing the issue.

Following plug-ins/tasks are suggested:

• Validation of the record against xsd and schematron
• Check metadata links (service operateson dataset, parent-child, feature catalog)
• Check link to WMS/WFS server. Check if server is available. Check if layer mentioned is available in capabilities. Or even check if other layers are available in capabilities that are not described in the catalog.
• If metadata is marked as Inspire, an attached WMS/WFS capabilities document could be checked on certain Inspire extensions (required keywords, service metadata link)

Much of the serverside code is already written (Bolsena) but testing needs to be completed and a UI is required. A couple of example plugins are also need to be developed in order to validate the API.