<?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/"
		xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: LITA National Forum 2008: Tim Spalding: &#8220;Library 2.0 is in Danger&#8221;</title>
	<atom:link href="http://litablog.org/2008/10/lita-national-forum-2008-tim-spalding-library-20-is-in-danger/feed/" rel="self" type="application/rss+xml" />
	<link>http://litablog.org/2008/10/lita-national-forum-2008-tim-spalding-library-20-is-in-danger/</link>
	<description>Library and Information Technology Association</description>
	<lastBuildDate>Fri, 20 Jan 2012 19:19:12 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: eschnell</title>
		<link>http://litablog.org/2008/10/lita-national-forum-2008-tim-spalding-library-20-is-in-danger/comment-page-1/#comment-166422</link>
		<dc:creator>eschnell</dc:creator>
		<pubDate>Sun, 19 Oct 2008 13:10:53 +0000</pubDate>
		<guid isPermaLink="false">http://litablog.org/?p=788#comment-166422</guid>
		<description>Thanks, Tim, for taking the time to comment, correct, and clarify!! (Opps, I could have taken one more click and uncovered the list of seventy! Bad librarian.)

A reaction to your comment about the languishing catalog, 

While the human interface of library catalogs has changed since the early Seventies, the vision of what the catalog is hasn&#039;t changed. The catalog is like that old used car that libraries have so much invested in, both fiscally and emotionally, that they do not dare trade it in for a new model.  Libraries approach to incorporating Web 2.0 is like putting fancy rims and tires on a 1970 Chevy. Much like the hybrid car, even the addition of newer &#039;discovery layers&#039; is simply a transitional technology. 

The service/system/environment you created with LibraryThing stands in stark contrast. You &#039;get&#039; that LibraryThing is in the &#039;transportation&#039; business, not the car business. People are drawn to and want to participate. Meanwhile, libraries need to  &quot;RickRoll&quot; customers into &#039;playing&#039; with the catalog. 

The way libraries envision the role and architecture of the catalog needs to change or 
libraries may be left with a broken down catalog that requires replacement parts that are hard, if not impossible, to find.</description>
		<content:encoded><![CDATA[<p>Thanks, Tim, for taking the time to comment, correct, and clarify!! (Opps, I could have taken one more click and uncovered the list of seventy! Bad librarian.)</p>
<p>A reaction to your comment about the languishing catalog, </p>
<p>While the human interface of library catalogs has changed since the early Seventies, the vision of what the catalog is hasn&#8217;t changed. The catalog is like that old used car that libraries have so much invested in, both fiscally and emotionally, that they do not dare trade it in for a new model.  Libraries approach to incorporating Web 2.0 is like putting fancy rims and tires on a 1970 Chevy. Much like the hybrid car, even the addition of newer &#8216;discovery layers&#8217; is simply a transitional technology. </p>
<p>The service/system/environment you created with LibraryThing stands in stark contrast. You &#8216;get&#8217; that LibraryThing is in the &#8216;transportation&#8217; business, not the car business. People are drawn to and want to participate. Meanwhile, libraries need to  &#8220;RickRoll&#8221; customers into &#8216;playing&#8217; with the catalog. </p>
<p>The way libraries envision the role and architecture of the catalog needs to change or<br />
libraries may be left with a broken down catalog that requires replacement parts that are hard, if not impossible, to find.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

