Unsettling books

I’m a born researcher. Studying stuff is a lot of what I do, whether I’m looking out the window of an airplaine, asking a question at a meeting, browsing through the Web and correspondence, or digging through books and journals in libraries.

Most of my library work, however, isn’t in library buildings. I work on my own screen. And there, much of what I’ve been studying lately is in Google scans of books.

I appreciate that Google has done Google Books. I also find the Google Books searching and reading process difficult in much the same way that looking at microfiche is difficult. The difference is that microfiche was in its time the best that could be done, while Google Books is great technology crippled by necessary compromise.

Much of that compromise — still ongoing — is around protecting both libraries and copyright holders. Contention around that topic has been large and complicated. A couple weeks back I hung out at Alternative Approaches to Open Digital Libraries in the Shadow of the Google Book Search Settlement: An Open Workshop at Harvard Law School, and left it better informed and less settled than ever.

In the Huffington Post, Pamela Samuelson, one of the world’s top copyright authorities, has a piece titled The Audacity of the Google Book Search Settlement, that begins,

  Sorry, Kindle. The Google Book Search settlement will be, if approved, the most significant book industry development in the modern era. Exploiting an opportunity made possible by lawsuits brought by a small number of plaintiffs on one narrow issue, Google has negotiated a settlement agreement designed to give it a compulsory license to all books in copyright throughout the world forever. This settlement will transform the future of the book industry and of public access to the cultural heritage of mankind embodied in books. How audacious is that?

She adds,

  Under the settlement, the Authors Guild and AAP are tasked with creating a new collecting society, the Book Rights Registry, which is supposed to find class members, sign them up, and pay them from a revenue stream that Google intends to generate from its commercialization of these books…
  Google will pay to the Registry 63 percent of the revenues it receives from its commercialization efforts of out-of-print books. After deducing its expenses, the Registry will pay royalties to those who have registered with it. Yet, the agreement also authorizes the Registry to pay out unclaimed funds from orphan and other unregistered works to registered owners, even though they are neither the authors nor the publishers of potentially millions of books.

It gets far more icky and complicated than that. Pamela continues,

  However, much larger questions call into question whether the settlement should be approved. One is whether the Authors Guild and AAP fairly represented the interests of all authors and publishers of in-copyright books during the negotiations that led up to the settlement agreement. A second is whether going forward, they and the newly created Registry to which they will give birth will fairly represent the interests of those on whose behalf the Registry will be receiving revenues from Google. As well-intentioned as they may be, the Authors Guild and AAP have negotiated an agreement that serves the interests of the core members of their organizational constituencies, not the thousands of times larger and more diverse class of authors and publishers of books from all over the world.

In What the Google Books Settlement Agreement Says About Privacy, Eric Hellman writes,

  Google, as presently constituted, has every reason to be concerned about user privacy and guard it vigilantly; its business would be severely compromised by any perception that it intrudes on the privacy of its users. As Larry Lessig pointed out at the Berkman workshop, that doesn’t mean that the Google of the future will behave similarly. Privacy concerns should be addressed; the main question has been how and where to address them. My reading of the settlement agreement is that it may be possible to address these concerns through the agreement’s Security Standard review mechanism, through oversight of the Registry, and through state and federal laws governing library patron privacy.

There’s a story this morning on NPR about how Google is building “the prospect of a virtual super-library”. Privacy is the angle on that one too. It’s also been the angle of the EFF for a long time. They’re looking for legally binding privacy guarantees. Google thinks a copyright conflict agreement would be a “wierd” place to put those guarantees.

It is a fortuitous but odd conflation. As Todd Carpenter tweets, “I don’t dismiss privacy concerns (have disabled WhysperSync on my #kindle for privacy) There are just bigger issues at stake.” Todd runs NISO, a publishing standards organization (he is also, by small-world coincidence in this thread — since, oddly, we’ve hardly talked about it, at least so far — my son-in-law). He also blogs here.

Here’s the larger issue for me: Google is a monopoly. One example. I’m looking right now at an AR&D case study (a .pdf I can’t find on the Web at the moment) of Jerry Damson Automotive Group, which the report says is the largest automobile dealer in Alabama. Here’s an excerpt:

  So where is the Damson group’s focus, if not on local media?
  “Every minute of every day is spent thinking about the consequences of our decisions as it relates to Google.” This remarkable statement is one that more advertisers will be making as they, too, grow in their un-derstanding of the Web and how advertising works in a hyperconnected universe. Boles is far ahead of most, but others will not be far behind, for people like him are paving the way for a future generation of strategies and tactics that enable commerce. “We begin each chunk (morning, mid-day, afternoon and evening) of the day with Google Analytics.”

Substitute libraries for “local media”, and you get a sense of the impact here .

Here at Harvard we have Hollis, one of the world’s largest searchable library catalogs. Maybe the largest, I dunno. But it’s a big one, and it matters. When I search through the Hollis catalog, which I do nearly every day through a search thing in my browser toolbar, many of the results are accompanied by a book cover graphic and a link that reads, “Discover more in Google Books”. That pops me out of Hollis and into Google Books itself. In other searches (through the new catalog, which is fancier), I get no mention of Google Books, but when I click on the picture of a book cover, Google Books is where I go. It’s in a different window, but still I get the impression that Google Books is part of Hollis. And that creeps me out a bit, handy as it is in some ways.

Siva Vaidhyanathan is writing a book called The Googlization of Everything: How one companyh is disrupting culture, commerce and community — and why we should worry. He spoke at the workshop as well, and has lots of deep and good things to say.

Lessig says this settlement moves books down the path of documentary films: access encumbered by a bunch of agreements, without a guarantee of future access. It is “worse that a digital bookstore.” It brings us to “an excessive permission culture” produced by “a structure of oligopolies”. A “tendency to access” but not of free access. He suggests that we are turning our culture over to tigers when they still look like kittens.

There is not an easy answer. Or set of answers. So I’ll stand right now on the questions raised at the end of this Seth Finkelstein essay in The Guardian:

  Amid all the reactions, an overall lesson should be how little can be determined by legalism, and how much remains unsettled as new technology causes shifts in markets and power. There’s some value in enemy-of-my-enemy opposition, where the interests of an advertising near-monopoly are a counterweight to a content cartel. But battles between behemoth businesses should not be mistaken for friendship to libraries, authors or public interest.


6 responses to “Unsettling books”

  1. There’s another huge question here you don’t raise is that the settlement anoints Google as a not-quite-exclusive party that can act in this manner. The Author’s Guild (of which I am a member) and other parties to the suit will have a specific agreement with Google, but any other company or non-profit or educational institution or government that wants to offer books on identical terms with identical indemnification, and identical court-stamped authority will have to start from scratch.

    What makes much more sense to me as an author is that the scanned books themselves in a commonly agreed-on format are placed into a common trust controlled by a consortium of authors, publishers, libraries, and academic groups that then provides wholesale licenses to companies like Google which are then allowed to add secret sauce.

    It makes no sense to me at this technological juncture to give Google the keys to the kingdom in a way that raises the bar for other companies to compete unless your goal is preserving artificially high prices or restricting access.

  2. Good points, Glenn. Thanks for bringing them up.

    There are so many planes on this 4-D polyhedron. Wish I could cover them all.

  3. There is absolutely NO impulse to do this other than from GOOGLE. No consortium of writers or publishers has yet said, Let’s put it all in one place. And even if there had been such a consortium, I doubt very much they’d say, “Let’s just give it all to Google!”

    There is NO reason to rush into this. And there is a rush.

    This is based on the false understanding of what “eBooks” are and what “digital books” actually need to be. Google understand this, because Google thinks far ahead. By the time everyone wakes up to the deeper implications of this, it will be far too late.

    http://ebooktest.blogspot.com/2009/08/reject-google-book-search-settlement.html

    http://ebooktest.blogspot.com/2009/07/dumb-ebooks-must-die-smart-ebooks-must.html

  4. […] Thanks to Stefan Czerniawski for pointing me to this excellent piece by Doc Searls on the Google […]

Leave a Reply

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