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 fields come from the CKAN core and have semantic relevance in CKAN, so we cannot easily change values of those fields.
The easiest way to fix these errors for GovData harvesting would be to modify the creation of the RDF file catalog.rdf
using some code like:
match ckanLanguage:
case "de":
rdfLanguage = "http://publications.europa.eu/resource/authority/language/DEU"
case "en":
rdfLanguage = "http://publications.europa.eu/resource/authority/language/ENG"
case _:
return "CKAN language not supported currently"
For a quick fix we could start with the most popular strings used in dcat_mediaType, dct_format and language_v.
Are there better fixes? Or maybe in other CKAN extensions?
The text was updated successfully, but these errors were encountered:
When checking our datasets, the EU validator using Profile
DCAT-AP.de 2.0 - Spezifikation (BETA.08-04.1)
https://offenedaten.frankfurt.de/catalog.rdf?fq=tags:GovData-Harvesting
we get these errors:
The fields come from the CKAN core and have semantic relevance in CKAN, so we cannot easily change values of those fields.
The easiest way to fix these errors for GovData harvesting would be to modify the creation of the
RDF
file catalog.rdfusing some code like:
For a quick fix we could start with the most popular strings used in
dcat_mediaType
,dct_format
andlanguage_v
.Are there better fixes? Or maybe in other CKAN extensions?
The text was updated successfully, but these errors were encountered: