Dear publishers: this is how to fix a bug in your platform
September 9, 2013
You know how every time you point out a problem to legacy publishers — like when they’re caught misrepresenting their open-access offerings they explain that it’s very complicated and will take months to fix?
Here’s how that should work:
To summarise: I found a bug in the PeerJ system; I reported it in two tweets (total word-count: 32); 27 hours later, they had fixed it, and our article was showing the end-pages in its bibliography.
Are you watching, Elsevier? 27 hours.
Of course, we do realise that it’s much harder for you. PeerJ have all that manpower, those thousands of people working on their system, while you only have one or two techies, who have all sorts of other duties as well as finding bug-reports on Twitter and immediately fixing them. It’s always tough for the little guy, isn’t it?