Deprecated: Creation of dynamic property Automattic\Jetpack\Connection\Manager::$error_handler is deprecated in /home4/onceand4/public_html/wp-content/plugins/jetpack/vendor/automattic/jetpack-connection/src/class-manager.php on line 93

Deprecated: Creation of dynamic property Automattic\Jetpack\Sync\Queue::$random_int is deprecated in /home4/onceand4/public_html/wp-content/plugins/jetpack/vendor/automattic/jetpack-sync/src/class-queue.php on line 40

Deprecated: Creation of dynamic property Automattic\Jetpack\Sync\Queue::$random_int is deprecated in /home4/onceand4/public_html/wp-content/plugins/jetpack/vendor/automattic/jetpack-sync/src/class-queue.php on line 40

Deprecated: Creation of dynamic property Publicize_UI::$in_jetpack is deprecated in /home4/onceand4/public_html/wp-content/plugins/jetpack/modules/publicize.php on line 53

Deprecated: Creation of dynamic property Jetpack_Likes::$in_jetpack is deprecated in /home4/onceand4/public_html/wp-content/plugins/jetpack/modules/likes.php on line 54

Deprecated: Creation of dynamic property Jetpack_Likes_Settings::$in_jetpack is deprecated in /home4/onceand4/public_html/wp-content/plugins/jetpack/modules/likes/jetpack-likes-settings.php on line 7

Deprecated: Creation of dynamic property Jetpack_Likes::$settings is deprecated in /home4/onceand4/public_html/wp-content/plugins/jetpack/modules/likes.php on line 55

Deprecated: Creation of dynamic property Jetpack_Shortcode_Unavailable::$shortcodes is deprecated in /home4/onceand4/public_html/wp-content/plugins/jetpack/modules/shortcodes/unavailable.php on line 19

Deprecated: Return type of Requests_Cookie_Jar::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/onceand4/public_html/wp-includes/Requests/Cookie/Jar.php on line 63

Deprecated: Return type of Requests_Cookie_Jar::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/onceand4/public_html/wp-includes/Requests/Cookie/Jar.php on line 73

Deprecated: Return type of Requests_Cookie_Jar::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/onceand4/public_html/wp-includes/Requests/Cookie/Jar.php on line 89

Deprecated: Return type of Requests_Cookie_Jar::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/onceand4/public_html/wp-includes/Requests/Cookie/Jar.php on line 102

Deprecated: Return type of Requests_Cookie_Jar::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/onceand4/public_html/wp-includes/Requests/Cookie/Jar.php on line 111

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/onceand4/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 40

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/onceand4/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 51

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/onceand4/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 68

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/onceand4/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 82

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/onceand4/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 91
 On Reviewing, and Reviews « Once & Future
Deprecated: preg_split(): Passing null to parameter #3 ($limit) of type int is deprecated in /home4/onceand4/public_html/wp-content/plugins/jetpack/_inc/lib/class.media-summary.php on line 420

Deprecated: preg_split(): Passing null to parameter #3 ($limit) of type int is deprecated in /home4/onceand4/public_html/wp-content/plugins/jetpack/_inc/lib/class.media-summary.php on line 420

Deprecated: preg_split(): Passing null to parameter #3 ($limit) of type int is deprecated in /home4/onceand4/public_html/wp-content/plugins/jetpack/_inc/lib/class.media-summary.php on line 420

Once & Future

Charlotte Ashley – Book seller, collector, writer, editor, historian

March 19, 2010

On Reviewing, and Reviews

The latest Quill & Quire (probably the best issue in years, and worth a read if you can find one) features an essay from Richard Bachmann, recently retired bookseller, in which he says the following:

The other…concern is the disappearance of avenues to tell people about books.  Superficially, it might seem that the new media have made available more channels of information than ever before.  I don’t believe this is an advantage.  Having a multitude of un-vetted book blogs is not quite the same thing as real discourse.”

He is lamenting, as most of us are, the death of newspaper book sections in particular, but more central, “legitimate” literary reviews in general.  I agree with his sentiment and maybe even his statement.

There are a lot of book blogs out there.  Even in the small sub-category of Canadian Book Blogs By Readers there are seemingly endless choices.  It’s easy and fun to read and review books and most of us do it.  But how does this add to the literary or publishing ecosystem?  I am absolutely guilty of talking more than I listen – I write reviews as if anyone might care, but I actually tend not to read blogs which simply review books.  Maybe this reflects my own interest, but I tend more towards blogs which provide “original content” in the form of essays and analysis rather than reviews or links elsewhere.  Where I do read reviews, shamefully, it tends to be to compare that reader’s thoughts to my own on books I have already read, rather than to evaluate a book for potential future purchase.

It isn’t that I don’t read reviews elsewhere either.  I am a fanatic reader of the TLS and frequently order books I have seen covered there.  Why should a book blog review be any different?

But it is different.  Bachmann is quite right – though a few comments to a blog post might constitute a very limited dialogue, this is nothing compared to the edifying and influential exchanges that occur through the TLS’s (or NYRB‘s) letters pages.  There’s a certain feeling of witnessing cultural formation before your eyes that you get from a “legitimate” source that feels lacking in blogs.  The conversation is too, to use Bachmann’s word, “diffuse”.  While this allows for wider coverage, it also pulls the conversation apart into disparate, self-selecting pieces.  Do writers Google themselves to see which blogs have reviewed them?  Do they care?  Would they respond to criticism?  Will anyone defend or contradict them?

What do we provide here?  I have a sneaking suspicion that the majority of my readers are either book bloggers themselves, or else publicists.  We’re people on the production, rather than purchasing, end.  Are we capable of reaching a wider public?  Do we help?  Publicists are certainly betting that we will – there’s a real upswing in promo copies going out to bloggers I’d reckon.  Whether this is speculation on the publishers’ part or if they have data to confirm that our special form of word-of-mouth actually translates into sales, I don’t know.

A suspect there’s a benefit to our coverage of small releases, based on my own limited data.  Publicists – take note!  My review of Frank Newfeld’s Drawing on Type is one of my most-viewed reviews, and certainly one of the most searched reviews.  That is to say, people search for “Frank Newfeld” or “Drawing on Type” and find my review.  On the other hand, my review of Val Ross’s Robertson Davies: A Portrait in Mosaic has been viewed three times as many times, but almost never because someone was actually searching for “Val Ross”, “Robertson Davies” or anything that might actually suggest this book.  So my review of Drawing on Type was probably more effective, from a publicity standpoint, than was my review of Robertson Davies.  This is probably because very few “big” reviews were out there, and my limited contribution was all that could be found.

This does not, however, suggest that small press publishing benefits from the bloggosphere.  We’re still talking about tiny numbers, and no conversation.  My review, after all, was not especially flattering.  Where’s the rebuttal?  I have been debateably harmful to Porcupine’s Quills’s sales.  This is not a healthy literary ecosystem.

But these are my limited numbers.  Perhaps some of you have had different experiences?  Do you read reviews online?  Do they make a difference to you?  Do we render a valuable service or a poor replacement?

2 thoughts on “On Reviewing, and Reviews”

  1. My copy of the recent Q&Q has gotten shoved in with the as-yet-unread New Yorkers for the month, but your mention of this article will bump it up the stack. (Yes, I read the reviews in both!)

    I do read online reviews, but I read them in a cautious sort of way because I am spoiler-phobic. If, after a couple of paragraphs, I don’t think the book will appeal, I often jump to the end, whereas I’m more likely to read a generally-bookish post through. But reviews do make a difference: I often immediately make an ILL request for a book that I’ve never heard of before, and if I like it, I follow up with a purchase.

    It does seem as though reviews about a specific book are less likely to receive a comment (public or otherwise) because, I suspect, that the readers are visiting some time after the review has been posted, which seems to suggest that there is no possibility of discourse.

    Time in Blog-Land seems to be so immediate; I hesitate to post a comment even if only a few days have passed since an article’s been published, so I’m sure someone else reading a review of something I read six months ago would think twice about adding to the “conversation”, let alone add to an empty comment field.

    It’s funny that your post, which raises the question of whether there is any real discourse on bookblogs, hasn’t gotten any comments, but it’s March: many have been absorbed in March-Break-ness, and Spring is arriving in the city, and I suppose it’s always possible that everyone is too busy reading?!


Deprecated: parse_str(): Passing null to parameter #1 ($string) of type string is deprecated in /home4/onceand4/public_html/wp-content/plugins/jetpack/class.jetpack.php on line 4218

Leave a Reply

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