Retraction Watch
Retraction Watch is a blog that reports on retractions of scientific papers.[1] The blog was launched in August 2010[2] and is produced by science writers Ivan Oransky (Vice President and Global Editorial Director of MedPage Today[3]) and Adam Marcus (editor of Gastroenterology & Endoscopy News).[4]
Contents
Scope
Oransky and Marcus were motivated to launch the blog to increase the transparency of the retraction process.[5] They observed that retractions of papers generally are not announced, and the reasons for retractions are not publicized.[5] One result is that other researchers or the public who are unaware of the retraction may make decisions based on invalid results. Oransky describes an example of a paper published in Proceedings of the National Academy of Sciences that reported that a certain molecule could cause some types of breast cancers to respond to a drug that would otherwise be ineffective. Although the paper was retracted, its retraction was not reported in the media outlets that had reported on its conclusions, and before it was retracted a company had been established to make use of the reported discovery.[6]
The blog argues that retractions provide a window into the self-correcting nature of science, and can provide insight into cases of scientific fraud.[7] Its operators say that as science journalists, they have "found retractions to be the source of great stories that say a lot about how science is conducted."[6]
Case discussions
When asked why a particular paper published in the Journal of the American Chemical Society had been retracted, the author told Retraction Watch that an error in the study had been discovered after publication, and that the technique he had described in the paper as an advancement was actually no more useful than the existing technique.[8] Science journalist Ben Goldacre commented, "That's useful information, much more informative than the paper simply disappearing one morning," noting that the retracted paper had already been cited 14 times "by people who believed it to be true."[8]
Watch view
Some journal editors are unwilling to respond to enquiries from Retraction Watch. On one single instance, when contacted about a retracted paper, the editor of one medical journal told the blog: “It’s none of your damn business,” and that retraction notices were issued “to inform our readers that the article is retracted," and: "if you get divorced from your wife, the public doesn’t need to know the details".[9]
Impact
Retraction Watch has demonstrated that retractions are more common than was previously thought.[6] When Retraction Watch was launched, Marcus "wondered if we’d have enough material".[10] It had been estimated that about 80 papers were retracted annually.[6] However, in its first year, the blog reported on approximately 200 retractions.[11] Retraction Watch has garnered praise[2][12] as useful to aspiring scientific journalists or people interested in the issue of accuracy."[5][8] In December 2014, the blog received a $400,000 grant from the MacArthur Foundation.[13]
See also
References
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 2.0 2.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Ivan Oransky Bio on Retraction Watch Retrieved Feb 5, 2015.
- ↑ Adam Marcus Bio on Retraction Watch Retrieved Feb 5, 2015.
- ↑ 5.0 5.1 5.2 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 6.0 6.1 6.2 6.3 Kelly Oakes, Helping journalists track retractions: one year of Retraction Watch, Association of British Science Writers, 20 August 2011
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 8.0 8.1 8.2 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
