It should be possible to edit it, so this definitely sounds like a bug. Thanks for sharing the error you did see. Is there any further detailed information in the network tab in the developer tools?
I’m also wondering if this happens with any DOI you’re attempting to edit or only with this specific one.
Hi @ewhanson ,
indeed, there is an error in the console.
There were only a few times when I had to edit DOIs, so as far as I remember some of them were edited without problems some of them were also reverting back to the root prefix… But I don’t remember clearly…
But the situation is strange for me…
I check the mistyped DOI by opening the URL: https://doi.org/10.XXXXX/.XYZ.2024.06.005
it points to the article, that’s OK, how should be.
But if I open the “right” DOI, to which I want to change the mistyped DOI by entering this URL https://doi.org/10.XXXXX/Q.XYZ.2024.06.005
I also get forwarded to the same article…
Thanks @Garant, that’s helpful. I’m not sure how this would have happened, but the “right” DOI is already in use somewhere in your installation, which is why you can’t add it to correct the mistyped one.
To dig into this, you may need to check in the database manually, unless you can easily see on the same item that another publication/galley is using the “right” DOI.
To see where this is happening, you can run the following SQL query (with your actual, “right” DOI instead of the placeholder prefix:
select * from dois where doi = '10.XXXXX/Q.XYZ.2024.06.005'
With any luck, this should return at least one DOI. You can then try and find where it’s already in use. It will be a doi_id in one of these tables: publications, publication_galleys, or issues. If it was accidentally added to something you didn’t mean, it will most likely be okay to delete that row in the database, edit the mistyped DOI, and resubmit.
Of course, before you make any changes to the database, make sure you have made appropriate backups and are able to restore the database if anything goes wrong.
Hope that helps. If you have any other questions about this, feel free to ask!
The table dois should be there, did he choose the database (“use” statement) before executing the select query.
Has the wrong doi and the associated metadata already been registered with Crossref?
Then registering with the correct DOI should lead to a conflict there, which you have to resolve with Crossref.
Hi @Garant, thanks for sharing. Since you found the DOI, the next step will be seeing what it is currently associated with. You could try the following query to see what publication/submission the DOI is associated with, and from there look in the OJS interface.
select * from publications where doi_id = 1500;
This will let you know the publication ID and submission ID for the item that is using this DOI. From there, you should be able to find it within OJS and remove it once you know which submission it belongs to.
Yes. A once registered DOI shouldn’t be changed (it’s persistent identifier), and changing it will create a conflict that you have to resolve within Crossref’s administration UI.