DataCite Support

DataCite Support

Welcome to DataCite's support site. Here you will find helpful information about our services. We have included comprehensive technical guides, training materials, and tips to help you successfully use DataCite services.

Get Started    API Reference

Metadata Quality

Best Practices

Metadata Properties

The DataCite Metadata Schema is a list of core metadata properties chosen for an accurate and consistent identification of a resource for citation and retrieval purposes, along with recommended use instructions.The Metadata Schema has three different levels of obligation for its metadata properties:

  • Mandatory: these properties must be provided, otherwise the DataCite DOI will not be minted or updated
  • Recommended: these properties are optional, but strongly recommended for interoperability
  • Optional: these properties are optional but provide a richer description of the object

To enhance the prospects of an object with a DataCite DOI to be found, cited and linked to original research, DataCite strongly encourages to submit as much metadata as the service is aware of and has permission to share.

Mandatory Properties

Mandatory and Recommended properties and sub‐properties are especially valuable to information seekers and added‐service providers, such as indexers. The DataCite Metadata Working Group members strongly urge the inclusion of metadata identified as Recommended for the purpose of achieving greater exposure for the resource’s metadata record, and therefore, the underlying research itself. 

Mandatory Properties
Identifier
Creator
Title
Publisher
PublicationYear
ResourceType

Recommended Properties

Recommended Properties
Subject
Contributor
Date
RelatedIdentifier
Description
GeoLocation

Optional Properties

Optional Properties
Language
AlternateIdentifier
Size
Format
Version
Rights
FundingReference

Updated about a year ago


Metadata Quality


Best Practices

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.