Skip navigation

General metadata vocabularies

Cross-disciplinary controlled values used to describe research resources, contributors, dates, identifiers, languages and technical formats consistently.

This resource provides practical guidance on selecting and recording standardised values for metadata fields shared across research domains, repositories and catalogue systems.

Using established vocabularies reduces ambiguity, supports automated validation and improves the exchange of metadata between repositories, DOI services, catalogues and research infrastructures.

ChatGPT Image 29 лип. 2026 р., 21_12_47 (1)

Resource information

Resource type: Controlled vocabulary reference

Vocabulary level: General and cross-disciplinary metadata

Primary audience: Researchers, data stewards, repository managers, metadata specialists and software developers

Primary uses: Dataset description, repository deposit, DOI registration, metadata validation and catalogue exchange

Main sources: DataCite, COAR, DCMI, CRediT, ORCID, ROR, IETF, ISO and IANA

Last reviewed: July 2026

Purpose and scope

General metadata vocabularies define standard values for properties that occur across disciplines and types of research output.

They help repositories and researchers use the same meaning for concepts such as dataset, software, data curator, collection date, translated title, personal name, organisation and file format.

These vocabularies provide the cross-disciplinary layer of a metadata record. More detailed scientific concepts should be supplied through domain-specific vocabularies and ontologies.

Important: always use the vocabulary required by the destination metadata profile. A repository may use one vocabulary internally and map its values to another vocabulary during export.

General vocabulary families

Resource description

Resource types, title types, description types and other values describing the nature and content of a research output.

People and organisations

Name types, contributor roles and identifier schemes for researchers, organisations and research contributors.

Dates and locations

Typed dates, language tags, country codes and other standardised geographic or temporal values.

Technical description

File formats, media types, identifier types and values used to describe technical representations.

Main vocabulary sources

Resource types

DataCite uses a broad controlled value in resourceTypeGeneral and permits a more specific free-text value in resourceType.

General type: identifies the broad category required for DataCite metadata.

Specific type: provides a narrower repository or domain description.

Example: general type Dataset and specific type Molecular dynamics simulation dataset.

COAR Resource Types

COAR Resource Types should be used when a repository or aggregator needs a more detailed and hierarchically organised description than the broad DataCite categories provide.

Example general type: dataset

Example publication type: journal article

Example report subtype: data management plan

Example computational type: workflow

Representation: persistent concept URI plus a multilingual label

Title types

The main title is recorded without a title type. Additional titles should use a controlled value explaining their function.

{
  "titles": [
    {
      "title": "Metadata profile for research datasets",
      "lang": "en"
    },
    {
      "title": "Профіль метаданих дослідницьких датасетів",
      "titleType": "TranslatedTitle",
      "lang": "uk"
    }
  ]
}

Description types

Contributor roles

DataCite contributor types identify how a person or organisation is associated with the described resource.

CRediT contributor roles

CRediT describes the specific activities through which an individual contributed to producing a research output.

Conceptualization · Data curation · Formal analysis · Funding acquisition · Investigation · Methodology · Project administration · Resources · Software · Supervision · Validation · Visualization · Writing – original draft · Writing – review and editing

Names and identifier schemes

Date types

Language tags

Use a standard language tag instead of entering the language name as unrestricted text.

Ukrainian: uk

English: en

British English: en-GB

German: de

Traditional Chinese: zh-Hant

Use the shortest adequate tag: use en unless a regional or script distinction is important.

Do not translate the code: use uk, not ua, for the Ukrainian language.

Separate language from country: language uk and country UA represent different concepts.

Country codes

Use ISO 3166 codes for countries and territories when the metadata profile requires a controlled geographic value.

File formats and media types

Record the machine-readable media type separately from a filename extension and, where useful, from the human-readable format name.

Format name: useful for human-readable documentation.

Extension: identifies the conventional filename suffix but is not a complete format identifier.

