Reference Linking plugin displaying duplicate DOI if reference already includes one (OJS 3.3.0.8)

Description of issue or problem I’m having:
When we publish a reference list that already includes DOIs, the Crossref Reference Linking Plugin retrieves those DOIs and adds them in duplicate to the citation on article’s landing page.

Look at the second reference in this example:

Bakewell, O. (2008). Research beyond the categories: The importance of policy irrelevant research into forced migration. Journal of Refugee Studies, 21(4), 432–453. https://doi.org/10.1093/jrs/fen042 DOI: https://doi.org/10.1093/jrs/fen042

The first instance of the DOI was included in the text the editor pasted into the References metadata; the second was retrieved by the plugin. The plugin didn’t recognize that the DOI was already included in the citation so now it displays both.

So I have two questions:

  1. Is there anything that can be done to keep the plugin from displaying the duplicate DOI?
  2. Can we fix the existing submissions that have already published without unpublishing them and manually removing the DOIs from the reference list?

Steps I took leading up to the issue:

  1. Install and activate Crossref Reference Linking plugin
  2. Add references with DOIs to the submission metadata
  3. Publish submission

What I tried to resolve the issue:
Nothing - I’m not sure I can do anything about this except request that editors and authors remove DOIs from the submitted reference lists, which brings up its own complications.

Application Version - e.g., OJS 3.1.2:
Crossref Reference Linking plugin v1.0.2.1(2021-03-27)
OJS 3.3.0.8

Additional information, such as screenshots and error log messages if applicable:
I have a hunch that I brought this up a year or two ago (it may even have been resolved) but can’t find the thread now…

Hi @tmrozewski , just wondering if you managed to solve this issue of not displaying duplicated in the landing page. I have seen that they are not displayed in the example that you sent but I am curious if it was fixed by changing the code or if it is a change in the workflow. In that sense, the only workaround that I can see it is to activate the plugin only when new articles are going to be submitted to Crossref using the CrossRef XML Export Plugin.

Best regards,
Daniel

1 Like

I’m not sure how that was resolved - the journal editor may have had an editorial assistant clean up the reference lists manually. This has fallen off my radar as lower priority but, if you’re interested in following up with the devs, you might considering logging an issue in GitHub.

1 Like

Hi @danimon,
did you find an answer to your question here?
I’m facing the same issue you reported.

Thanks in advance