"Open" leads to Error: DOI Not Found even with full URL

[ror3d]

JabRef version

Latest development branch build (please note build date below)

Operating system

Windows

Details on version and operating system

Windows 11

Checked with the latest development build (copy version output from About dialog)

• [X] I made a backup of my libraries before testing the latest development version.
• [X] I have tested the latest development version and the problem persists

Steps to reproduce the behaviour

1. Create a new entry
2. In the General tab, under DOI, set the URL to either
   • https://dl.acm.org/doi/10.5555/846276.846298
   • https://dl.acm.org/doi/10.5555/3295222.3295349
3. Notice that click the button next to the DOI "Get bilbiographic data from DOI" produces error "No data was found for the identifier"
4. Notice that click the button next to the DOI "Open" opens the DOI website with error "DOI NOT FOUND"

Notes

It seems that 10.5555 is assigned to crossref.org and that they use it for testing, or something like that (according to https://community.crossref.org/t/how-can-i-get-a-list-of-all-doi-for-a-prefix/943 ). I don't know why ACM would use that prefix for some articles.

Expected behaviour Since in the DOI field there's the full URL to the article, at least the "Open" button should actually open the website there. I understand that seeing how these DOI are not recognized by doi.org, it might not be feasible to get the information from them from whatever service though.

Appendix

No response

[Siedlerchr]

Hi,

Urls belong in the URL field. JabRef will display an option to open the link.

Alternatively, you can add an URL in the file field. For DOIs we have a cleanup to remove the URL part etc. as well. DOIs are opened using doi.org

Your special case appears to be a weird case from ACM. I don't know why they use that weird doi as part of the URL. When I export that bibtex I don't even see the DOI filled.

[ror3d]

Well the DOI field seems to support having DOI urls in it, that's the cause of the confusion, because with other URLs it would just open the correct DOI path, but with these it opens the wrong page (tries to go through doi.org even though going through the URL should work fine)

[koppor]

I tried https://doi.org/10.5555/846276.846298, but that is 404. What did I do wrong? 😅

[koppor]

Same for https://doi.org/10.5555/3295222.3295349

Confusion by ACM, because they use DOIs NOT governed by the DOI foundation?! - https://www.doi.org/

[koppor]

Do you have contact to ACM / the journal editors and clarify why ACM could not manage to get official DOIs for the articles? 😅

[ror3d]

My understanding is that the 10.5555 is assigned to crossref.org (inputting the prefix in https://dx.doi.org gives this)

But from the post I linked before, crossref.org uses that prefix only for testing or something like that.

And I guess ACM might use crossref behind the scenes for something and somehow have been using this prefix when they maybe shouldn't have. I honestly don't understand either.

I don't have direct contact with anyone there, I am not sure how I'd reach them easily, but there's probably some email to contact for stuff like this... maybe the one for crossref that's in the doi screenshot I posted

[koppor]

In short: Wish: If there is a full URL in the DOI field, that URL should be used to open the link, not the parsed DOI. -- Reason: Publishers share incorrect DOIs, which work "locally", which should also be supported by JabRef.