# Double trouble with DOIs

**URL:** <https://community.crossref.org/t/double-trouble-with-dois/1232>\
**Category:** Content Registration\
**Tags:** metadata, blog, crossref-labs, metadata-quality\
**Created:** [10 March 2020 14:22 UTC](https://community.crossref.org/t/double-trouble-with-dois/1232 "2020-03-10T14:22:14Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Crossref](https://sea2.discourse-cdn.com/flex020/user_avatar/community.crossref.org/crossref/32/31_2.png) [@Crossref](https://community.crossref.org/u/Crossref)\
**Post date:** [10 March 2020 14:22 UTC](https://community.crossref.org/t/double-trouble-with-dois/1232/1 "2020-03-10T14:22:14Z")

</div>

Detective Matcher stopped abruptly behind the corner of a short building, praying that his loud heartbeat doesn’t give up his presence. This missing DOI case was unlike any other before, keeping him awake for many seconds already. It took a great effort and a good amount of help from his clever assistant Fuzzy Comparison to make sense of the sparse clues provided by Miss Unstructured Reference, an elegant young lady with a shy smile, who begged him to take up this case at any cost.

* * *
This is a companion discussion topic for the original entry at [https://www.crossref.org/blog/double-trouble-with-dois/](https://www.crossref.org/blog/double-trouble-with-dois/)

---

<div class="post-metadata">

**Author:** ![arleysoto](https://sea2.discourse-cdn.com/flex020/user_avatar/community.crossref.org/arleysoto/32/1988_2.png) [@arleysoto](https://community.crossref.org/u/arleysoto)\
**Post date:** [13 March 2020 00:20 UTC](https://community.crossref.org/t/double-trouble-with-dois/1232/2 "2020-03-13T00:20:46Z")

</div>

Hi [@Crossref-team](https://community.crossref.org/groups/crossref-team), it is such a good post! It would be nice if you put the figures in table’s format, for a better reading 😉

---

<div class="post-metadata">

**Author:** ![rclark](https://sea2.discourse-cdn.com/flex020/user_avatar/community.crossref.org/rclark/32/19_2.png) [@rclark](https://community.crossref.org/u/rclark)\
**Post date:** [16 March 2020 16:30 UTC](https://community.crossref.org/t/double-trouble-with-dois/1232/3 "2020-03-16T16:30:19Z")

</div>

I’ll share your feedback, Arley! Thanks.

---

<div class="post-metadata">

**Author:** ![rclark](https://sea2.discourse-cdn.com/flex020/user_avatar/community.crossref.org/rclark/32/19_2.png) [@rclark](https://community.crossref.org/u/rclark)\
**Post date:** [24 January 2022 14:35 UTC](https://community.crossref.org/t/double-trouble-with-dois/1232/4 "2022-01-24T14:35:16Z")

</div>



---

<div class="post-metadata">

**Author:** ![rdmpage](https://sea2.discourse-cdn.com/flex020/user_avatar/community.crossref.org/rdmpage/32/643_2.png) [@rdmpage](https://community.crossref.org/u/rdmpage)\
**Post date:** [11 April 2022 07:21 UTC](https://community.crossref.org/t/double-trouble-with-dois/1232/5 "2022-04-11T07:21:05Z")

</div>

I stumbled across this post in a recent Twitter conversation about duplicate DOIs (I can’t post a link but the Tweet is rdmpage/status/1513184259523162119) and I’ve blogged about this issue a number of times. The problem still exists (this community post is two years old). Are there any plans to address the issue? An obvious starting point would be to focus on JSTOR content as this seems to be a common denominator for many of the duplicate DOIs.

---

<div class="post-metadata">

**Author:** ![Crossref](https://sea2.discourse-cdn.com/flex020/user_avatar/community.crossref.org/crossref/32/31_2.png) [@Crossref](https://community.crossref.org/u/Crossref)\
**Post date:** [11 April 2022 07:21 UTC](https://community.crossref.org/t/double-trouble-with-dois/1232/6 "2022-04-11T07:21:05Z")

</div>



---

<div class="post-metadata">

**Author:** ![Ginny](https://sea2.discourse-cdn.com/flex020/user_avatar/community.crossref.org/ginny/32/1694_2.png) [@Ginny](https://community.crossref.org/u/Ginny)\
**Post date:** [22 April 2022 10:37 UTC](https://community.crossref.org/t/double-trouble-with-dois/1232/8 "2022-04-22T10:37:37Z")

</div>

We’ve outlined a few things here in [a new thread](https://community.crossref.org/t/the-problem-with-duplicate-dois-and-how-you-can-help/2634) @rdmpage. And more to follow there too soon. Thanks for highlighting this issue.

---

<div class="post-metadata">

**Author:** ![rdmpage](https://sea2.discourse-cdn.com/flex020/user_avatar/community.crossref.org/rdmpage/32/643_2.png) [@rdmpage](https://community.crossref.org/u/rdmpage)\
**Post date:** [22 April 2022 17:34 UTC](https://community.crossref.org/t/double-trouble-with-dois/1232/9 "2022-04-22T17:34:05Z")

</div>

@Ginny Thanks for the update. Look forward to learning more about the reanalysis. It would also be nice if the publishers and digital libraries involved contributed to this discussion so that the community as a whole can be more aware of the issues.
