Skip navigation

DataCite Metadata Schema

A practical overview of the metadata properties used to register DataCite DOIs, generate citations and connect research outputs.

The DataCite Metadata Schema provides a structured, cross-disciplinary description of datasets, software, publications, workflows, instruments and other research resources.

It supports persistent identification, citation, discovery and the creation of machine-readable relationships between research outputs, people, organisations and projects.

ChatGPT Image 27 лип. 2026 р., 22_26_38 (2)

Resource information

Resource type: Metadata schema overview

Current schema version: DataCite Metadata Schema 4.7

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

Primary uses: DOI registration, resource citation, discovery, version linking and connection of research outputs

Supported resource scope: Datasets, software, publications, workflows, instruments, projects and other research resources

Maintained by: DataCite Metadata Working Group

Last reviewed: July 2026

Purpose and scope

The DataCite Metadata Schema defines the properties and controlled values used to identify a research resource, register its DOI, generate a citation and describe its relationships with other research outputs.

The schema is intentionally cross-disciplinary. It provides a common description that can be exchanged between repositories, discovery services, citation indexes and research information systems.

DataCite metadata does not attempt to record every scientific, methodological or technical characteristic of a resource. Detailed disciplinary metadata should be maintained in the repository record, related documentation or a domain-specific metadata profile.

Important: DataCite metadata identifies, cites and connects a resource. It does not replace README files, manifests, provenance records, file-level metadata or domain-specific scientific descriptions.

What DataCite metadata supports

Persistent identification

Connects a DOI with a stable landing page and a structured description of the identified research resource.

Citation

Records creators, title, publisher, publication year and resource type needed to generate a standard citation.

Discovery

Adds descriptions, subjects, dates, locations and other information that helps users and services find and evaluate the resource.

Relationships

Links datasets, publications, software, versions, projects, people, organisations and other research entities.

DataCite Metadata Schema 4.7

Version 4.7 continues the DataCite 4.x metadata model and introduces new controlled values and additional detail for describing relationships.

New resource types: Poster and Presentation.

New related identifier types: RAiD and SWHID.

New relationship type: Other.

New relationship detail: relationTypeInformation can provide additional information where the standard relationship vocabulary is insufficient.

Levels of obligation

DataCite assigns one of three obligation levels to each major metadata property.

Mandatory — M

The property must be supplied for a complete DataCite metadata record.

Recommended — R

The property is not mandatory but is strongly recommended for interoperability, discovery and linking.

Optional — O

The property provides additional detail when relevant information is available.

Local requirement

A repository may make a DataCite-recommended or optional property mandatory within its own metadata profile.

Mandatory DataCite properties

Six major properties form the mandatory core of a DataCite metadata record.

Recommended and optional properties

Creators, contributors and affiliations

DataCite distinguishes primary creators from other contributors. This separation supports reliable attribution and machine-readable identification of different roles.

Creator

A person or organisation primarily responsible for producing the resource.

Contributor

A person or organisation that contributed through a defined role but is not a primary creator.

Name identifier

A persistent identifier for a person or organisation, such as ORCID.

Affiliation

The organisation associated with a creator or contributor, preferably identified with ROR where available.

Persistent identifiers used with DataCite metadata

DOI: identifies the registered research resource.

ORCID: identifies an individual creator or contributor.

ROR: identifies an affiliation, publisher, funder or another research organisation.

RAiD: can identify a research activity or project.

SWHID: can identify archived software source code.

Other identifiers: may identify publications, grants, samples, instruments and domain-specific research entities.

Connecting research outputs

The RelatedIdentifier property records a persistent identifier for another resource and specifies the nature of the relationship through a controlled relation type.

RelatedIdentifier and RelatedItem

RelatedIdentifier

Use when the related resource has a recognised identifier such as a DOI, URL, ISBN, ISSN, ORCID, RAiD or SWHID.

Relation type

Always specify how the described resource is related to the identified object.

RelatedItem

Use for a structured description of a related item, including cases where the related item has no persistent identifier.

Relationship detail

Use additional relationship information only when the standard controlled relation types cannot describe the relationship adequately.

Resource type

ResourceType combines a controlled general category with an optional specific description supplied by the repository or research community.

General type: a value from the DataCite resourceTypeGeneral controlled vocabulary.

Specific type: a more precise local or disciplinary description of the resource.

Example: general type Dataset with the specific type Molecular dynamics simulation dataset.

Rights and access information

The Rights property records legal rights or reuse conditions associated with the resource.

Rights name: the human-readable name of the licence or rights statement.

Rights URI: the persistent web address of the licence or rights statement.

Rights identifier: a controlled identifier, such as an SPDX licence identifier, where applicable.

Access status: should also be represented according to the requirements of the repository or interoperability profile.

Versioning and DOI assignment

Minor update

Retain the same DOI, update the metadata and increment the Version property where appropriate.

Major version

Assign a new DOI when the content changes substantially and users need to cite the versions independently.

Version sequence

Link earlier and later versions using IsPreviousVersionOf and IsNewVersionOf.

Canonical DOI

Where used, connect the DOI representing all versions with individual version DOIs using HasVersion and IsVersionOf.

