Closed chiarachiarelli closed 3 years ago
I'm investigating this and I found that the reason why it happens is that in the schematron rules file, the variable where the associated resource name is stored is empty.
I'm referring to the variable $nameTitle here: https://github.com/metadata101/iso19115-3.2018/blob/24ae19dddd0cd791d3978f8e99e080798eef001e/src/main/plugin/iso19115-3.2018/schematron/schematron-rules-iso.sch#L1536
I also checked with a online XPath tester that the context xpath of the rule is correct.
Hope these findings can be helpful.
Maybe it is related to #4805, geonetwork expects a uuid, not a hyperink?
The problem is that the metadata validated is enhanced with the geonet
namespace, to link the UI elements with the validation rules. The rule matches any element in //mri:MD_DataIdentification/mri:associatedResource/*
, checking also these elements and causing the validation error.
Going to update it to discard elements in the geonet
namespace
Trying to add one or more "Associated resource" with "Association Type" and "Initiative Type" the ISO validator for ISO19115-3 gives 10 times the same error "When a resource is associated, a name or a metadata reference MUST be specified" which though doesn't seem resolvable.
Here follows an exampe of xml that gives 10 times the same error: "When a resource is associated, a name or a metadata reference MUST be specified."
Screenshots
GeoNetwork Version 3.10.*