<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: My (Our) Abusive Relationship with Google and What We Can Do About It</title>
	<atom:link href="http://www.inthelibrarywiththeleadpipe.org/2009/my-abusive-relationship-with-google/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.inthelibrarywiththeleadpipe.org/2009/my-abusive-relationship-with-google/</link>
	<description>The murder victim? Your library assumptions. Suspects? It could have been any of us.</description>
	<lastBuildDate>Wed, 10 Mar 2010 19:50:35 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Google Book Settlement Link Dump Awesomeness at pureinformation.org</title>
		<link>http://www.inthelibrarywiththeleadpipe.org/2009/my-abusive-relationship-with-google/comment-page-1/#comment-536</link>
		<dc:creator>Google Book Settlement Link Dump Awesomeness at pureinformation.org</dc:creator>
		<pubDate>Mon, 16 Feb 2009 21:26:22 +0000</pubDate>
		<guid isPermaLink="false">http://inthelibrarywiththeleadpipe.org/?p=924#comment-536</guid>
		<description>[...] In the Library with the Lead Pipe: My (Our) Abusive Relationship with Google and What We Can Do Abou... [...]</description>
		<content:encoded><![CDATA[<p>[...] In the Library with the Lead Pipe: My (Our) Abusive Relationship with Google and What We Can Do Abou&#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wednesday Links &#171; Bib-Laura-graphy</title>
		<link>http://www.inthelibrarywiththeleadpipe.org/2009/my-abusive-relationship-with-google/comment-page-1/#comment-507</link>
		<dc:creator>Wednesday Links &#171; Bib-Laura-graphy</dc:creator>
		<pubDate>Wed, 11 Feb 2009 17:11:37 +0000</pubDate>
		<guid isPermaLink="false">http://inthelibrarywiththeleadpipe.org/?p=924#comment-507</guid>
		<description>[...] always-educational In the Library with the Lead Pipe has a detailed breakdown of what librarians need to know about the Google books [...]</description>
		<content:encoded><![CDATA[<p>[...] always-educational In the Library with the Lead Pipe has a detailed breakdown of what librarians need to know about the Google books [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hilary Davis</title>
		<link>http://www.inthelibrarywiththeleadpipe.org/2009/my-abusive-relationship-with-google/comment-page-1/#comment-471</link>
		<dc:creator>Hilary Davis</dc:creator>
		<pubDate>Wed, 04 Feb 2009 22:28:09 +0000</pubDate>
		<guid isPermaLink="false">http://inthelibrarywiththeleadpipe.org/?p=924#comment-471</guid>
		<description>Emily - thanks for tackling this tough and timely topic. What I&#039;m learning from this post and following-up on the references that you point to is that there are many more questions than answers at this point.  Just this week, at my library we had a seminar on the Google books product and it generated a lot of questions and very divergent perspectives.  

&lt;br /&gt;&lt;br /&gt;
Some additional points that people raised from the discussion at my library that I&#039;m still ruminating over are (1) could this settlement could have an impact on ebook providers like ebrary and netlibrary (which I think could be bad for diversifying the marketplace); (2) Google is making more content snippets available than are currently available (which I think it a good thing); (3) Google may find this venture to not be profitable one day and shut down the service leaving libraries/info providers empty-handed (which I think would be a bad thing); (4) the future of library catalogs could drastically change in a world with Google Books serving up 7+ million books (I don&#039;t know if this is good or bad); (5) the Books Rights Registry is only proposed to be composed of industry people with no library representation (which I think is probably a bad thing); (6) it&#039;s confusing as to what would happen to books or publishers interested in participating for content published after January 5, 2009.</description>
		<content:encoded><![CDATA[<p>Emily &#8211; thanks for tackling this tough and timely topic. What I&#8217;m learning from this post and following-up on the references that you point to is that there are many more questions than answers at this point.  Just this week, at my library we had a seminar on the Google books product and it generated a lot of questions and very divergent perspectives.  </p>
<p>Some additional points that people raised from the discussion at my library that I&#8217;m still ruminating over are (1) could this settlement could have an impact on ebook providers like ebrary and netlibrary (which I think could be bad for diversifying the marketplace); (2) Google is making more content snippets available than are currently available (which I think it a good thing); (3) Google may find this venture to not be profitable one day and shut down the service leaving libraries/info providers empty-handed (which I think would be a bad thing); (4) the future of library catalogs could drastically change in a world with Google Books serving up 7+ million books (I don&#8217;t know if this is good or bad); (5) the Books Rights Registry is only proposed to be composed of industry people with no library representation (which I think is probably a bad thing); (6) it&#8217;s confusing as to what would happen to books or publishers interested in participating for content published after January 5, 2009.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Emily Ford</title>
		<link>http://www.inthelibrarywiththeleadpipe.org/2009/my-abusive-relationship-with-google/comment-page-1/#comment-470</link>
		<dc:creator>Emily Ford</dc:creator>
		<pubDate>Wed, 04 Feb 2009 20:00:34 +0000</pubDate>
		<guid isPermaLink="false">http://inthelibrarywiththeleadpipe.org/?p=924#comment-470</guid>
		<description>&lt;p&gt;@Ellie. Yes, but there are issues. What if Google thinks something is copyrighted  but a library thinks it is in public domain? Do we then get access to this book? Do we have to pay for it? What is the process via which we can challenge the registry? These answers are unclear.&lt;/p&gt;

&lt;p&gt;@Kristin. Thanks so much for pointing these things out! I find all of the technicalities very cumbersome, and am glad that you have been able to clarify some of them.&lt;/p&gt;

&lt;p&gt;I am confused about the authentication process and what really is going to happen with this. I think we need more clarification. 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 confusing this with something else? Maybe I confused this with public libraries, where remote access will not be available, or with the cross-border issue. I also found that many of Clancy&#039;s answers were nebulous about this. In effect, I don&#039;t think we or Google yet know how exactly these things are going to be implemented. The fact that you and I got different messages listening to the panel points to the fact that we need more clarification on the matter. &lt;/p&gt;

&lt;p&gt;Regarding privacy, I agree that this is a good time for us to review the agreements we already have. In terms of Google, I am afraid that any data they keep might then reflect on the library. So if someone from such and such library was looking at such and such book and a subpoena comes for that data, what do we do? Even though we have the ability to technically anonymize data, I wonder if every library will. What happens then?&lt;/p&gt;

&lt;p&gt;Privacy, then, becomes a greater issue for the individual user who logs in and buys a book as an individual consumer. I think libraries can play a key role in educating the public about this model of private data storage.&lt;/p&gt;

&lt;p&gt;And on to Harvard. The article to which I linked states that they aren&#039;t participating in the digitization of in-copyright works. I should have been more clear, so thanks for pointing this out! The reason I use Harvard as an example is that I think they have done us (libraries and librarians and the public) a great service by saying that they need more time to look at the agreement to see how they will continue to participate. Other libraries did not do this, but it is discourse we need.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>@Ellie. Yes, but there are issues. What if Google thinks something is copyrighted  but a library thinks it is in public domain? Do we then get access to this book? Do we have to pay for it? What is the process via which we can challenge the registry? These answers are unclear.</p>
<p>@Kristin. Thanks so much for pointing these things out! I find all of the technicalities very cumbersome, and am glad that you have been able to clarify some of them.</p>
<p>I am confused about the authentication process and what really is going to happen with this. I think we need more clarification. 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 confusing this with something else? Maybe I confused this with public libraries, where remote access will not be available, or with the cross-border issue. I also found that many of Clancy&#8217;s answers were nebulous about this. In effect, I don&#8217;t think we or Google yet know how exactly these things are going to be implemented. The fact that you and I got different messages listening to the panel points to the fact that we need more clarification on the matter. </p>
<p>Regarding privacy, I agree that this is a good time for us to review the agreements we already have. In terms of Google, I am afraid that any data they keep might then reflect on the library. So if someone from such and such library was looking at such and such book and a subpoena comes for that data, what do we do? Even though we have the ability to technically anonymize data, I wonder if every library will. What happens then?</p>
<p>Privacy, then, becomes a greater issue for the individual user who logs in and buys a book as an individual consumer. I think libraries can play a key role in educating the public about this model of private data storage.</p>
<p>And on to Harvard. The article to which I linked states that they aren&#8217;t participating in the digitization of in-copyright works. I should have been more clear, so thanks for pointing this out! The reason I use Harvard as an example is that I think they have done us (libraries and librarians and the public) a great service by saying that they need more time to look at the agreement to see how they will continue to participate. Other libraries did not do this, but it is discourse we need.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kristin Antelman</title>
		<link>http://www.inthelibrarywiththeleadpipe.org/2009/my-abusive-relationship-with-google/comment-page-1/#comment-469</link>
		<dc:creator>Kristin Antelman</dc:creator>
		<pubDate>Wed, 04 Feb 2009 19:04:52 +0000</pubDate>
		<guid isPermaLink="false">http://inthelibrarywiththeleadpipe.org/?p=924#comment-469</guid>
		<description>I&#039;d like to make a couple factual corrections to this post:

Google will not &quot;know&quot; what you read, copy, print, etc.  At the ALA session, Clancy said that Google intends (in fact, would have to) work with whatever authentication mechanisms libraries currently use to pass users through to content.  That may be EZproxy now, but will be something like Shibboleth in the future, where only a &quot;token&quot; is passed to the information provider saying person x is authorized to get the content.  If our systems 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&#039;s servers.  But as we talk about the privacy of use data issue, I would hope that we aren&#039;t setting ourselves up to look like hypocrites.  Do our libraries&#039; licenses for ejournals constrain what use data publishers can store?  Do they specify how quickly those logs are scrubbed, and what data the vendor is permitted to track and keep and to what purpose?  And, if the publisher refuses these terms, do we refuse to buy their content?

You say &quot;Harvard immediately pulled out of participation.&quot;  That is not true.  Darnton addressed this &quot;rumor&quot; in the NYT this week (&quot;“Contrary to many reports, Harvard has not rejected the settlement,” Mr. Darnton wrote in an e-mail message, [...] “It is studying the situation as the proposed accord makes its way through the court.” NYT 2/2/09).  Google continues to scan out-of-copyright books from Harvard, which is scope they&#039;ve had from the beginning.

You write, &quot;the settlement will not allow for a subscriber library&#039;s users to login via remote access.&quot;  This would obviously be an enormous concern to an academic library, but it is not the case.  It is true that the proposed agreement doesn&#039;t explicitly say off site uses are permitted for higher education institutions, but it *does* explicitly say they are prohibited without BRR approval for 3 of the 6 categories institutional subscribers (K-12, government, public libraries).  See p. 42 of the agreement.  See also Q 7 in the Google settlement FAQ (http://books.google.com/googlebooks/agreement/faq.html#q7): &quot;The Institutional Subscription will allow users to search, read online (including through remote access) and print books made available through this agreement.&quot;</description>
		<content:encoded><![CDATA[<p>I&#8217;d like to make a couple factual corrections to this post:</p>
<p>Google will not &#8220;know&#8221; what you read, copy, print, etc.  At the ALA session, Clancy said that Google intends (in fact, would have to) work with whatever authentication mechanisms libraries currently use to pass users through to content.  That may be EZproxy now, but will be something like Shibboleth in the future, where only a &#8220;token&#8221; is passed to the information provider saying person x is authorized to get the content.  If our systems 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&#8217;s servers.  But as we talk about the privacy of use data issue, I would hope that we aren&#8217;t setting ourselves up to look like hypocrites.  Do our libraries&#8217; licenses for ejournals constrain what use data publishers can store?  Do they specify how quickly those logs are scrubbed, and what data the vendor is permitted to track and keep and to what purpose?  And, if the publisher refuses these terms, do we refuse to buy their content?</p>
<p>You say &#8220;Harvard immediately pulled out of participation.&#8221;  That is not true.  Darnton addressed this &#8220;rumor&#8221; in the NYT this week (&#8220;“Contrary to many reports, Harvard has not rejected the settlement,” Mr. Darnton wrote in an e-mail message, [...] “It is studying the situation as the proposed accord makes its way through the court.” NYT 2/2/09).  Google continues to scan out-of-copyright books from Harvard, which is scope they&#8217;ve had from the beginning.</p>
<p>You write, &#8220;the settlement will not allow for a subscriber library&#8217;s users to login via remote access.&#8221;  This would obviously be an enormous concern to an academic library, but it is not the case.  It is true that the proposed agreement doesn&#8217;t explicitly say off site uses are permitted for higher education institutions, but it *does* explicitly say they are prohibited without BRR approval for 3 of the 6 categories institutional subscribers (K-12, government, public libraries).  See p. 42 of the agreement.  See also Q 7 in the Google settlement FAQ (<a href="http://books.google.com/googlebooks/agreement/faq.html#q7" rel="nofollow">http://books.google.com/googlebooks/agreement/faq.html#q7</a>): &#8220;The Institutional Subscription will allow users to search, read online (including through remote access) and print books made available through this agreement.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ellie</title>
		<link>http://www.inthelibrarywiththeleadpipe.org/2009/my-abusive-relationship-with-google/comment-page-1/#comment-465</link>
		<dc:creator>Ellie</dc:creator>
		<pubDate>Wed, 04 Feb 2009 16:03:01 +0000</pubDate>
		<guid isPermaLink="false">http://inthelibrarywiththeleadpipe.org/?p=924#comment-465</guid>
		<description>Thanks Emily! I hadn&#039;t bothered to read over the settlement yet and didn&#039;t know it included anything about a database subscription. I think an important distinction is that the books in this database are generally the in-copyright, not commercially available category. The concept of limiting this to a specific terminal definitely bothers me, but the fact that it doesn&#039;t seem to impact the out of copyright books makes me happy. I&#039;ve been reading Free Culture and am fascinated by the battle for &quot;fair use.&quot; I&#039;m also glad that this seems to continue to allow the snippets feature in the freely searchable Google books search, so that discovery option is not removed. I also wonder whether this will help fuel more print on demand projects with the scanned text more readily available. Lots of interesting questions!</description>
		<content:encoded><![CDATA[<p>Thanks Emily! I hadn&#8217;t bothered to read over the settlement yet and didn&#8217;t know it included anything about a database subscription. I think an important distinction is that the books in this database are generally the in-copyright, not commercially available category. The concept of limiting this to a specific terminal definitely bothers me, but the fact that it doesn&#8217;t seem to impact the out of copyright books makes me happy. I&#8217;ve been reading Free Culture and am fascinated by the battle for &#8220;fair use.&#8221; I&#8217;m also glad that this seems to continue to allow the snippets feature in the freely searchable Google books search, so that discovery option is not removed. I also wonder whether this will help fuel more print on demand projects with the scanned text more readily available. Lots of interesting questions!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
