We're trying to migrate to GeoNetwork 3.2.1 -we've been working with 2.6.4 untill now- but we have a problem with metadata validation.
Even If we set all schematron rules to
"Only Report errors, does not affect validity of metadata" or
"Ignore this group, the schematron will not be ran even if criteria match",
when we upload an xml file (both by using the geonetwork-manager library , and by curl invocation towards REST API) we receive an HTTP 400 error, with a response body like the following :
{"message":"SchematronValidationErrorEx","code":"runtime_exception","description":"Schematron errors detected for file - ....
This is a problem especially because -if I correctly understand the report- our metadata only fails to comply to INSPIRE rules ("schematron-rules-inspire.disabled"), and we cannot work on following this directive now.
If we cannot solve this problem we'd be stuck with version 2.6.4 for long, so I'd really appreciate any suggestion on this.
Thanks in advance,
Fabio Sinibaldi
--
--- --- --- ---
Fabio Sinibaldi
CNR Istituto di Scienza e Tecnologie dell' Informazione A. Faedo
Area della Ricerca CNR
InfraScience Group http://nemis.isti.cnr.it/groups/infrascience
Via G. Moruzzi, 1 – 56124 Pisa, Italy
In the issue there's a link to a branch solving it. I thought was already
merged this fix, but it's not. I'll check to do a PR so gets included.
Regards,
Jose García
On Fri, Oct 5, 2018 at 7:23 PM Fabio Sinibaldi <fabio.sinibaldi@anonymised.com>
wrote:
Hi all,
We're trying to migrate to GeoNetwork 3.2.1 -we've been working with
2.6.4 untill now- but we have a problem with metadata validation.
Even If we set all schematron rules to
"Only Report errors, does not affect validity of metadata" or
"Ignore this group, the schematron will not be ran even if criteria match",
when we upload an xml file (both by using the geonetwork-manager library
, and by curl invocation towards REST API) we receive an HTTP 400 error,
with a response body like the following :
This is a problem especially because -if I correctly understand the
report- our metadata only fails to comply to INSPIRE rules
("schematron-rules-inspire.disabled"), and we cannot work on following
this directive now.
If we cannot solve this problem we'd be stuck with version 2.6.4 for
long, so I'd really appreciate any suggestion on this.
Thanks in advance,
Fabio Sinibaldi
--
--- --- --- ---
Fabio Sinibaldi
CNR Istituto di Scienza e Tecnologie dell' Informazione A. Faedo
Area della Ricerca CNR
InfraScience Group http://nemis.isti.cnr.it/groups/infrascience
Via G. Moruzzi, 1 – 56124 Pisa, Italy