Weekend reads: Hydroxychloroquine paper earns correction; company allegedly fakes COVID-19 data; why retractions fail

Before we present this week’s Weekend Reads, a question: Do you enjoy our weekly roundup? If so, we could really use your help. Would you consider a tax-deductible donation to support Weekend Reads, and our daily work? Thanks in advance.

The week at Retraction Watch featured:

How many papers about COVID-19 have been retracted? We’ve been keeping track, as part of our database. Here’s our frequently updated list.

Here’s what was happening elsewhere:

Like Retraction Watch? You can make a tax-deductible contribution to support our work, follow us on Twitter, like us on Facebook, add us to your RSS reader, or subscribe to our daily digest. If you find a retraction that’s not in our database, you can let us know here. For comments or feedback, email us at [email protected].

5 thoughts on “Weekend reads: Hydroxychloroquine paper earns correction; company allegedly fakes COVID-19 data; why retractions fail”

  1. The US Food and Drug Administration (FDA) “has warned a drug company for data falsification” and environmental issues.

    The link embedded in the above generated the error message below.

    Server Error in ‘/’ Application.
    Index was outside the bounds of the array.
    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

    Exception Details: System.IndexOutOfRangeException: Index was outside the bounds of the array.

    Source Error:

    The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:

    1. Add a “Debug=true” directive at the top of the file that generated the error. Example:

    or:

    2) Add the following section to the configuration file of your application:

    Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.

    Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.

    Stack Trace:

    1. Since this current problem is a server side issue (and will probably be resolved shortly) – there’s precious little RetractionWatch can do about this, as it’s not one of their servers …

      They could, however, return to moderating comments. There’s too much philodoxy, and too little philosophy, in many of the readers’ replies these days. It wasn’t always like this.

      1. number of responses has reduced as well. i was following retraction watch since beginning. now a days, you see some posts without any comments. It is a trend! moderation helps but prevents people from commenting freely. this is what happening on pubpeer too.

  2. “A study of retractions in the life sciences, using PubMed, which the author says is, to the best of her knowledge, “the biggest dataset on retractions in biomedical literature to be studied.” We’d humbly suggest looking at our database, which is far more comprehensive, next time.” – i don’t remember of reading a manuscript without a physical address. of course, this is a practice many newspapers and magazines follow. However, in this manuscript, author hasn’t listed any affiliation nor a physical address. Very odd (at least for me). We have seen many “ghost writers” recently…

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.