From metadata to a findable DOI

1. Prepare metadata

Complete the mandatory properties and add recommended fields needed for discovery and linking.

2. Assign the DOI

Use a repository account and an authorised DOI prefix to assign or generate a DOI suffix.

3. Provide the URL

Connect the DOI to a stable landing page describing the resource and providing access information.

4. Publish or update

Create a draft record during preparation or publish it as a findable DOI when the resource is ready.

Minimum metadata for DOI registration

Creator: primary creator or creators.

Title: name of the resource.

Publisher: organisation publishing, hosting or distributing the resource.

Publication year: year in which the resource becomes available.

Resource type: controlled general resource category.

DOI and landing-page URL: persistent identifier and the current web location to which it resolves.

Minimum metadata is not sufficient metadata

A DOI can technically be registered with a small number of properties, but such a record may provide little support for discovery, evaluation and reuse.

For discovery: add Description, Subject and relevant Dates.

For attribution: add ORCID identifiers, affiliations and Contributor roles.

For reuse: add Rights, Format, Size and technical documentation.

For research connectivity: add RelatedIdentifier, FundingReference and version relationships.

For domain interpretation: retain additional metadata in the repository record and domain-specific profile.

DataCite and the Core dataset metadata profile

Example DataCite JSON metadata

The following simplified example illustrates the structure used when a repository sends metadata to the DataCite REST API.

{
  "data": {
    "type": "dois",
    "attributes": {
      "doi": "10.xxxx/example-dataset",
      "event": "publish",
      "url": "https://repository.example.org/dataset/123",
      "creators": [
        {
          "name": "Researcher, Example",
          "nameType": "Personal",
          "givenName": "Example",
          "familyName": "Researcher",
          "nameIdentifiers": [
            {
              "nameIdentifier": "https://orcid.org/0000-0000-0000-0000",
              "nameIdentifierScheme": "ORCID",
              "schemeUri": "https://orcid.org"
            }
          ],
          "affiliation": [
            {
              "name": "Example Research Institution",
              "affiliationIdentifier": "https://ror.org/example",
              "affiliationIdentifierScheme": "ROR",
              "schemeUri": "https://ror.org"
            }
          ]
        }
      ],
      "titles": [
        {
          "title": "Example research dataset"
        }
      ],
      "publisher": {
        "name": "Example Data Repository"
      },
      "publicationYear": 2026,
      "types": {
        "resourceTypeGeneral": "Dataset"
      },
      "subjects": [
        {
          "subject": "research data"
        }
      ],
      "descriptions": [
        {
          "description": "Dataset produced during the example study.",
          "descriptionType": "Abstract"
        }
      ],
      "rightsList": [
        {
          "rights": "Creative Commons Attribution 4.0 International",
          "rightsUri": "https://creativecommons.org/licenses/by/4.0/",
          "rightsIdentifier": "CC-BY-4.0",
          "rightsIdentifierScheme": "SPDX",
          "schemeUri": "https://spdx.org/licenses/"
        }
      ],
      "relatedIdentifiers": [
        {
          "relatedIdentifier":
            "10.xxxx/example-publication",
          "relatedIdentifierType": "DOI",
          "relationType": "IsSupplementTo",
          "resourceTypeGeneral": "JournalArticle"
        }
      ],
      "version": "1.0",
      "language": "en"
    }
  }
}

Metadata quality recommendations

Use structured names

Separate personal and organisational names and include persistent identifiers where available.

Provide an abstract

Add a Description with descriptionType Abstract so users can evaluate the resource before accessing it.

Use typed relationships

Every related identifier should include the identifier type and the relationship type.

Update the record

Keep the DOI URL, creators, version, rights and relationships current after registration.

Common implementation errors

Using only mandatory properties: the DOI exists, but the record is difficult to discover and evaluate.

Recording all participants as creators: contributor roles and primary authorship become unclear.

Providing an identifier without a relation type: the connection between resources cannot be interpreted automatically.

Confusing Publisher with Creator: the repository or distributing organisation is usually the Publisher, not the research team.

Using a licence as an access status: legal permission for reuse and technical availability should be represented separately.

Assigning one DOI to substantially different versions: independently citable major versions may require separate DOIs.

Treating DataCite as complete domain metadata: scientific parameters and provenance remain insufficiently documented.

How to use this resource

1. Identify the resource

Determine the resource type, creators, title, publisher and publication year.

2. Enrich the record

Add an abstract, subjects, contributors, dates, rights, funding and relevant technical information.

3. Connect outputs

Add persistent identifiers for publications, datasets, software, projects and related versions.

4. Validate and register

Validate required properties and controlled values before registering or updating the DOI.

Explanatory status

This page provides an explanatory overview of the DataCite Metadata Schema for research data preparation, training and repository support.

It does not replace the official DataCite schema, controlled vocabularies, XML Schema Definition, REST API documentation or requirements established by the repository registering the DOI.

Repository-specific application profiles may require additional properties or impose stricter validation rules than the general DataCite specification.

The official DataCite documentation should be consulted before implementing, validating or updating a production metadata workflow.