Retraction Watch

Tracking retractions as a window into the scientific process

The Retraction Watch 2016 year in review — and a sneak peek at our database

with 6 comments

It’s been another exciting year for us at Retraction Watch. As always, there has been more to cover than we have time for. At the same time, we’ve expanded our efforts in other media, telling bigger stories and offering more analysis. And we’ve made major progress on our database — more on that in a moment.

A sampling of what happened this year:


  • We launched The Retraction Watch Daily, a digest of our posts from the previous day, and a sneak peek at some of our Weekend Reads. (You haven’t signed up yet? Click here, we’ll wait.)





  • We began a partnership with Science, to contribute in-depth investigations and other pieces to their news section. Here’s an example, about a case at Duke involving hundreds of millions of dollars in grants.


  • Thanks to the support of the Helmsley Trust, we completed a strategic planning process. Stay tuned in 2017 as we begin to implement parts of the resulting plan.


  • We published a piece in Nautilus on fake authorship. We had fun with this one — as did many of the people involved in the phenomenon, which included an fictional character from a hit television show.

And now, a sneak peek at something we know a lot of readers have been eagerly awaiting (as have we!): Our retraction database, being built with the generous support of the MacArthur and Arnold Foundations. It’s still a work in progress; we have a lot more retractions to enter, and we’ll be fixing bugs and adding functionality, but go to for a taste. You can search by country, author, DOI, reason for retraction, journal, and many more criteria. As always, we welcome your feedback.

Now, some numbers:

  • Cumulative page views since our launch in August 2010: More than 25 million
  • Subscribers to our email alerts: More than 13,000
  • Facebook likes: More than 20,000
  • Twitter followers: More than 16,000

And the numbers we’re most grateful for: More than 70 individual donors made gifts to The Center For Scientific Integrity, totaling more than $12,000. That unrestricted funding will allow us to grow even more in 2016. It’s not too late to make an end-of-year tax-deductible donation, either. Here’s how.

As we say frequently, but not often enough, we couldn’t have done any of this without our readers — including our critics — and our fantastic, dedicated staff. Thank you, and all the best in 2017!

Like Retraction Watch? Consider making a tax-deductible contribution to support our growth. You can also follow us on Twitter, like us on Facebook, add us to your RSS reader, sign up on our homepage for an email every time there’s a new post, or subscribe to our daily digest. Click here to review our Comments Policy. For a sneak peek at what we’re working on, click here.

Written by Ivan Oransky

December 30th, 2016 at 11:30 am

Posted in RW announcements

  • Neuroskeptic December 30, 2016 at 3:30 pm

    Great work on the database! This could be a real game changer. A few remarks/suggestions on the current version:

    1) The “reasons for retraction” categories need tweaking. For example there’s a category “Image – Plagiarism/Duplication”, but authors duplicating their own images is not plagiarism; it would make more sense to group this with image manipulation as they often go together. As it stands searching for “plagiarism” returns lots of irrelevant image duplication hits.

    2) Some authors appear in the author drop down menu multiple times. E.g. Y Fujii appears as “Fujii, Y.” “Fujii, Yoshitaka” and “Fujii., Y.”

    3) When viewing an entry, it would be useful if you could click on an author’s name to see all of their other retractions (if any). Also would it be possible to append the retraction count after each author’s name e.g. Yoshitaka Fujii (150)

    • Ivan Oransky January 1, 2017 at 3:14 pm

      Thanks, NS! Great feedback, here are some responses:

      1) Agreed that these are a work in progress; will take these comments into account as we tweak.
      2) Indeed; this is happening as we make entries, but it will be cleaned up as we go.
      3) Stay tuned, that’s planned for the next phase of development.

  • Scott December 31, 2016 at 11:40 am

    Will the database have an API? It would be great to have it to make other applications (e.g. a Chrome Extension that flags retracted papers when searching on Google Scholar).

    • Ivan Oransky January 1, 2017 at 3:15 pm

      Agreed. Definitely in the plan for a later phase of development — thanks.

    • Matthias November 17, 2017 at 4:05 am

      Seconded. Yes please REST API.

  • Richard Smith-Unna April 7, 2017 at 2:34 pm

    Ivan, the database is a great idea. Would you consider making the data open? This could be used in so many ways – if you just post the data to somewhere public, people can build APIs and tools around it, and it won’t cost you anything to maintain apart from the data collation.

  • Post a comment

    Threaded commenting powered by interconnect/it code.