The current version of the DataCite Metadata Schema is 4.3. The official version of the DataCite Metadata Schema, as well as the official version of the schema documentation in PDF format, can always be found at the DataCite Metadata Schema website. For convenience purposes, a copy of the schema documentation can also be found in support pages under DataCite Metadata Schema 4.3.
The most recent version of the DataCite Metadata Schema is the preferred version of the schema for DOI Fabrica and our APIs, but many of the previous versions of the DataCite Metadata Schema are still valid.
Retirement of Schema Versions 2.x
Beginning 1 January 2019, it will no longer be possible to register new DOIs using either DataCite Metadata Schema 2.1 or 2.2.
To register DOIs using a more recent version of the Schema, it is necessary to update the namespace submitted as part of the metadata, e.g.
Please review the documentation for your selected replacement Schema version to learn more about the available metadata requirements and options. In particular, please note that resourceTypeGeneral is a required field as of Schema 4.0.
- DataCite Metadata Schema 4.2 (Released Released 20 March 2019)
- DataCite Metadata Schema 4.1 (Released Released 23 Oct 2017)
- DataCite Metadata Schema 4.0 (Released 19 Sep 2016)
- DataCite Metadata Schema 3.1 (Released 16 Oct 2014)
- DataCite Metadata Schema 3.0 (Released 24 Jul 2013)
- DataCite Metadata Schema 2.2 (Released 1 Jul 2011)
- DataCite Metadata Schema 2.1 (Released 28 Mar 2011)
- DataCite Metadata Schema 2.0 (24 Jan 2011)
Starting with version 3.0 only major releases will have a new namespace, meaning that it is only necessary to specify
http://datacite.org/schema/kernel-3 rather than
http://datacite.org/schema/kernel-3.1, for example.
The version number is formatted as: Major.Minor
- Major Version — A major release is for adding features that require breaking backward compatibility with previous versions or represent fundamental changes. For a major release, the MAJOR component is incremented by one and the MINOR component is set to zero, e.g. 3.1 to 4.0.
- Minor Version — A minor release is for adding features that do not break backward compatibility with previous versions and for fixing bugs that may or may not break backwards compatibility. For a minor release, the MINOR component is incremented by one, e.g. 3.0 to 3.1.
Would you like to know more?
If you have any questions, requests or ideas please contact us!
Updated 9 months ago