search

metadata101 / iso19139.gemini23

Gemini 2.3 schema plugin for Geonetwork 3.4.3+
0 stars 3 forks source link

Record that was APISO valid when imported becomes invalid in GeoNetwork #4

Closed nmtoken closed 4 years ago

nmtoken commented 4 years ago

Looking at my record with file identifier <gco:CharacterString>ea819b92-d389-193a-e044-002128a47908</gco:CharacterString> which is BGSsv-examplea1.xml at https://github.com/AGIGemini/Schematron/tree/master/samples

If I validate this file using the APISO schema in oXygen I'm told it's valid.

If I look at the same file that has been imported into the geonet38 server (and then harvested by me) and validate that file using the APISO schema in oXygen I'm told it's not-valid.

In the original file I have:

<gmd:verticalElement gco:nilReason="inapplicable"/>

In the geonet38 version of the file this has been changed to:

<gmd:verticalElement gco:nilReason="missing">
    <gco:CharacterString/>
</gmd:verticalElement>`

Causing the validation fail:

Invalid content was found starting with element '{"http://www.isotc211.org/2005/gco":CharacterString}'. One of '{"http://www.isotc211.org/2005/gmd":EX_VerticalExtent}' is expected.

archaeogeek commented 4 years ago

Closing as discussion is in https://github.com/metadata101/iso19139.gemini23/issues/5