Closed clbarnes closed 2 years ago
This is now implemented. :tada:
I got most of the way through an implementation too, but stalled when it turned out openretractions' database is very patchy. I picked a few DOIs from retractionwatch's top 10 most cited and openretractions had none of them, even thought they seem to have been reported correctly on pubmed/ crossref. It may be worth mentioning which database your implementation uses in the docs so that people can be aware of any caveats associated with it.
Add this to the readme and help. Let me know if you find any better site for this.
I did contact retractionwatch about making their data available over an API; they said it's something they'd like to do and existed somewhere on the backlog but wasn't a priority and they had limited dev time.
Ha, I feel that. :smile_cat:
The largest retraction database (retractionwatch) doesn't have an API, but openretractions does. A tool to go through your .bib and raise retractions and other updates would be valuable, and should only require the DOI.