-
-
Notifications
You must be signed in to change notification settings - Fork 489
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to validate iso19139 records which use regions keywords. #7207
Milestone
Comments
ianwallen
changed the title
Unable to properly validate records which use regions keywords.
Unable to validate iso19139 records which use regions keywords.
Jul 6, 2023
fxprunayre
added a commit
that referenced
this issue
Jul 7, 2023
Updated the date in the default thesaurus.
As we now set the dates in ISO records, maybe we should only accept valid ISO date format from thesaurus ? |
josegar74
pushed a commit
that referenced
this issue
Jul 7, 2023
ianwallen
pushed a commit
that referenced
this issue
Jul 7, 2023
fxprunayre
added a commit
to eea/geonetwork-eea
that referenced
this issue
Sep 20, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Unable to properly validate records which use regions keywords.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Expecting to be able to validate the record.
Desktop (please complete the following information):
Additional context
Issue could have also been created from the following PR
#6972
It seems like the dates in the following file are incorrect.
core-geonetwork/web/src/main/webapp/WEB-INF/data/config/codelist/external/thesauri/place/regions.rdf
Lines 14 to 15 in 9b7bd67
So we could simply update the date on that thesaurus.
Or we could enhance that PR and add better date handling
Not sure what the recommended solution would be?
The text was updated successfully, but these errors were encountered: