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

DataCite Researcher Profiles

DataCite Researcher Profiles provides insight into data level metrics by researcher.

How it works

A researcher that has openly published research datasets can now find out many times these published datasets have been viewed, downloaded, and cited by visiting their DataCite Researcher Profile page.

Example Researcher Profile:

How to access

To access Research Profiles navigate to: +RESEARCHER_ORCID_ID

What information is available there

Under the Info tab you will see a dashboard with a summary of the researcher's DOIs by year, DOIs by resource type, Citations, Views and Downloads.

Researcher Profiles Dashboard

In the Settings tab you can see the ORCID iD, Given Name and Family Name of the researcher.

Under the DOIs tab you will see the list of all the DOIs where the researcher ORCID iD appears in the metadata. You can filter by Resource Type, Year Published and Repository using the facets on the left. You can sort the DOIs by Date Updated and Date Created by selecting from the menu on the top right.


This work is supported by the Belmont Forum as an output of the PARSEC project, with funds specifically provided by the National Science Foundation under Grant Number 1929464


I can not find all my resources under the DOIs tab, Why?

Currently, the list includes only resources with your ORCID id in their DOI metadata. In the near future, we will include resources claimed via Datacite Search. For more information about claiming visit the ORCID claim page


Would you like to know more?

If you have any questions, requests or ideas please contact us!

Updated about a month ago

DataCite Researcher Profiles

Suggested Edits are limited on API Reference Pages

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