Closed Daniel-Mietchen closed 10 years ago
Thanks for bringing this up. This is part of exposing our database, except the way its currently handled it hasn't made it into our database. So this is intstructive for that modelling what we've done.
Max Klein ‽ http://notconfusing.com/
On Wed, Jul 30, 2014 at 1:25 PM, Daniel Mietchen notifications@github.com wrote:
Assigned #24 https://github.com/wpoa/recitation-bot/issues/24 to @notconfusing https://github.com/notconfusing.
— Reply to this email directly or view it on GitHub https://github.com/wpoa/recitation-bot/issues/24#event-147159330.
we have the faillog now http://tools.wmflabs.org/recitation-bot/faillog.html
Just tried to upload http://dx.doi.org/10.7554/eLife.01621 , which was published in June but does not seem to be in PMC yet, so the upload understandably failed: http://tools.wmflabs.org/recitation-bot/10.7554/eLife.01621.html .
There are multiple reasons why uploads may fail, and I am wondering what the best process would be to expose them in a way that is compatible with our bug tracking here on GitHub.
This should integrate with https://github.com/wpoa/OA-signalling/issues/81 .