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

Missed conflict report

Learn more about conflicts and the conflict report. Conflicts are usually flagged upon deposit, but sometimes this doesn’t happen, creating a missed conflict.

A missed conflict may occur for several reasons:

  • Two DOIs are deposited for the same item, but the metadata is slightly different (DOI A deposited with an online publication date of 2011, DOI B deposited with a print publication date of 1972)
  • DOIs were deposited with a unique item number. Before 2008, DOIs containing unique item numbers (supplied in the <publisher_item> element) were not checked for conflicts.

The missed conflict report compares article titles across data for a specified journal or journals. To retrieve a missed conflict report for a title:

  1. Start from the browsable title list and search or browse for the title
  2. Click the Blue chevrons right icon icon at the far right of the title
  3. The missed conflict interface will pop up in a second window. Enter your email address in the appropriate field. Multiple title IDs can be included in a single request if needed

A report will be emailed to the email address you provided. This report lists all DOIs with identical article titles that have not been flagged as conflicts.

Page owner: Isaac Farley   |   Last updated 2020-April-08