DCAT-AP to CKAN
Loader, loads DCAT-AP v1.1 metadata to a CKAN catalog.
- CKAN Action API URL
- URL of the CKAN API of the target catalog, e.g.
https://linked.opendata.cz/api/3/action - CKAN API Key
- The API key allowing write access to the CKAN catalog. This can be found on the user detail page in CKAN.
- CKAN dataset ID
- The CKAN dataset ID to be used for the current dataset
- Load language RDF language tag
- Since DCAT-AP supports multilinguality and CKAN does not, this specifies the RDF language tag of the language, in which the metadata should be loaded.
- Profile
- CKAN can be extended with additional metadata fields for datasets (packages) and distributions (resources). If the target CKAN is not extended, choose
Pure CKAN. - Generate CKAN resources from VoID example resources
- If the input metadata contains
void:exampleResource, create a CKAN resource from it. - Generate CKAN resource from VoID SPARQL endpoint
- If the input metadata contains
void:sparqlEndpoint, create a CKAN resource from it.
Characteristics
- ID
- l-dcatap11tockan
- Type
- loader
- Inputs
- RDF single graph - EU MDR NALs
- RDF single graph - DCAT-AP v1.1
- Look in pipeline
- Sample pipeline
- Available
The DCAT-AP to CKAN component loads DCAT-AP v1.1 metadata to a CKAN open data catalog instance. The typical usage is for metadata created by the DCAT-AP Dataset, DCAT-AP Distribution and VoID Dataset components. The component currently uses the File type NAL codelist published by the EU Publications Office to label file types in the CKAN catalog. Therefore, this codelist needs to be provided on its EU MDR NALs input. This can be a local copy, or a fresh download. See the sample pipeline for a typical usage.
Note that when there is information about a dataset publisher in the input data, mainly its name, and there is a matching Organization in the target CKAN, the component will try to register the CKAN dataset in the CKAN organization. When there is no such organization in the target CKAN, the component will try to create one.
Currently, there is only one additional profile intended to be used with CKAN catalogs extended with the CKAN extension for Czech NKOD. This extension supports all metadata fields required by the Czech National Open Data Catalog.