Open jhpoelen opened 4 years ago
Thanks @jhpoelen, I will have a look at this one tomorrow.
Other malformed dois include:
local found malformed doi [0.2307/3565022]
local found malformed doi [110.1007/bf00240204]
local found malformed doi [110.3354/meps084101]
local found malformed doi [NA]
The 4 malformed dois listed above were fixed! Thank you for pointing out @jhpoelen!
@BenMerSci wow that's fast! Just curious - how do you keep track of your data versions?
btw - found another malformed DOI:
found malformed doi [2433/156407]
@jhpoelen, we have a daily dump of the DB but this is not perfect. Do you know some tools for that?
There's many versioning techniques. I am keeping track of all datasets coming into GloBI using content hashes via https://github.com/globalbioticinteractions/elton . I've also seen folks use git to version their datasets. Perhaps something for another thread.
Also, note that I've setup a mangal integration check at https://travis-ci.org/globalbioticinteractions/mangal . You'll find warning like malformed doi in the basic report at the end of the travis log. Scheduled to run weekly.
Hi @jhpoelen, The last malformed DOI that you found ([2433/156407]) was actually the NA one in your first post that I "fixed". It seems though that it isn't, but I don't really understand. If I go for example on https://www.doi.org/ and search the article with [2433/156407], I get the right page to download the associated article. Is it because it doesn't lead directly to the article itself?
According to the DOI specs, a DOI must starts with 10.
. This tells me that 2433/156407
is a malformed DOI.
Through Global Biotic Interactions <> Mangal Integration (see https://github.com/globalbioticinteractions/globalbioticinteractions/issues/81), I found a malformed doi for reference https://mangal.io/api/v2/reference/24 :