• My (Our) Abusive Relationship with Google and What We Can Do About It

    February 4, 2009

    Thanks to Flickr user gynti_46 for use of the photo.

    Thanks to Flickr user gynti_46 for use of the photo.

    Since Octo­ber some­thing has been weigh­ing on my pro­fes­sional mind: my abu­sive rela­tion­ship with Google. I love Google, I don’t ever want to leave my Gmail, my Gchat, my Google­Docs, my web searches, my Google Reader, but right now I wish I weren’t so depen­dent on it.

    The weight to which I am refer­ring is the pro­posed Google Book Search Set­tle­ment Agreement. Google knows with whom I e-mail and chat, for what I search, what blogs I read, and on and on. With the pro­posed set­tle­ment Google will take a fur­ther step in con­trol­ling my (and libraries’) infor­ma­tion use and seek­ing behav­ior. Google will know what books I read, what pages I read, how long I read them, what pages I print, and what pas­sages I copy and paste. (If you don’t know what I’m talk­ing about you should stop read­ing imme­di­ately and read the 2-Page Super Sim­ple Sum­mary on the Google Book Search set­tle­ment agree­ment pro­duced by the ALA Office of Infor­ma­tion Tech­nol­ogy Pol­icy (OITP). Then, and only then, con­tinue here at ItLWtLP.)

    For those of you who aren’t going to go read this doc­u­ment, here’s my sim­ple recap: The Amer­i­can Asso­ci­a­tion of Pub­lish­ers (AAP) and the Authors Guild filed a class action law­suit against Google Book Search for copy­right infringe­ment. Instead of going to trial, the par­ties have agreed to set­tle out-of-court. Google has agreed to fund a right­sh­older data­base called the Book Rights Reg­istry, which will be run by the right­sh­old­ers (authors and pub­lish­ers). Google will sell books to indi­vid­ual con­sumers, but right­sh­old­ers will have finan­cial stakes in the prod­uct. Libraries will be able to sub­scribe to gain full-text access to books via the Google Book Search Project, mim­ic­k­ing the same model as many other library prod­ucts. The pro­posed set­tle­ment has far-reaching impli­ca­tions for use of dig­i­tized mate­ri­als in libraries, the role of fair use, and the future dig­i­tal mar­ket. Unfor­tu­nately, many of the agreement’s facets are anti­thet­i­cal to the mis­sion and pur­pose of libraries. In fact, some libraries, such as  Har­vard, imme­di­ately pulled out of par­tic­i­pa­tion with the Google Book Search Project.

    I won’t pro­vide you with a more in depth analy­sis of the suit in this blog post. As I men­tioned in my first sen­tence, this abu­sive rela­tion­ship has been eat­ing at my brain for many months and it’s just now begin­ning to solid­ify. What I do want to share is what I think we in the library com­mu­nity can do about the set­tle­ment. The stakes of the set­tle­ment are enor­mous, and nei­ther the righthold­ers or Google rep­re­sent libraries in this process. But we, librar­i­ans and the library com­mu­nity at large, are an ornery bunch. Aren’t we the com­mu­nity that took to court over the PATRIOT Act? Aren’t we the com­mu­nity that insti­gated a pub­lic out­cry when Michael Moore’s pub­lisher pulled Stu­pid White Men for being too crit­i­cal of for­mer Pres­i­dent Bush? Aren’t we “rad­i­cal” and “militant?”

    Because I don’t want libraries, infor­ma­tion advo­cates, patrons, or any­one else to be trapped in an abu­sive rela­tion­ship with Google I would like to offer the fol­low­ing sug­ges­tions for what indi­vid­u­als and the pro­fes­sional com­mu­nity can do to pro­tect and sal­vage what remains of our rela­tion­ship with “the big G.” (And maybe even make this Google Book Set­tle­ment Agree­ment a bit more reasonable.)

    Indi­vid­u­als

    Edu­cate yourself.

    Knowl­edge is empow­er­ment. Read through blog posts, doc­u­ments, and news arti­cles about the pro­posed set­tle­ment agree­ment. The ALA Wash­ing­ton Office is track­ing most every­thing that’s out there and has made a nice lit­tle por­tal web site for you to use. Par­tic­u­larly use­ful is also the Guide to the Per­plexed: Libraries and the Google Library Project Set­tle­ment. This longer doc­u­ment pro­vides a broader view than the 2-page doc­u­ment. You might even con­sider check­ing out what Google has to say about the “ground­break­ing agree­ment.”

    Because the set­tle­ment is so intrin­si­cally tied to copy­right law and fair use, this is an ideal time to refresh your­self on the basics. Re-read Kenny Crews’s Copy­right Law for Librar­i­ans and Edu­ca­tors and Car­rie Russell’s Com­plete Copy­right. Sub­scribe to blogs that deal with copy­right such as librarycopy​right​.net or Karen Coyle’s blog.

    Rumi­nate.

    Ask your­self and think about the tough ques­tions. Dur­ing the Google Book Set­tle­ment: What’s in it for Libraries? panel at ALA Mid­win­ter, Karen Coyle posed the fol­low­ing ques­tions: Does the prod­uct serve my users? What will the col­lec­tion be? What is the qual­ity of the prod­uct? Pan­elist Laura Quil­ter pushed the panel par­tic­i­pants and audi­ence to con­sider the pri­vacy issues pre­sented by the pro­posed model for access­ing dig­i­tal mate­ri­als through Google Books. As librar­i­ans we have a respon­si­bil­ity to pro­tect our users. Mold and define your per­sonal and pro­fes­sional val­ues for pri­vacy. This will be incred­i­bly use­ful if you are put in a place to con­sider pur­chas­ing and imple­ment­ing this sub­scrip­tion prod­uct in your library.

    Be an advo­cate in your community.

    Let’s face it. There are so many issues to fol­low in our pro­fes­sion, that chances are many of your col­leagues might not know any­thing about this pro­posed set­tle­ment agree­ment. Talk with your col­leagues and share with them what you have learned. Push your admin­is­tra­tors to find out if any pre-emptive dis­cus­sions regard­ing this prod­uct have occurred. What is the insti­tu­tional stance on the set­tle­ment agree­ment and Google Books in gen­eral? By ask­ing the hard ques­tions of our super­vi­sors and admin­is­tra­tors, we are often able to gen­er­ate insti­tu­tional discourse.

    The Com­mu­nity

    Ask and discuss.

    ALA has very bright and informed peo­ple work­ing to under­stand the Google Book Set­tle­ment Agree­ment. Librar­i­ans who spe­cial­ize in infor­ma­tion pol­icy, entire offices and com­mit­tees that deal with leg­is­la­tion and lob­by­ing for ALA inter­ests. But this 300+ page legal doc­u­ment that is the agree­ment is con­fus­ing and still not fully under­stood by the library com­mu­nity. At the afore­men­tioned Mid­win­ter panel dis­cus­sion, many things came to light that we (or at least I) did not pre­vi­ously know about the set­tle­ment. For exam­ple, the set­tle­ment will not allow for a sub­scriber library’s users to login via remote access and access their library’s sub­scrip­tion to the Google Books data­base. Users who are com­mu­nity mem­bers of a sub­scrib­ing insti­tu­tion will only be able to access the resource “on cam­pus.” Another fine exam­ple is how Google will serve pub­lic libraries with this prod­uct. Google will allow pub­lic libraries one access sta­tion to the prod­uct. Only one.

    We need more fora in which to engage to find out exactly what the set­tle­ment agree­ment means to us and our users. Pro­fes­sional orga­ni­za­tions, ALA, SLA, PLA, ARL and oth­ers should con­sider host­ing more web-hosted sem­i­nars for their mem­bers on the sub­ject. More­over, host­ing other kinds of dis­cus­sion fora to ask ques­tions and com­mis­er­ate within the library com­mu­nity such as BBS or wikis or even blogs will be help­ful to those of use who strug­gle to under­stand the issues inher­ent with the settlement.

    It is also of import to note that dur­ing the panel at Mid­win­ter Dan Clancy, Engi­neer­ing Direc­tor for the Google Book Search Project, said he would like to be able to be avail­able to the library com­mu­nity for more dis­cus­sion. State libraries, con­sor­tia, or other large groups should con­sider con­tact­ing Dan and sched­ule a tele­con about concerns.

    Edu­cate Google.

    I would like to give Google the ben­e­fit of the doubt. How­ever, the fact remains that Google is a busi­ness and will not imple­ment pol­icy or pro­ce­dure based upon it being “the right things to do.” Rather, Google will make pol­icy, and change pro­ce­dure, as it is ben­e­fi­cial to busi­ness and the deep Google pock­et­book. That being said, I think Google would attempt to take more respon­si­bil­ity for “doing the right thing” if the com­pany were to real­ize that the pro­posed set­tle­ment model is not one upon which libraries will will­ingly spend their money. Just because Google will have a monop­oly on the dig­i­tized books, does not mean that we should lower our stan­dards for offer­ing resources to patrons that are easy to use and eth­i­cally imple­mented. We, as a com­mu­nity, need to share with Google the eth­i­cal prin­ci­ples and best prac­tices that we have worked so hard to develop — of par­tic­u­lar rel­e­vance, the Prin­ci­ples for Dig­i­tal Con­tent, and the Prin­ci­ples for a Net­worked World.

    Develop posi­tion state­ments, draft and pass res­o­lu­tions, or take other gov­ern­men­tal action.

    A uni­fied voice of librar­i­ans can be a pow­er­ful thing. More­over, if pro­fes­sional orga­ni­za­tions such as ALA, whose mem­ber­ship is pur­ported to be 65,000 (accord­ing to the ALA Annual Report), use their posi­tion as the good stew­ards of knowl­edge and infor­ma­tion, we have the abil­ity to put up a good fight that might yield some pos­i­tive results. Cur­rently the Wash­ing­ton Office is work­ing to gather ALA mem­ber­ship input so that it can issue a posi­tion state­ment or take other action on the set­tle­ment. (I don’t even know the proper chan­nels to let ALA where I stand on this issues. To this end, ALA should con­sider cre­at­ing a sys­tem that enables solic­it­ing and gain­ing mem­ber­ship com­ment when warranted.)

    ALA Coun­cil should also con­sider pass­ing a res­o­lu­tion regard­ing the Google Book Search Set­tle­ment Agree­ment. It is not out of the ques­tion that this kind of polit­i­cal activ­ity will help the orga­ni­za­tion to retain its integrity and ethics regard­ing pri­vacy, infor­ma­tion pol­icy, and what best serves libraries and patrons.

    ALA and other library orga­ni­za­tions should con­sider future legal action. It seems to me that libraries would have a good case to bring forth their own class action law­suit. This might be a last case resort, but I do not think we should not sit idly by if a large market-driven prod­uct were to threaten the library community’s abil­ity to best serve the public.

    Cre­ate sup­port mate­ri­als and doc­u­ments for libraries to use.

    Shortly after the court “okays” the Google Books Set­tle­ment agree­ment, libraries will face a “pur­chase or not to pur­chase” ques­tion for the Google Books sub­scrip­tion prod­uct. Nav­i­gat­ing the ins and outs of the legalese in the set­tle­ment will be daunt­ing for any library sys­tem, con­sor­tium, or lone library that chooses to buy the prod­uct. Hav­ing FAQs handy or even an ALA Toolkit on best imple­men­ta­tion prac­tices for Google Books would be a great service.

    It doesn’t have to be a wait­ing game.

    If we work now to under­stand what we can about the pro­posed set­tle­ment, if we start to eval­u­ate the effect pur­chas­ing this prod­uct will have on our libraries and patrons, if we cre­ate a uni­fied voice and fos­ter dis­course, then we will bet­ter be able to keep fires under con­trol and per­haps keep our brains in our heads. Google is a pow­er­ful com­pany, but pow­er­ful, too, is the voice of libraries and librar­i­ans. I firmly believe that if we con­tinue to put our efforts toward under­stand­ing every­thing encom­passed by the Google Book set­tle­ment issue, then we will bet­ter be able to serve our com­mu­ni­ties, and per­haps inform pos­i­tive changes that will let us sit in bet­ter peace with our friend and enemy. This is my call to you, col­leagues, to engage, think, debate, and defend library val­ues. Take con­trol and save your­self from this abu­sive rela­tion­ship. Google can be a ref­er­ence librarian’s best friend, but right now, with the pro­posed set­tle­ment, it is look­ing as if we are sub­ject to con­tin­ued abuse.


    Thanks to Laura Quil­ter for her edi­to­r­ial com­ments; Todd Han­non for a close read; and Brett Bon­field, Ellie Col­lier and Hilary Davis from ItLWtLP for read­ing this post and offer­ing feed­back.

    You might also be inter­ested in:

