Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jabref flagging NASA DOI as invalid #6932

Closed
NRJank opened this issue Sep 21, 2020 · 7 comments
Closed

Jabref flagging NASA DOI as invalid #6932

NRJank opened this issue Sep 21, 2020 · 7 comments

Comments

@NRJank
Copy link

NRJank commented Sep 21, 2020

JabRef 5.1--2020-08-30--e023aa0
Windows 10 10.0 amd64
Java 14.0.2

(same issue on previous JabRef 4.3.1)

NASA DOI is flagged as invalid, so links to open/lookup/get bibtex data, etc., are disabled.

Steps to reproduce the behavior:

  1. create new article
  2. put NASA DOI in DOI feild, e.g., 2060/19660017401
  3. valid doi resolves to http://dx.doi.org/2060/19660017401 at https://ntrs.nasa.gov/citations/19660017401

gets flagged with "DOI 2060/19660017401 is invalid" error.

@NRJank NRJank changed the title Jabref Jabref flagging NASA DOI as invalid Sep 22, 2020
@Siedlerchr
Copy link
Member

Siedlerchr commented Sep 22, 2020

I tested this with the 5.2 snapshot.
FIrst of all, JabRef's statement that the above mentioned DOI is invalid, is correct.
JabRef follows the DOI spec and the DOI spec says that it needs a prefix with "10".

I have no idea and could not find any further information on this and how this works
It should be possible to search for the documents using the SOA/NASA database fetcher in JabRef.

@NRJank
Copy link
Author

NRJank commented Sep 22, 2020

Interesting. I was surprised to see the format myself, but doi.org seems to have no problem with it. The spec does state that DOIs use 10. and that part of ISO 26324 is paywalled. Nonetheless, Nasa uses 2060 and DOI resolves it for them.

@Siedlerchr
Copy link
Member

Yeah, never seen that before. I also tested the API resolving manually, but it only returns some part HTML content and no bibtex.
However, you can probably use the above fetcher or you can search using https://ui.adsabs.harvard.edu/

@NRJank
Copy link
Author

NRJank commented Sep 22, 2020

i dropped an inquiry to doi.org since that seems in conflict with their stated naming convection. we'll see if they respond.

@NRJank
Copy link
Author

NRJank commented Sep 22, 2020

from DOI.org staff:

"The identifier you have cited for the NASA Technical Report is a handle, not a DOI. The DOI System is a specific implementation of the Handle System. Handles should be resolved on the web via the Handle System Proxy, in this case that URL would be https://hdl.handle.net/2060/19660017401 and not the DOI proxy. While handle and DOI resolution on the web are similar, the proxy servers do not have identical functionality. You are correct that an identifier, even if appended to https://dx.doi.org, that does not begin with a 10. prefix is not a DOI. It is possible that NASA is also a member of a DOI Registration Agency and does assign DOIs to some of their publications. This particular technical report has been given a handle."

@Siedlerchr Siedlerchr reopened this Sep 22, 2020
@Siedlerchr
Copy link
Member

Thanks for posting the response.
That explains a lot. In short handles are just some kind of persistent unique identifier for managing urls or other resources.
I read a bit about that and it seems like DOI is a special implementation of a handle system
https://project-thor.readme.io/docs/project-glossary

To sum up, JabRef's behavior is correct.

@NRJank
Copy link
Author

NRJank commented Sep 22, 2020

seems so. Jabref -could- manage handles in general, but there's a URL field for that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants