Old DOIs become unactive

Description of issue or problem I’m having:
Old DOIs from 2018 and older are suddenly not active anymore.
They were deposited in the past by CrossRef XML Export Plugin.
In the Plugin shows just 4 articles from 2017 that are suddenly Failed. Plugin is not showing the problem with all other articles (but they are existing).

Steps I took leading up to the issue:
I tryed to reload reactive them. But with no success.
I tryied to activate/deactivate plugins: Scopus/Crossref Plugin, Crossref Reference Linking, CrossRef XML Export Plugin.
With no succes.

What I tried to resolve the issue:
I wrote also for help to Crossref, do not know if issue is on their or OJS site.

Application Version - e.g., OJS 3.1.2:
We are using OJS 3.3.0.5.

Additional information, such as screenshots and error log messages if applicable:
Message from the 4 failed DOI:
Record not processed because submitted version: 1634117037 is less or equal to previously submitted version 201710051443

<?xml version="1.0" encoding="UTF-8"?>

<doi_batch_diagnostic status=“completed” sp=“ds4.crossref.org”>
<submission_id>1510030515</submission_id>
<batch_id>_1634117037</batch_id>
<record_diagnostic status=“Failure” msg_id=“4”>
10.14528/snr.2017.51.3.194
Record not processed because submitted version: 1634117037 is less or equal to previously submitted version 201710051443
</record_diagnostic>
<batch_data>
<record_count>1</record_count>
<success_count>0</success_count>
<warning_count>0</warning_count>
<failure_count>1</failure_count>
</batch_data>
</doi_batch_diagnostic>

Thank you for any suggestion.
Martina

Hi @martinca

The crux of the issue here is this:

Record not processed because submitted version: 1634117037 is less or equal to previously submitted version 201710051443

This is related to the timestamp on your deposit. Crossref checks to make sure that updates to a DOI happen after the original deposit. But, the issue is that the format of your original timestamp is different than the format of the timestamp in OJS now.

Basically, 1634117037 is a smaller number than 201710051443, so it must be older.

You can fix this by contacting Crossref support and requesting a timestamp reset. They’ll need a list of all the affected DOIs, but it’s an easy fix on their end and you should then be able to deposit/update these.

Best,
Mike

1 Like

Thank you Mike for your kind help!

Now, I just found out, with also help of Crossref support, that 4 “failed” DOIs in Crossref Plugin are now working.

But all other 70 DOIs are still not opening.
Crossref Plugin is showing them as active, as the same is on Crossref Membership Record history. But in reality they are not responding.
I suspect: it would be possible that there would be error connected to Scopus/Crossref Plugin or Crossref Reference Linking? Would be possible that this plugins in the backgrounds are causing some problems?

Example of some not working DOIs:
https://doi.org/10.14528/snr.2017.51.3.178
https://doi.org/10.14528/snr.2018.52.2.207
https://doi.org/10.14528/snr.2018.52.1.184
https://doi.org/10.14528/snr.2016.50.4.128

Thank you very much in advance for any suggestion how to resolve this problem!

Martina

1 Like

Hi @martinca,

I believe you have an issue with your server configuration. I think your domain isn’t configured correctly.

This is the URL associated with these DOIs:

http://obzornik.zbornica-zveza.si:5050/index.php/ObzorZdravNeg/article/view/207

That :5050 shouldn’t be in your domain, but I suspect it’s somewhere in your journal or server configuration files. OJS is assigning that URL to all these DOIs. I’d ask your system admin folks if they know how that :5050 is ending up in your exports.

1 Like