You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The test on keyword in metadata (md-iso.f.1: Dataset keyword) might be broken... I have made some tests with compliant metadata and all the tests fails in md-iso.f.1.
The message I get is: "The metadata record has keywords which originate from a controlled vocabulary 'GEMET - INSPIRE themes, version 1.0', but the date or date type is not correct. Date should be '2008-06-01' and date type 'publication'. The keywords are: Administrative units."
Thanks for reporting the issue. The issue has been already registered and the solution has been implemented, the pull request is pending to be accepted. Follow the discussion in the following link: inspire-eu-validation/ets-repository#180
inakidiazdecerio
added
solved
Solution developed and accepted, not yet deployed
and removed
ready for testing
Solution provided to reporter or developed & deployed in staging (or beta), waiting for testing
labels
Jul 11, 2019
The test on keyword in metadata (md-iso.f.1: Dataset keyword) might be broken... I have made some tests with compliant metadata and all the tests fails in md-iso.f.1.
The message I get is: "The metadata record has keywords which originate from a controlled vocabulary 'GEMET - INSPIRE themes, version 1.0', but the date or date type is not correct. Date should be '2008-06-01' and date type 'publication'. The keywords are: Administrative units."
The test report is available at: http://inspire-sandbox.jrc.ec.europa.eu/etf-webapp//v2/TestRuns/EID4cf6e5cb-60d0-4b02-947b-5d43cdf4af79.html?lang=en
When I look into the xml-metadata document the date and date type seems to be correct. Can you reproduce the error?
One of the tested metadata is: https://geodata-info.dk/srv/eng/csw?service=CSW&request=GetRecordById&version=2.0.2&outputSchema=http://www.isotc211.org/2005/gmd&elementSetName=full&id=50f84f74-a55a-5ca2-e36e-d9d696434322
Thanks,
Lars DK
The text was updated successfully, but these errors were encountered: