<?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 The Show Room Library</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: The Show Room Library</title>
			<pubDate>Fri, 26 Sep 2008 17:18:16 +0000</pubDate>
			<dc:creator>Jodi Schneider [Visitor]</dc:creator>
			<guid isPermaLink="false">c75050@http://blogs.lib.berkeley.edu/</guid>
			<description>Was popping in on this again, and thought I'd connect this up with&lt;br /&gt;
http://worldcat.org/blogs/archives/2008/09/worldcat-for-iphone.htm&lt;br /&gt;
&lt;br /&gt;
Karen Coyle's been asking for &quot;search in the stacks&quot; capability for a while. We're slowly getting there.</description>
			<content:encoded><![CDATA[Was popping in on this again, and thought I'd connect this up with<br />
http://worldcat.org/blogs/archives/2008/09/worldcat-for-iphone.htm<br />
<br />
Karen Coyle's been asking for "search in the stacks" capability for a while. We're slowly getting there.]]></content:encoded>
			<link>http://blogs.lib.berkeley.edu/shimenawa.php/2008/07/14/the_show_room_library#c75050</link>
		</item>
				<item>
			<title>In response to: The Show Room Library</title>
			<pubDate>Wed, 13 Aug 2008 21:42:14 +0000</pubDate>
			<dc:creator>Adam Corson-Finnerty [Visitor]</dc:creator>
			<guid isPermaLink="false">c57819@http://blogs.lib.berkeley.edu/</guid>
			<description>I am not so sure that libraries should be poised to jump on every bandwagon that comes along.  For one thing, we don't have the money to cook up new apps every time someone comes along with a commercial gadget or widget that is both &quot;cool&quot; and &quot;hot.&quot;  &lt;br /&gt;
