-
Notifications
You must be signed in to change notification settings - Fork 0
Metadata semantics
A name given to the resource. One line heading that names a resource, gives a description of it. A title could for example be the name of (a section of) a written resource.
As ckan primarily deals with data sets, the title refers to a data set. Please note that for ckan itself, the 'title' field is optional, and by default the same as 'name'.
A description of the data set. Again, for ckan itself, the field is optional.
A URL for the source of a data set. Optional for ckan. The field should contain only one value.
Writer, generator or producer of the resource described by the metadata. This field can be identified with the 'creator' field in the Dublin Core standard. Since multiple authors can be associated with a resource, the field can have multiple values. In creating a list of authors, the policy is to avoid duplicates.
An entity, that is: a person, an organisation, or a service, participating in the creation of a resource. Here also, like in the case of the 'creator' field, the policy is to avoid duplicates.
Specification of the language used in the resource. For example, an English book about Japanese language, will have 'English' as the value of the language field.
The date at which the resource was created.
The date at which the resource was made known to the public.
The organisation of information according to preset specifications (computer processing) or tradition (books, physical representation of content). For example: file format, physical medium, or dimensions. Multiple field values are allowed, since sometimes a metadata description applies to more than one resource.
Audience for the resource described by the metadata, a specific branch of knowledge.
An aggregation of resources. A body which the resource is part of.
Organised body of people, territory or area indefinitely bounded like for example 'mountainous area'. Currently, the field is only part of CMDI metadata mapping, see questions. In principle, multiple field values are allowed.
A representation of the resource in term of keywords, key phrases, or classification codes. Preferably these should be part of a closed vocabulary.
A reference to the metadata as stored, the metadata the presentation in CKAN is based on.
The metadata ifself. The field is internal to ckan, that is: it is not visible as a field to the user.
Description of the authority that has been granted to access the resource described by the metadata.
Categorisation of the subject of description into for example: text image, audio, video, object, collection, event, interaction, and or data set.
Denotation of an area the resource described by the metadata is associated with. The denotation can take the form of a list of coordinates. It can also take the form of a description like for example: South-Asia. Multiple field values could be mapped.
Different from denotations in terms of borders there are more qualitative descriptions. Think for example of a country as an organised body of people, or a territory or area indefinitely bounded like for example 'mountainous area' or 'savanna'. These kind of properties cannot be termed as a location, and are therefore called 'geographic descriptions'.
Denotation of a period in time the resource described by the metadata is associated with. The coverage is expressed by two dates: the begindate and the enddate. The dates need to be specified in UTC format. Only a single value can be associated with each of these fields.
Different from other fields since a metadata schema only indirectly describes the metadata's subject. A URI to an elaborate description of the form the metadata can take. This can be a website, a document, or a more formal normative schema backing up description.
The organisation that makes the resource (not the data about the resource, not the metadata) available to the public by any type of electronic means. If not the publisher of the resource, a DataProvider will typically be a data center.
The DataProvider definition, based on the DataCite definition, is not compatible with the definition listed in the deliverable. At least if you interpret HostingInstitution in DataCite as provider.