6 Comments

  • Ellie says:

    Thanks Emily! I hadn’t both­ered to read over the set­tle­ment yet and didn’t know it included any­thing about a data­base sub­scrip­tion. I think an impor­tant dis­tinc­tion is that the books in this data­base are gen­er­ally the in-copyright, not com­mer­cially avail­able cat­e­gory. The con­cept of lim­it­ing this to a spe­cific ter­mi­nal def­i­nitely both­ers me, but the fact that it doesn’t seem to impact the out of copy­right books makes me happy. I’ve been read­ing Free Cul­ture and am fas­ci­nated by the bat­tle for “fair use.” I’m also glad that this seems to con­tinue to allow the snip­pets fea­ture in the freely search­able Google books search, so that dis­cov­ery option is not removed. I also won­der whether this will help fuel more print on demand projects with the scanned text more read­ily avail­able. Lots of inter­est­ing questions!

  • Kristin Antelman says:

    I’d like to make a cou­ple fac­tual cor­rec­tions to this post:

    Google will not “know” what you read, copy, print, etc. At the ALA ses­sion, Clancy said that Google intends (in fact, would have to) work with what­ever authen­ti­ca­tion mech­a­nisms libraries cur­rently use to pass users through to con­tent. That may be EZproxy now, but will be some­thing like Shib­bo­leth in the future, where only a “token” is passed to the infor­ma­tion provider say­ing per­son x is autho­rized to get the con­tent. If our sys­tems pass an IP address, and we are not happy with that, there are steps we can take to, in essence, anonymize that before the request hits Google’s servers. But as we talk about the pri­vacy of use data issue, I would hope that we aren’t set­ting our­selves up to look like hyp­ocrites. Do our libraries’ licenses for ejour­nals con­strain what use data pub­lish­ers can store? Do they spec­ify how quickly those logs are scrubbed, and what data the ven­dor is per­mit­ted to track and keep and to what pur­pose? And, if the pub­lisher refuses these terms, do we refuse to buy their content?

    You say “Har­vard imme­di­ately pulled out of par­tic­i­pa­tion.” That is not true. Darn­ton addressed this “rumor” in the NYT this week (““Con­trary to many reports, Har­vard has not rejected the set­tle­ment,” Mr. Darn­ton wrote in an e-mail mes­sage, […] “It is study­ing the sit­u­a­tion as the pro­posed accord makes its way through the court.” NYT 2÷2÷09). Google con­tin­ues to scan out-of-copyright books from Har­vard, which is scope they’ve had from the beginning.

    You write, “the set­tle­ment will not allow for a sub­scriber library’s users to login via remote access.” This would obvi­ously be an enor­mous con­cern to an aca­d­e­mic library, but it is not the case. It is true that the pro­posed agree­ment doesn’t explic­itly say off site uses are per­mit­ted for higher edu­ca­tion insti­tu­tions, but it *does* explic­itly say they are pro­hib­ited with­out BRR approval for 3 of the 6 cat­e­gories insti­tu­tional sub­scribers (K-12, gov­ern­ment, pub­lic libraries). See p. 42 of the agree­ment. See also Q 7 in the Google set­tle­ment FAQ (http://​books​.google​.com/​g​o​o​g​l​e​b​o​o​k​s​/​a​g​r​e​e​m​e​n​t​/​f​a​q​.​h​t​m​l​#q7): “The Insti­tu­tional Sub­scrip­tion will allow users to search, read online (includ­ing through remote access) and print books made avail­able through this agreement.”

  • Emily Ford says:

    @Ellie. Yes, but there are issues. What if Google thinks some­thing is copy­righted but a library thinks it is in pub­lic domain? Do we then get access to this book? Do we have to pay for it? What is the process via which we can chal­lenge the reg­istry? These answers are unclear.

    @Kristin. Thanks so much for point­ing these things out! I find all of the tech­ni­cal­i­ties very cum­ber­some, and am glad that you have been able to clar­ify some of them.

    I am con­fused about the authen­ti­ca­tion process and what really is going to hap­pen with this. I think we need more clar­i­fi­ca­tion. Did Clancy not point to the fact that they would have to look into remote access and try their best to not allow it? Am I con­fus­ing this with some­thing else? Maybe I con­fused this with pub­lic libraries, where remote access will not be avail­able, or with the cross-border issue. I also found that many of Clancy’s answers were neb­u­lous about this. In effect, I don’t think we or Google yet know how exactly these things are going to be imple­mented. The fact that you and I got dif­fer­ent mes­sages lis­ten­ing to the panel points to the fact that we need more clar­i­fi­ca­tion on the matter.

    Regard­ing pri­vacy, I agree that this is a good time for us to review the agree­ments we already have. In terms of Google, I am afraid that any data they keep might then reflect on the library. So if some­one from such and such library was look­ing at such and such book and a sub­poena comes for that data, what do we do? Even though we have the abil­ity to tech­ni­cally anonymize data, I won­der if every library will. What hap­pens then?

    Pri­vacy, then, becomes a greater issue for the indi­vid­ual user who logs in and buys a book as an indi­vid­ual con­sumer. I think libraries can play a key role in edu­cat­ing the pub­lic about this model of pri­vate data storage.

    And on to Har­vard. The arti­cle to which I linked states that they aren’t par­tic­i­pat­ing in the dig­i­ti­za­tion of in-copyright works. I should have been more clear, so thanks for point­ing this out! The rea­son I use Har­vard as an exam­ple is that I think they have done us (libraries and librar­i­ans and the pub­lic) a great ser­vice by say­ing that they need more time to look at the agree­ment to see how they will con­tinue to par­tic­i­pate. Other libraries did not do this, but it is dis­course we need.

  • Hilary Davis says:

    Emily — thanks for tack­ling this tough and timely topic. What I’m learn­ing from this post and following-up on the ref­er­ences that you point to is that there are many more ques­tions than answers at this point. Just this week, at my library we had a sem­i­nar on the Google books prod­uct and it gen­er­ated a lot of ques­tions and very diver­gent perspectives.

    Some addi­tional points that peo­ple raised from the dis­cus­sion at my library that I’m still rumi­nat­ing over are (1) could this set­tle­ment could have an impact on ebook providers like ebrary and netli­brary (which I think could be bad for diver­si­fy­ing the mar­ket­place); (2) Google is mak­ing more con­tent snip­pets avail­able than are cur­rently avail­able (which I think it a good thing); (3) Google may find this ven­ture to not be prof­itable one day and shut down the ser­vice leav­ing libraries/info providers empty-handed (which I think would be a bad thing); (4) the future of library cat­a­logs could dras­ti­cally change in a world with Google Books serv­ing up 7+ mil­lion books (I don’t know if this is good or bad); (5) the Books Rights Reg­istry is only pro­posed to be com­posed of indus­try peo­ple with no library rep­re­sen­ta­tion (which I think is prob­a­bly a bad thing); (6) it’s con­fus­ing as to what would hap­pen to books or pub­lish­ers inter­ested in par­tic­i­pat­ing for con­tent pub­lished after Jan­u­ary 5, 2009.

  • […] always-educational In the Library with the Lead Pipe has a detailed break­down of what librar­i­ans need to know about the Google books […]

  • […] In the Library with the Lead Pipe: My (Our) Abu­sive Rela­tion­ship with Google and What We Can Do Abou… […]

Subscribe to comments for this post:

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>
Powered by WordPress | Original Theme by mg12 Edited by Derik. | Valid XHTML 1.1 and CSS 3