JabRef / jabref

Graphical Java application for managing BibTeX and biblatex (.bib) databases
https://devdocs.jabref.org
MIT License
3.6k stars 2.57k forks source link

Creating entry via mEDRA (using DOI) doesn't work #7673

Closed sparusaurata closed 3 years ago

sparusaurata commented 3 years ago

When I try to create a new entry by giving a DOI with the mEDRA service, an error is raised:

image

… even if the DOI resolver at mEDRA.org finds the reference.

Siedlerchr commented 3 years ago

Thanks for your report. It seemed maybe some temporary issue, or might be specific to your DOI. I tested a few DOIs with medra, but works for me. Can you please post your DOI here you tried?

mlep commented 3 years ago

I tried with this one: 10.5194/npg-24-569-2017 JabRef replies that mEDRA did not find any entry, but it works on mEDRA website.

JabRef 5.3--2021-04-26--add694a Linux 4.19.0-16-amd64 amd64 Java 15.0.2 JavaFX 16+8

Siedlerchr commented 3 years ago

Just use the normal DOI fetcher. JabRef will automatically check if the DOI belongs to medra or not. However, yours belongs to crossref and JabRef gets a HTTP 504 error, gateway timeout, so a problem on the CrossRef site. Totally odd.

sparusaurata commented 3 years ago

Can you please post your DOI here you tried?

I tried this one: 10.1016/0304-3975(95)00073-6.

Just use the normal DOI fetcher.

This what I initially wanted to do, but it didn't work (see here) so I used mEDRA as indicated in the docs.

Siedlerchr commented 3 years ago

I cannot reproduce this. The normal DOI fetcher works fine for me with your DOI. Mabye it was a temporary issue at CrossRef

mlep commented 3 years ago

Using Library --> New entry, both DOI (i.e. 10.5194/npg-24-569-2017 and 10.1016/0304-3975(95)00073-6) works using the ID type Crossef and DOI, but not using mEDRA. Any idea how long "temporary" could be?

ruanych commented 3 years ago

I ran some tests:


mEDRA url: https://data.medra.org/10.3303/CET2184030


mEDRA url: https://data.medra.org/10.5194/npg-24-569-2017


Maybe this is a problem with mEDRA's API?

Siedlerchr commented 3 years ago

@Ryyyc You can test also with 'Accept: application/x-bibtex'

ruanych commented 3 years ago

@Ryyyc You can test also with 'Accept: application/x-bibtex'

The response of test https://data.medra.org/10.3303/CET2184030 with 'Accept: application/x-bibtex' is still 200 OK.

C:\Users\ruan>curl -I -H "Accept: application/x-bibtex" https://data.medra.org/10.3303/CET2184030
HTTP/1.1 200 OK
Date: Fri, 07 May 2021 15:22:53 GMT
Server: Apache-Coyote/1.1
Cache-Control: no-transform, max-age=60
Access-Control-Allow-Origin: *
Vary: Accept
Content-Type: application/x-bibtex;charset=UTF-8

C:\Users\ruan>curl -H "Accept: application/x-bibtex" https://data.medra.org/10.3303/CET2184030
 @article{Salvoni Daniela_Boselli Antonella_Sannino Alessia_Parlato Loredana_Ejrnaes Mikkel_Chengjun Zhang_You Lixing_Wang Xuan_Amoruso Salvatore_Pepe Giovanni Piero_2021, place={IT}, title={Demonstration of Atmospheric Lidar Measurement in the Infrared Wavelength Domain with a Superconducting Nanowire Single Photon Detector}, volume={84}, url={https://doi.org/10.3303/CET2184030}, DOI={10.3303/CET2184030}, journal={Chemical Engineering Transactions}, publisher={AIDIC: Italian Association of Chemical Engineering}, author={Salvoni Daniela and Boselli Antonella and Sannino Alessia and Parlato Loredana and Ejrnaes Mikkel and Chengjun Zhang and You Lixing and Wang Xuan and Amoruso Salvatore and Pepe Giovanni Piero}, year={2021}, month={Apr}, pages={175–180} }


The response of test https://data.medra.org/10.5194/npg-24-569-2017 with 'Accept: application/x-bibtex' is still 404 Not Found.

C:\Users\ruan>curl -I -H "Accept: application/x-bibtex" https://data.medra.org/10.5194/npg-24-569-2017
HTTP/1.1 404 Not Found
Date: Fri, 07 May 2021 15:22:40 GMT
Server: Apache-Coyote/1.1
Access-Control-Allow-Origin: *
Siedlerchr commented 3 years ago

I think this is something on the Medra/DOI publisher side. I had this problem with other EU publications as well, they did not return bibtex but html from the website despite the Accept header. Maybe you can contact the support and ask them