DE: Dieses Repository beinhaltet die Erweiterung von ckanext-dcat auf die Spezifikation DCAT-AP.de. EN: This is a DCAT-AP.de specific CKAN extension for providing and importing DCAT-AP.de-Profile data.
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?
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.rdf using 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?