ABCDEF
1
Dublin CoreDC DefinitionDCATCKANProposalNotes
2
contributorAn entity responsible for making contributions to the resource.dct:contributorextra:contributorAdd support for contributor to the CKAN DCAT pluginNot part of standard CKAN DCAT plugin
3
coverageThe spatial or temporal topic of the resource, spatial applicability of the resource, or jurisdiction under which the resource is relevant.dct:coverage; dcat:spatial; dcat:temporalextra:spatial_uri + extra:spatial + extra:spatial_text; extra:temporal_start + extra:temporal_end; extra:coverageFor CKAN/DCAT to coverage, use a text description of the spatial and temporal characteristics e.g. "Bounding lat-lon [53, -4.5],[50, 1.7]. 2022-01-01 - 2022-12-31"

For DC->DCAT/CKAN, store coverage as dct:coverage/extra:coverage without attempting to generate dcat:spatial and dcat:temporal. Note that extra:coverage is not part of the standard CKAN DCAT plugin
Lack of definition for coverage makes mapping DC->DCAT or CKAN problematic.
4
creatorAn entity primarily responsible for making the resource.dct:creatorextra:creatorAdd support for contributor to the CKAN DCAT pluginNot part of standard CKAN DCAT plugin
5
dateA point or period of time associated with an event in the lifecycle of the resource.dct:date or dct:issuedextra:issuedMap date to the issed date of the dataset dct:issuedThe DC "date" field definition makes it impossible to infer how it is being used.
6
descriptionAn account of the resource.dct:descriptionnotes
7
formatThe file format, physical medium, or dimensions of the resource.dct:formatresource:format
8
identifierAn unambiguous reference to the resource within a given context.dct:identifierextra:identifier (synonyms - extra:guid, extra:id)
9
languageA language of the resource.dct:languageextra:language
10
publisherAn entity responsible for making the resource available.dct:publisherextra:publisher_uri
11
relationA related resource.dct:relationextra:relationStore in the CKAN extra:relation field unmodifiedNot part of standard CKAN DCAT plugin. CKAN has its own "relations" structure that is complex to map to this one
12
rightsInformation about rights held in and over the resource.dct:rights or dct:licenseresource:rights or resource:licenseFor CKAN/DCAT to DC use dct:rights if available, otherwise dct:licenseThe rights may include license and copyright elements. They are combined in DC but separate in DCAT and CKAN. For DC->CKAN/DCAT use rights.
13
sourceA related resource from which the described resource is derived.dct:sourceextra:source
14
subjectThe topic of the resource.dct:keywordstagsFor DC->DCAT/CKAN store in dct:keywords/tags

For DCAT/CKAN->DC concatenate dcat:keywords/tags and dcat:theme e.g.

dcat:theme: "assets"
dcat:keywords: "132kV, tranformer"
-> dc:subject: "assets, 132kV, transformer"
15
titleA name given to the resource.dct:titletitle
16
typeThe nature or genre of the resource.dct:typeextra:dcat_type
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100