-
Notifications
You must be signed in to change notification settings - Fork 0
DataCite mapping
Metadata conforming to the DataCite metadata definition can be dealt with much in the same way as Dublin Core metadata. The main difference is that the DataCite definition comprises less elements, and is more targeted towards data sets, while
| facet | DataCite metadata property (and Id) |
|---|---|
| creator | Creator (2) |
| contributor | Contributor (7) |
| language | Language (9) |
| CreationDate | Date (8), but only if the type (8.1) is 'Created' or 'Collected' |
| PublicationDate | Date (8), but only if the type (8.1) is 'Issued' |
| format | Format (14) |
| discipline | |
| collection | ResourceType (10), but only if resourceTypeGeneral (10.1) equals 'collection' |
| country | |
| title | |
| notes | |
| subject | Subject (6) |
| URL | Identifier (1), only if the type (1.1) is 'DOI' |
| rights | Rights (16) |
| ResourceType | ResourceType (10) |
| SpacialCoverage | GeoLocation (18), but only in the form of geoLocationPlace (18.3) |
| TemporalCoverage | |
| DataProvider |
In case of the CreationDate facet, the DataCite 'date' property is used, but only then if the property is of type 'Created' or 'Collected'. The 'Collected' type was added since most of the data harvested included this property.
The discipline and country facets have no equivalent in the DataCite definition. A similar remark can be made about the 'collection' facet: currently the data does not provide a value for the facet, a mapping has been put in effect however.
For the title facet, DataCite title elements without a type specification are preferred.
Finally, the 'SpacialCoverage' facet shows the value of the 'GeoLocation' property, only in case the property is of type 'geoLocationPlace'. In that case the DataCite definition allows a description of the geographic location. Because this does not match the semantic metadata definition, the latter one needs to be adapted.
References: DataCite metadata definition, Metadata semantics