Latest blog posts
Fabienne Michaud
2021 September 20

Similarity Check news: iThenticate v2.0 ready for launch

Crossref Similarity Check news: iThenticate v2.0 ready for launch Last year, we announced the upcoming launch of a new version of iThenticate, the product from Turnitin that powers Crossref Similarity Check. We know some of you have been waiting a long time for this upgrade and we are very happy to share with you that we are now ready to release it. We will be rolling out this new version in stages, so not everyone will be able to upgrade to the new version immediately.

...Find out more
Isaac Farley
2021 September 08

Lesson learned, the hard way: Let’s not do that again!

TL;DR We missed an error that led to resource resolution URLs of some 500,000+ records to be incorrectly updated. We have reverted the incorrect resolution URLs affected by this problem. And, we’re putting in place checks and changes in our processes to ensure this does not happen again. How we got here Our technical support team was contacted in late June by Wiley about updating resolution URLs for their content. It’s a common request of our technical support team, one meant to make the URL update process more efficient, but this was a particularly large request.

...Find out more
Rosa Clark
2021 August 20

Crossref Conversations: audio blog about helping open science

Crossref Conversations is an audio blog we’re trying out that will cover various topics important to our community. This conversation is between colleagues Anna Tolwinska and Rosa Morais Clark, discussing how we can make research happen faster, with fewer hurdles, and how Crossref can help. Our members have been asking us how Crossref can support open science, and we have a few insights to share. So we invite you to have a listen.

...Find out more
Ginny Hendricks
2021 July 26

Some rip-RORing news for affiliation metadata

We’ve just added to our input schema the ability to include affiliation information using ROR identifiers. Members who register content using XML can now include ROR IDs, and we’ll add the capability to our manual content registration form, participation reports, and metadata retrieval APIs in the near future. And we are inviting members to a Crossref/ROR webinar on 29th September at 3pm UTC. The background We’ve been working on the Research Organization Registry (ROR) as a community initiative for the last few years.

...Find out more
  • Menu
search

Documentation

Reports

For anyone using any of our reports, please consider completing this survey by 1 July 2021 to help us improve our reporting.

Our reports are tools to help you evaluate and improve your metadata. The dashboard gives an overview of our ever-growing corpus of metadata. How good is your metadata? Find out using Participation Reports and other reports to evaluate your metadata records, check for any issues, and learn how to resolve them.

Some reports are sent to you by email, and some are available on our website.

Reports by email

We send reports by email from reports@crossref.org to specific contacts on your account. Do add this address to your email contacts list or safe senders list to ensure that you receive them. These reports are intended to help you keep your metadata records up-to-date, and include:

  • Conflict report - this report shows where two (or more) DOIs have been submitted with the same metadata, indicating that you may have duplicate DOIs. You’ll start receiving conflict reports if you have at least one conflict. These reports are sent out on a monthly basis, or more frequently if your number of conflicts peaks by over 500, and it is sent to the main Technical contact on your account.
  • DOI error report - a DOI error report is sent immediately when a user informs us that they’ve seen a DOI somewhere which doesn’t resolve to a website, and it is sent to the main Technical contact on your account.
  • Resolution report - this monthly report shows the number of successful and failed DOI resolutions for the previous month, and it is sent to the Primary contact on your account (please note - this contact used to be known as the Business contact).
  • Schematron report - the main Technical contact on your account may also receive periodic Schematron reports if there’s a metadata quality issue with your records.

If you aren’t receiving reports, please check the emails aren’t being caught by your spam filter. It might also be because we our contact information for your organization is not current, or you aren’t the designated reports person in our database. Please contact us and we’ll sort it out for you.

If you are not the appropriate person to receive reports, we can send reports to a different email address. If you don’t find our reports useful, please contact us and we’ll see what we can do.

If you need information about something that’s not covered by your reports, please explore all the information you can access through our REST API, or contact us for help.

Reports available on our website

These reports are available on our website:

Page owner: Isaac Farley   |   Last updated 2021-June-01