Conformance to Dublin Core

At the moment, the data in the catalogue is exclusively provided through ckan. If we want to be able to provide the data using the OAI protocol, we need to keep an eye on the conformance of the data in the catalogue with Dublin Core, since OAI requires this. The following table lists issues in the relation between the catalogue properties and Dublin Core.

catalogue	DC
Creator	1.1
Contributor	terms
Language	1.1
CreationDate	not included, use date
Format	terms
Discipline	not included, could be audience
Collection	not included
Country	not included, could be coverage
title	1.1
notes
Subject	1.1
URL
MetadataSource
fulltext

The CreationDate field might be in the DC mapping, but it is not part of the standard. The 'date' field is however; it is part of 1.1. More data related properties are including in the terms definition.

At first sight, it might look like isPartOf in terms could be used as the domain of the mapping to Collection. However, in case of isPartOf another comparable or related resource is targeted.

In DC 'collection' is not a property, but a collection. It could be wise to replace collection with 'isPartOf'.

It might be possible to replace country can be replaced by coverage. If coverage cannot be used in case country refers to the origin of the resource, publisher or created could be used instead. This would need to be reviewed.

References

Dublin Core metadata element set