&lt;br /&gt;
Libraries can and probably should wait to see if an innovative device or app establishes itself.  &lt;br /&gt;
&lt;br /&gt;
Your underlying assumption seems to be that if libraries aren't immediately knee-deep in the latest and greatest, the bangwagon and the entire parade will pass on and leave us on the dusty road.&lt;br /&gt;
&lt;br /&gt;
I don't think so.  There is a reason  for the term &quot;bleeding edge.&quot;  And even the trailing edge is still off the ground.</description>
			<content:encoded><![CDATA[I am not so sure that libraries should be poised to jump on every bandwagon that comes along.  For one thing, we don't have the money to cook up new apps every time someone comes along with a commercial gadget or widget that is both "cool" and "hot."  <br />
<br />
Libraries can and probably should wait to see if an innovative device or app establishes itself.  <br />
<br />
Your underlying assumption seems to be that if libraries aren't immediately knee-deep in the latest and greatest, the bangwagon and the entire parade will pass on and leave us on the dusty road.<br />
<br />
I don't think so.  There is a reason  for the term "bleeding edge."  And even the trailing edge is still off the ground.]]></content:encoded>
			<link>http://blogs.lib.berkeley.edu/shimenawa.php/2008/07/14/the_show_room_library#c57819</link>
		</item>
				<item>
			<title>In response to: The Show Room Library</title>
			<pubDate>Tue, 15 Jul 2008 20:55:07 +0000</pubDate>
			<dc:creator>Joseph Ugoretz [Visitor]</dc:creator>
			<guid isPermaLink="false">c55843@http://blogs.lib.berkeley.edu/</guid>
			<description>The iPhone before this upgrade was a fantastic reader--if you &quot;jailbroke&quot; the phone and used books.app .&lt;br /&gt;
&lt;br /&gt;
With the upgrade, that's no longer necessary, and you can get the free app eReader (which allows purchasing books from ereader.com or --soon-- fictionwise).&lt;br /&gt;
&lt;br /&gt;
Even better (much, much, better) is the Bookshelf app available in the app store.  This is written by the same person who made books.app (which he did for free and accepted only donations to the Humane Society).  The app costs a small amount of money, but it allows easy loading and reading of free public domain books from (eg) gutenberg.org .&lt;br /&gt;
&lt;br /&gt;
The iPhone as a reader has two huge advantages over the Kindle--the backlight (for reading in bed), and the fact that you can actually put it in your pocket.&lt;br /&gt;
&lt;br /&gt;
Library apps should come soon, I agree.  But the ebook apps are already there and well-implemented.  I've been reading books on my iPhone for a year now--and love the fact that with the new software I have more options for loading them and for reading them.</description>
			<content:encoded><![CDATA[The iPhone before this upgrade was a fantastic reader--if you "jailbroke" the phone and used books.app .<br />
<br />
With the upgrade, that's no longer necessary, and you can get the free app eReader (which allows purchasing books from ereader.com or --soon-- fictionwise).<br />
<br />
Even better (much, much, better) is the Bookshelf app available in the app store.  This is written by the same person who made books.app (which he did for free and accepted only donations to the Humane Society).  The app costs a small amount of money, but it allows easy loading and reading of free public domain books from (eg) gutenberg.org .<br />
<br />
The iPhone as a reader has two huge advantages over the Kindle--the backlight (for reading in bed), and the fact that you can actually put it in your pocket.<br />
<br />
Library apps should come soon, I agree.  But the ebook apps are already there and well-implemented.  I've been reading books on my iPhone for a year now--and love the fact that with the new software I have more options for loading them and for reading them.]]></content:encoded>
			<link>http://blogs.lib.berkeley.edu/shimenawa.php/2008/07/14/the_show_room_library#c55843</link>
		</item>
				<item>
			<title>In response to: The Show Room Library</title>
			<pubDate>Tue, 15 Jul 2008 18:33:26 +0000</pubDate>
			<dc:creator>pbrantley [Member]</dc:creator>
			<guid isPermaLink="false">c55842@http://blogs.lib.berkeley.edu/</guid>
			<description>Jackie,&lt;br /&gt;
&lt;br /&gt;
Very cool.  I'll promote AT&amp;amp;T's contest more widely, although time is short.  &lt;br /&gt;
&lt;br /&gt;
However, I suspect that at least for libraries, the reward structure is not optimal.  Educause is less vital in their domain, and management support would be needed to exercise development privileges for mobile apps.  Linkages to student groups, an avowed target audience, are usually weak on large research campuses.&lt;br /&gt;
&lt;br /&gt;
I'm very keen to motivate additional work; please write me out of band if AT&amp;amp;T might eventually have interest in sponsoring a content focussed contest.  </description>
			<content:encoded><![CDATA[Jackie,<br />
<br />
Very cool.  I'll promote AT&amp;T's contest more widely, although time is short.  <br />
<br />
However, I suspect that at least for libraries, the reward structure is not optimal.  Educause is less vital in their domain, and management support would be needed to exercise development privileges for mobile apps.  Linkages to student groups, an avowed target audience, are usually weak on large research campuses.<br />
<br />
I'm very keen to motivate additional work; please write me out of band if AT&amp;T might eventually have interest in sponsoring a content focussed contest.  ]]></content:encoded>
			<link>http://blogs.lib.berkeley.edu/shimenawa.php/2008/07/14/the_show_room_library#c55842</link>
		</item>
				<item>
			<title>In response to: The Show Room Library</title>
			<pubDate>Tue, 15 Jul 2008 14:40:37 +0000</pubDate>
			<dc:creator>Jackie Siminitus [Visitor]</dc:creator>
			<guid isPermaLink="false">c55841@http://blogs.lib.berkeley.edu/</guid>
			<description>Peter,&lt;br /&gt;
Maybe it was bad timing, but I got zero interest when I offered CARL-IT a link to the AT&amp;amp;T 2008 Big Mobile on Campus contest so librarians could submit their mobile library applications to the mix.  It's not too late -- the contest runs through the end of August. See http://higheredcontest.wireless.att.com  -- This seems like a great opportunity to get library applications noticed.</description>
			<content:encoded><![CDATA[Peter,<br />
Maybe it was bad timing, but I got zero interest when I offered CARL-IT a link to the AT&amp;T 2008 Big Mobile on Campus contest so librarians could submit their mobile library applications to the mix.  It's not too late -- the contest runs through the end of August. See http://higheredcontest.wireless.att.com  -- This seems like a great opportunity to get library applications noticed.]]></content:encoded>
			<link>http://blogs.lib.berkeley.edu/shimenawa.php/2008/07/14/the_show_room_library#c55841</link>
		</item>
				<item>
			<title>In response to: The Show Room Library</title>
			<pubDate>Mon, 14 Jul 2008 23:55:05 +0000</pubDate>
			<dc:creator>Eric Lease Morgan [Visitor]</dc:creator>
			<guid isPermaLink="false">c55725@http://blogs.lib.berkeley.edu/</guid>
			<description>I seriously want to create a few iPhone apps such as one integrating with MyLibrary, our integrated library catalog, or my Alex Catalogue of Electronic Texts. I suppose the lack of applications is due to the low funding for non-essential purchases such as &quot;experimental&quot; iPhones.  --ELM</description>
			<content:encoded><![CDATA[I seriously want to create a few iPhone apps such as one integrating with MyLibrary, our integrated library catalog, or my Alex Catalogue of Electronic Texts. I suppose the lack of applications is due to the low funding for non-essential purchases such as "experimental" iPhones.  --ELM]]></content:encoded>
			<link>http://blogs.lib.berkeley.edu/shimenawa.php/2008/07/14/the_show_room_library#c55725</link>
		</item>
			</channel>
</rss>
