-
Notifications
You must be signed in to change notification settings - Fork 0
Domain comparison
We currently harvest metadata records in three forms: CMDI, DataCite and Dublin Core. These records are mapped to the records that you can see in the metadata catalogue. The following table lists the properties in the range of the mapping from DataCite, CMDI and Dublin Core, next to properties available in our catalogue.
Catalogue | DataCite | CMDI | DC |
---|---|---|---|
Creator | + | m | + |
Contributor | + | m | + |
Language | + | + | + |
CreationDate | + | m | |
Format | + | + | m |
Discipline | m | ||
Collection | + | ||
Country | + | ||
title | + | + | + |
notes | m | m | m |
Subject | + | + | |
url | m | m | m |
MetadataSource | m | m | m |
fulltext | m | m | m |
Rights | n | n | n |
ResourceType | n | n | n |
SpacialCoverage | n | n | n |
TemporialCoverage | n | n | n |
MetadataSchema | n | n | n |
In the table 'm' means that the property listed is not part of the format literally. 'Notes', for example, it not a property DataCite records. It is a property of the catalogue's metadata records that, by mapping, will be associated with some property or properties in Dublin Core records. Only a '+' means that the property is actually available in the domain.
As it turns out, apart from the new properties (marked n) still to be added, the mapping from CMDI to catalogue records is the most complete. Only the Subject property is missing from the range of the mapping. Both the mapping from DataCite and Dublin Core lack a couple of properties: Discipline, Collection, Country. On top of these, the mapping from DataCite lacks the CreationDate property.
For DDI, mappings are under development. As a guideline for a definition, the set of properties currently shown in the catalogue should be considered.