Media type: supports machine processing and content negotiation.

Format version: should be recorded separately when compatibility depends on a specific release.

How to record a controlled value

Where the metadata system supports structured values, record more than the displayed label.

{
  "value": "dataset",
  "conceptUri": "http://purl.org/coar/resource_type/c_ddb1",
  "vocabulary": "COAR Resource Types",
  "vocabularyVersion": "3.2",
  "language": "en"
}

Value: preferred human-readable label.

Concept URI: stable identifier of the concept.

Vocabulary: name of the source vocabulary.

Vocabulary version: release used by the record.

Language: language of the displayed label.

Example of controlled values in a metadata record

{
  "resourceType": {
    "resourceTypeGeneral": "Dataset",
    "resourceType": "Computational materials dataset",
    "coarType": {
      "label": "dataset",
      "uri": "http://purl.org/coar/resource_type/c_ddb1"
    }
  },
  "titles": [
    {
      "title": "Example computational dataset",
      "lang": "en"
    },
    {
      "title": "Приклад обчислювального датасета",
      "titleType": "TranslatedTitle",
      "lang": "uk"
    }
  ],
  "contributors": [
    {
      "name": "Example Researcher",
      "nameType": "Personal",
      "contributorType": "DataCurator",
      "nameIdentifier": {
        "scheme": "ORCID",
        "uri": "https://orcid.org/0000-0002-1825-0097"
      },
      "creditRoles": [
        "Data curation",
        "Validation"
      ]
    }
  ],
  "affiliation": {
    "name": "Example Research Institution",
    "identifierScheme": "ROR",
    "identifier": "https://ror.org/example"
  },
  "dates": [
    {
      "date": "2026-07-01",
      "dateType": "Created"
    },
    {
      "date": "2026-07-20",
      "dateType": "Issued"
    }
  ],
  "language": "en",
  "country": "UA",
  "formats": [
    {
      "formatName": "Comma-separated values",
      "fileExtension": ".csv",
      "mediaType": "text/csv"
    },
    {
      "formatName": "JSON",
      "fileExtension": ".json",
      "mediaType": "application/json"
    }
  ]
}

How to select a general metadata vocabulary

1. Identify the field

Determine whether the value describes a resource, contributor, date, identifier, language, country or technical format.

2. Check requirements

Review the metadata profile and destination repository for a required vocabulary or code list.

3. Select the concept

Choose the most precise valid value without using a narrower term than the available evidence supports.

4. Preserve provenance

Store the vocabulary name, concept identifier and version where the system permits.

Mapping between general vocabularies

A local repository may need to translate the same value into several external representations.

Validation rules

Value validation

Check that the supplied code or term belongs to the required controlled list.

Identifier validation

Check identifier syntax, scheme name and resolvability where appropriate.

Context validation

Confirm that the value is valid for the metadata property in which it is used.

Mapping validation

Verify that exported values preserve the intended meaning in the destination profile.

Common implementation errors

Using a filename extension as the complete format description: the technical representation remains ambiguous.

Using a country code as a language code: UA represents Ukraine, while uk represents Ukrainian.

Using only a displayed organisation name: changes, translations and similarly named organisations cannot be disambiguated.

Using CRediT as a replacement for DataCite contributorType: contribution activities and metadata relationships are different concepts.

Choosing Other too early: a suitable controlled value may already exist.

Combining several values in one string: individual terms cannot be validated or indexed.

Recording a label without its vocabulary: the source and meaning of the value become unclear.

Ignoring vocabulary versions: later changes cannot be traced reliably.

How to use this resource

1. Find the property

Identify the metadata field for which a standard value is required.

2. Select the source

Use the vocabulary prescribed by DataCite, the repository or the destination catalogue.

3. Record structured values

Preserve codes, identifiers, labels and vocabulary information in separate fields.

4. Validate the export

Check how the value appears in DataCite, OAI-PMH, catalogue and machine-readable web metadata.