<?xml version="1.0" encoding="iso-8859-1"?><!-- generator="b2evolution/2.4.2" -->
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:admin="http://webns.net/mvcb/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/">
	<channel>
		<title>shimenawa - Latest comments on Google Books: A Reprise with Clarity</title>
		<link>http://blogs.lib.berkeley.edu/shimenawa.php?disp=comments</link>
		<description></description>
		<language>en-US</language>
		<docs>http://backend.userland.com/rss</docs>
		<admin:generatorAgent rdf:resource="http://b2evolution.net/?v=2.4.2"/>
		<ttl>60</ttl>
				<item>
			<title>In response to: Google Books: A Reprise with Clarity</title>
			<pubDate>Fri, 23 Mar 2007 18:40:18 +0000</pubDate>
			<dc:creator>John Mignault [Visitor]</dc:creator>
			<guid isPermaLink="false">c351@http://blogs.lib.berkeley.edu/</guid>
			<description>&lt;i&gt;How much better we would be were we the ones to design, push and popularize these features the public seems to clamor for.&lt;/i&gt;&lt;br /&gt;
&lt;br /&gt;
I am not entirely sure we would ever be in this position. One of the defining memes of today's technologists is 'disintermediation.' Accompanying that concept is the belief that the problems that necessitate many professions in the first place i.e. librarians as information intermediaries) could be solved if only we were to apply the right mix of technologies to them.  To this point of view, technology sufficiently changes everything, and is enough of an end in itself, that pretty much any profession (save technologists, of course) is eligible for disintermediation, i.e., elimination. When all you have is a hammer, everything looks like a nail. Given this, it is likely that the tech-leaning side of librarianship will continually imitate rather than innovate, hoping that if we just adopt the right set of tools, that somehow we will be spared oblivion. I anticipate the breathless demands that your library sign up for Twitter 'right now,' because 'that's where your users are', or rather, where we'd &lt;i&gt;like them to be&lt;/i&gt; - we look less backward that way.</description>
			<content:encoded><![CDATA[<i>How much better we would be were we the ones to design, push and popularize these features the public seems to clamor for.</i><br />
<br />
I am not entirely sure we would ever be in this position. One of the defining memes of today's technologists is 'disintermediation.' Accompanying that concept is the belief that the problems that necessitate many professions in the first place i.e. librarians as information intermediaries) could be solved if only we were to apply the right mix of technologies to them.  To this point of view, technology sufficiently changes everything, and is enough of an end in itself, that pretty much any profession (save technologists, of course) is eligible for disintermediation, i.e., elimination. When all you have is a hammer, everything looks like a nail. Given this, it is likely that the tech-leaning side of librarianship will continually imitate rather than innovate, hoping that if we just adopt the right set of tools, that somehow we will be spared oblivion. I anticipate the breathless demands that your library sign up for Twitter 'right now,' because 'that's where your users are', or rather, where we'd <i>like them to be</i> - we look less backward that way.]]></content:encoded>
			<link>http://blogs.lib.berkeley.edu/shimenawa.php/2007/03/09/google_books_a_reprise_with_clarity#c351</link>
		</item>
				<item>
			<title>In response to: Google Books: A Reprise with Clarity</title>
			<pubDate>Fri, 23 Mar 2007 18:37:24 +0000</pubDate>
			<dc:creator>John Mignault [Visitor]</dc:creator>
			<guid isPermaLink="false">c350@http://blogs.lib.berkeley.edu/</guid>
			<description>&gt; How much better we would be were we the ones to design, push and popularize these features the public seems to clamor for.&lt;br /&gt;
&lt;br /&gt;
I am not entirely sure we would ever be in this position. One of the defining memes of today's technologists is 'disintermediation.' Accompanying that concept is the belief that the problems that necessitate many professions in the first place i.e. librarians as information intermediaries) could be solved if only we were to apply the right mix of technologies to them.  To this point of view, technology sufficiently changes everything, and is enough of an end in itself, that pretty much any profession (save technologists, of course) is eligible for disintermediation, i.e., elimination. When all you have is a hammer, everything looks like a nail. Given this, it is likely that the tech-leaning side of librarianship will continually imitate rather than innovate, hoping that if we just adopt the right set of tools, that somehow we will be spared oblivion. I anticipate the breathless demands that your library sign up for Twitter 'right now,' because 'that's where your users are', or rather, where we'd &lt;i&gt;like them to be&lt;/i&gt; - we look less backward that way.</description>
			<content:encoded><![CDATA[> How much better we would be were we the ones to design, push and popularize these features the public seems to clamor for.<br />
<br />
I am not entirely sure we would ever be in this position. One of the defining memes of today's technologists is 'disintermediation.' Accompanying that concept is the belief that the problems that necessitate many professions in the first place i.e. librarians as information intermediaries) could be solved if only we were to apply the right mix of technologies to them.  To this point of view, technology sufficiently changes everything, and is enough of an end in itself, that pretty much any profession (save technologists, of course) is eligible for disintermediation, i.e., elimination. When all you have is a hammer, everything looks like a nail. Given this, it is likely that the tech-leaning side of librarianship will continually imitate rather than innovate, hoping that if we just adopt the right set of tools, that somehow we will be spared oblivion. I anticipate the breathless demands that your library sign up for Twitter 'right now,' because 'that's where your users are', or rather, where we'd <i>like them to be</i> - we look less backward that way.]]></content:encoded>
			<link>http://blogs.lib.berkeley.edu/shimenawa.php/2007/03/09/google_books_a_reprise_with_clarity#c350</link>
		</item>
				<item>
			<title>In response to: Google Books: A Reprise with Clarity</title>
			<pubDate>Fri, 23 Mar 2007 11:40:53 +0000</pubDate>
			<dc:creator>leo waaijers [Visitor]</dc:creator>
			<guid isPermaLink="false">c349@http://blogs.lib.berkeley.edu/</guid>
			<description>What Google offers to libraries is little short of perfect.&lt;br /&gt;
They scan your paper stuff and offer the metadata (including snippets of text) for free on the internet. Where-ever possible they include the full text for free reading and reuse by teachers, researchers and the general public. Not for commercial re-use. So what?&lt;br /&gt;
But they store the scans in their own servers and do not allow storage in the institutional repositories. This of course causes suspense. It would help if Google were prepared to escrow the scans to the libraries. Just in case, you know.  &lt;br /&gt;
</description>
			<content:encoded><![CDATA[What Google offers to libraries is little short of perfect.<br />
They scan your paper stuff and offer the metadata (including snippets of text) for free on the internet. Where-ever possible they include the full text for free reading and reuse by teachers, researchers and the general public. Not for commercial re-use. So what?<br />
But they store the scans in their own servers and do not allow storage in the institutional repositories. This of course causes suspense. It would help if Google were prepared to escrow the scans to the libraries. Just in case, you know.  <br />
]]></content:encoded>
			<link>http://blogs.lib.berkeley.edu/shimenawa.php/2007/03/09/google_books_a_reprise_with_clarity#c349</link>
		</item>
				<item>
			<title>In response to: Google Books: A Reprise with Clarity</title>
			<pubDate>Fri, 16 Mar 2007 19:38:29 +0000</pubDate>
			<dc:creator>jennifer [Visitor]</dc:creator>
			<guid isPermaLink="false">c345@http://blogs.lib.berkeley.edu/</guid>
			<description>Great clarification - but I totally understood the tenor and tone of the original piece. This point has been stated over and over again in my studies for emergent technologies and the library profession/service's lack of timely response.  Think of all we could be doing/could have done if we simply could embrace the positive aspects with a healthy appreciation for the risks. Refusal to change/enhance our practice only emphasizes the stereotype our collective society has of libraries and librarians. How much better we would be were we the ones to design, push and popularize these features the public seems to clamor for.&lt;br /&gt;
Thanks for sharing your thoughts.&lt;br /&gt;
j.</description>
			<content:encoded><![CDATA[Great clarification - but I totally understood the tenor and tone of the original piece. This point has been stated over and over again in my studies for emergent technologies and the library profession/service's lack of timely response.  Think of all we could be doing/could have done if we simply could embrace the positive aspects with a healthy appreciation for the risks. Refusal to change/enhance our practice only emphasizes the stereotype our collective society has of libraries and librarians. How much better we would be were we the ones to design, push and popularize these features the public seems to clamor for.<br />
Thanks for sharing your thoughts.<br />
j.]]></content:encoded>
			<link>http://blogs.lib.berkeley.edu/shimenawa.php/2007/03/09/google_books_a_reprise_with_clarity#c345</link>
		</item>
				<item>
			<title>In response to: Google Books: A Reprise with Clarity</title>
			<pubDate>Tue, 13 Mar 2007 03:05:48 +0000</pubDate>
			<dc:creator>Outliar [Visitor]</dc:creator>
			<guid isPermaLink="false">c343@http://blogs.lib.berkeley.edu/</guid>
			<description>Interesting &quot;clarification.&quot;  When I read your &quot;poem&quot; the other day, I thought, &quot;Ooh, must be frustrating to be the piper for cooperative digitization in the current environment.&quot;  Not sure how many books DLF thinks it's had a hand in digitizing, but &quot;not many&quot; is probably a good guess, and the prospects going forward seem to be getting worse rather than better.  With so many DLF libraries looking to digitization partners with drive and resources, it could be hard to grab attention-- not to mention dues.  The hum of real work-- like in those steel mills you used to study-- can distract people from the endless preparation to do something.  Anyway, thanks for clarifying that Book Search is a good thing (&quot;in its broadest conception&quot;)--some folks missed that point in the earlier post.    </description>
			<content:encoded><![CDATA[Interesting "clarification."  When I read your "poem" the other day, I thought, "Ooh, must be frustrating to be the piper for cooperative digitization in the current environment."  Not sure how many books DLF thinks it's had a hand in digitizing, but "not many" is probably a good guess, and the prospects going forward seem to be getting worse rather than better.  With so many DLF libraries looking to digitization partners with drive and resources, it could be hard to grab attention-- not to mention dues.  The hum of real work-- like in those steel mills you used to study-- can distract people from the endless preparation to do something.  Anyway, thanks for clarifying that Book Search is a good thing ("in its broadest conception")--some folks missed that point in the earlier post.    ]]></content:encoded>
			<link>http://blogs.lib.berkeley.edu/shimenawa.php/2007/03/09/google_books_a_reprise_with_clarity#c343</link>
		</item>
			</channel>
</rss>
