Use of DataCite¶

What’s different¶

In this document you will find the needed properties to make your data archive compatible with the OpenAIRE infrastructure. OpenAIRE has adopted the DataCite Metadata Schema v3.1 with some minor adjustments.

• OpenAIRE accepts other persistent identifier schemes and not only a DOI in 1.1 identifierType (M).
• OpenAIRE recommends exporting links to related publications and datasets (i.e. 12. RelatedIdentifier (MA) property and attributes are mandatory when applicable).
• OpenAIRE recommends using the 7. Contributor (MA/O) property to relate a dataset to funding information.
• DataCite optional properties 8. Date (M) and 17. Description (MA) are mandatory in OpenAIRE.
• OpenAIRE enforces an encoding scheme on DataCite property 16. Rights (MA).

Access rights and license information¶

OpenAIRE uses the access rights to enable a better user experience by declaring the access rights clear and explicit in the portal. Access rights are specified using the 16. Rights (MA) property. Please see example of encoding scheme in the section above.

An example:

1
2
3

<rightsList>
  <rights rightsURI=”info:eu-repo/semantics/openAccess” />
</rightsList>

OpenAIRE further recommends including license information if available:

1
2
3
4
5
6

<rightsList>
  <rights rightsURI=”info:eu-repo/semantics/openAccess” />
  <rights rightsURI=”http://creativecommons.org/licenses/by/4.0/”>
    Creative Commons Attribution 4.0 International
  </rights>
</rightsList>

Funding information¶

OpenAIRE have a specific use of the 7. Contributor (MA/O) property to identify links to funding steams.

One of OpenAIRE’s main goals is to link research output to (EC) research funding. The following application of the contributor property allows unique and persistent identification of the funder who has funded wholly or partly the dataset described.

The following properties are mandatory when applicable to provide funding information: 7. Contributor (MA/O), 7.1 contributorType (MA/O), 7.2 contributorName (MA/O), 7.3 nameIdentifier (MA/O) and 7.3.1 nameIdentifierScheme (MA/O).

An example for linking a research output to the OpenAIREplus FP7 project:

1
2
3
4
5
6

 <contributor contributorType="Funder">
   <contributorName>European Commission</contributorName>
     <nameIdentifier nameIdentifierScheme="info">
       info:eu-repo/grantAgreement/EC/FP7/282896
   </nameIdentifier>
 </contributor>

Related publications and datasets information¶

OpenAIRE harvests all datasets from a data repository, but exposes only certain datasets in the OpenAIRE portal. See the Set content for specific details of which datasets are exposed.

For example, datasets related to publication will be exposed in the OpenAIRE portal. The link between the dataset and publication may be explicit defined, as described in this section, or automatically inferred by the OpenAIRE infrastructure.

If the link is explicit defined, the dataset will be exposed in the OpenAIRE portal within 1-2 days after harvesting (a repository is harvested once a week on average). If the link is automatically inferred by the OpenAIRE infrastructure it may take up to a month after harvesting before the dataset is exposed in the OpenAIRE portal. It is thus mandatory when applicable to provide links to related publications and datasets when these links are available in the repository, and thereby ensure faster exposure of the dataset in the OpenAIRE portal.

1
2
3
4
5

<relatedIdentifier
  relatedIdentifierType="DOI"
  relationType="IsCitedBy">
 10.1234/bar
</relatedIdentifier>

Embargo date information¶

For OpenAIRE two main types of dates are relevant. When the data were made available, published or uploaded to a formal database, this is the date the data were ‘’Issued’‘.

Sometimes data may be embargoed for a period; this information should be managed by the data provider and expressed by exporting an ‘’Available’’ date to indicate the end of an embargo period and an ‘’Accepted’’ date to indicate the start of an embargo period.

An example:

1
2
3

<dates>
 <date dateType="Issued">2005-04-05</date>
</dates>

An embargo example:

1
2
3
4

<dates>
 <date dateType="Accepted">2011-12-01</date>
 <date dateType="Available">2012-12-01</date>
</dates>