karen_w_newton (karen_w_newton) wrote,
karen_w_newton
karen_w_newton

When does a bad review go too far?

Some reviews read more like diatribes than reviews.  The term hatchet job is often bandied about when a reviewer really doesn't like a book. Today's post is about what sounds like a groundbreaking UK lawsuit: an author was awarded damages for a bad book review. This sounds like a dangerous precedent. A basic tenant of reviewing is that the reviewer is allowed to have an opinion and to express it. 

However, if you read about the suit in this post in Slate, you will see the author's victory wasn't because the review was bad;  it was because the review was inaccurate. The book was nonfiction, and the reviewer noted that her own name was listed as being interviewed. She claimed she had not in fact been interviewed, and thus cast doubt on the author's veracity and research. It turned out the reviewer had been interviewed, but she had forgotten about it. 

So, the answer to today's post subject is: A bad review goes too far when the reviewer states an absolute fact that turns out to be totally untrue.  Opinions cannot be proved wrong, but facts can.  Reviewers have an obligation to be right if they state something as fact and not merely opinion.

I have to say I agree with the judge. What do you think?
 





Subscribe

  • The curse of YA, or Why is Harry Potter an orphan?

    I saw a link on Neil Gaiman's Facebook page to this NYT Books section essay about how prevalent bad or missing parents are in YA fiction. It's a…

  • More on "sticky books"

    Since my post of the other day, I have decided that either kids' books are more likely to be inherently sticky or that things we read when young are…

  • And a little child shall lead them

    The subject line refers not to religion, but to publishing. The Washington Post did away with their print Book World standalone section, which used…

  • Post a new comment

    Error

    Anonymous comments are disabled in this journal

    default userpic
  • 7 comments