<?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"
	>
<channel>
	<title>Comments on: Only as good as&#8230;</title>
	<atom:link href="http://remainingrelevant.net/remaining/121/feed" rel="self" type="application/rss+xml" />
	<link>http://remainingrelevant.net/remaining/121</link>
	<description>Why stop dreaming when you wake up?</description>
	<pubDate>Thu, 04 Dec 2008 22:01:12 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Remaining Relevant &#187; Blog Archive &#187; Sad passing: Dean Ray von Dran</title>
		<link>http://remainingrelevant.net/remaining/121#comment-447</link>
		<dc:creator>Remaining Relevant &#187; Blog Archive &#187; Sad passing: Dean Ray von Dran</dc:creator>
		<pubDate>Mon, 23 Jul 2007 16:48:27 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/remainingrelevant/?p=121#comment-447</guid>
		<description>[...] was Dean von Dran who greeted our class when I started at SU. He was full of enthusiasm and play and kindness. I never had occasion [...]</description>
		<content:encoded><![CDATA[<p>[...] was Dean von Dran who greeted our class when I started at SU. He was full of enthusiasm and play and kindness. I never had occasion [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Remaining Relevant &#187; Blog Archive &#187; Library 2.0 Tours New Hampshire</title>
		<link>http://remainingrelevant.net/remaining/121#comment-446</link>
		<dc:creator>Remaining Relevant &#187; Blog Archive &#187; Library 2.0 Tours New Hampshire</dc:creator>
		<pubDate>Fri, 16 Jun 2006 04:17:23 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/remainingrelevant/?p=121#comment-446</guid>
		<description>[...] You decide if this is something for your library. Implement a pilot project (don&#8217;t forget to publicize it). Make a IM reference page. Write a policy (if you must). [...]</description>
		<content:encoded><![CDATA[<p>[...] You decide if this is something for your library. Implement a pilot project (don&#8217;t forget to publicize it). Make a IM reference page. Write a policy (if you must). [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Remaining Relevant &#187; Blog Archive &#187; Running away to see you</title>
		<link>http://remainingrelevant.net/remaining/121#comment-445</link>
		<dc:creator>Remaining Relevant &#187; Blog Archive &#187; Running away to see you</dc:creator>
		<pubDate>Fri, 02 Jun 2006 18:46:30 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/remainingrelevant/?p=121#comment-445</guid>
		<description>[...] Denver bound (1)Debut (4)Interoperability in Library Systems (1)RSS, Perl, and New Books, OH MY! (4)Only as good as... (3)the key to success (1)They only suck 'cause we let 'em (4)Something about the springtime (1)Another sad day... (2)Fondest of Farewells (2)Google Nation (1)Adventures in xml (1)Part Three - Buy, Hack, or Build (2)Greek Tragedy (1)the sharp edge of a metaphor (1) [...]</description>
		<content:encoded><![CDATA[<p>[...] Denver bound (1)Debut (4)Interoperability in Library Systems (1)RSS, Perl, and New Books, OH MY! (4)Only as good as&#8230; (3)the key to success (1)They only suck &#8217;cause we let &#8216;em (4)Something about the springtime (1)Another sad day&#8230; (2)Fondest of Farewells (2)Google Nation (1)Adventures in xml (1)Part Three - Buy, Hack, or Build (2)Greek Tragedy (1)the sharp edge of a metaphor (1) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lichen</title>
		<link>http://remainingrelevant.net/remaining/121#comment-444</link>
		<dc:creator>Lichen</dc:creator>
		<pubDate>Wed, 17 May 2006 12:52:07 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/remainingrelevant/?p=121#comment-444</guid>
		<description>Tom - Thank you for you congrats.  I'm shameless enough to offer some &lt;a href="http://www.flickr.com/photos/thegloaming/" rel="nofollow"&gt;graduation&lt;/a&gt; &lt;a href="http://www.flickr.com/photos/jahw/145586424/" rel="nofollow"&gt;photos&lt;/a&gt;.  I found your technology plan unarguably sensible.  I'm sure your director and staff will agree.

Brian - Tools like RSS, IM and the like DO have a place in the library, but their use must be reevaluated regularly and their continuing relevance constantly examined by the &lt;i&gt;web staff&lt;/i&gt;.  I mean that we can't invest in the web site's tools, this would risk quick obsolescence - and a continuing &lt;a href="http://en.wikipedia.org/wiki/Information_silo" rel="nofollow"&gt;silo structure&lt;/a&gt;.  I think this follows your idea about approaching new online tools from a collection development standpoint.

I agree with you... I would summarize simply that every new service must be related to the organization's misson and plans.  If it doesn't, it's inappropriate.</description>
		<content:encoded><![CDATA[<p>Tom - Thank you for you congrats.  I&#8217;m shameless enough to offer some <a href="http://www.flickr.com/photos/thegloaming/" rel="nofollow">graduation</a> <a href="http://www.flickr.com/photos/jahw/145586424/" rel="nofollow">photos</a>.  I found your technology plan unarguably sensible.  I&#8217;m sure your director and staff will agree.</p>
<p>Brian - Tools like RSS, IM and the like DO have a place in the library, but their use must be reevaluated regularly and their continuing relevance constantly examined by the <i>web staff</i>.  I mean that we can&#8217;t invest in the web site&#8217;s tools, this would risk quick obsolescence - and a continuing <a href="http://en.wikipedia.org/wiki/Information_silo" rel="nofollow">silo structure</a>.  I think this follows your idea about approaching new online tools from a collection development standpoint.</p>
<p>I agree with you&#8230; I would summarize simply that every new service must be related to the organization&#8217;s misson and plans.  If it doesn&#8217;t, it&#8217;s inappropriate.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: herzogbr</title>
		<link>http://remainingrelevant.net/remaining/121#comment-443</link>
		<dc:creator>herzogbr</dc:creator>
		<pubDate>Tue, 16 May 2006 20:24:52 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/remainingrelevant/?p=121#comment-443</guid>
		<description>I feel great pressure to improve the quality of my comments, since this is now the blog of a Master, and not just a lowly student.  Way to go.

But foregoing quality, I have long liked the idea that a library's website should essentially be a branch library - meaning that it can serve patrons independently of the main building.  By extension, then, it is absolutely necessary to &lt;i&gt;staff&lt;/i&gt; this branch appropriately.  In many cases, it seems library websites are an afterthought, or are dumped on whoever happens to have the time, the inclination, or the skills (but not necessarily all three), or are contracted out to a third-party developer who creates the website but does not maintain it.  It seems that before a library website could ever hope to be and remain useful to patrons, it must be staffed like any other branch.

Also, in regards to tools like RSS, IM, etc.: jumping on the bandwagon and saying a library offers these doesn't seem inherently useful to me - these technologies are just tools, after all, like "print" or "fax."  A library can say "we've got books," but if all those books are outdated or duplicate copies, they are not a useful tool for patrons.  So, rather than libraries just offering more technology tools out of peer pressure, I'd like something along the lines of Tom Boone's goals, but that would serve as an actual collection development plan that includes not only these tools, but information sources as well.

Because, does just offering IM reference and RSS updates of events make a library website a branch library?  These certainly provide for interactivity, but do they provide access to information?  Someone could IM the reference desk and ask a question, which the reference librarian could then look up in a book - but that's not a branch library, that's a reference service.  A "branch library" shouldn't strive for patron interactivity, but patron independence (libraries should provide access to information, not access to librarians).  Which would require &lt;i&gt;all&lt;/i&gt; library tools, including the book collection and databases with At-Home access, to be available remotely (and I mean the actual full text, not just our catalog citations).  Google Books is going that way, but even that still doesn't sit well with me (pesky copyright laws).

So before we create a MySpace profile for the library (or Facebook for the academics) because it's the hip thing to do, we need to figure out what happens next.  Would kids actually contact the library through MySpace?  And if they did, will we have anything to offer, or will all of our answers be "well, if you come into the library, we have a book</description>
		<content:encoded><![CDATA[<p>I feel great pressure to improve the quality of my comments, since this is now the blog of a Master, and not just a lowly student.  Way to go.</p>
<p>But foregoing quality, I have long liked the idea that a library&#8217;s website should essentially be a branch library - meaning that it can serve patrons independently of the main building.  By extension, then, it is absolutely necessary to <i>staff</i> this branch appropriately.  In many cases, it seems library websites are an afterthought, or are dumped on whoever happens to have the time, the inclination, or the skills (but not necessarily all three), or are contracted out to a third-party developer who creates the website but does not maintain it.  It seems that before a library website could ever hope to be and remain useful to patrons, it must be staffed like any other branch.</p>
<p>Also, in regards to tools like RSS, IM, etc.: jumping on the bandwagon and saying a library offers these doesn&#8217;t seem inherently useful to me - these technologies are just tools, after all, like &#8220;print&#8221; or &#8220;fax.&#8221;  A library can say &#8220;we&#8217;ve got books,&#8221; but if all those books are outdated or duplicate copies, they are not a useful tool for patrons.  So, rather than libraries just offering more technology tools out of peer pressure, I&#8217;d like something along the lines of Tom Boone&#8217;s goals, but that would serve as an actual collection development plan that includes not only these tools, but information sources as well.</p>
<p>Because, does just offering IM reference and RSS updates of events make a library website a branch library?  These certainly provide for interactivity, but do they provide access to information?  Someone could IM the reference desk and ask a question, which the reference librarian could then look up in a book - but that&#8217;s not a branch library, that&#8217;s a reference service.  A &#8220;branch library&#8221; shouldn&#8217;t strive for patron interactivity, but patron independence (libraries should provide access to information, not access to librarians).  Which would require <i>all</i> library tools, including the book collection and databases with At-Home access, to be available remotely (and I mean the actual full text, not just our catalog citations).  Google Books is going that way, but even that still doesn&#8217;t sit well with me (pesky copyright laws).</p>
<p>So before we create a MySpace profile for the library (or Facebook for the academics) because it&#8217;s the hip thing to do, we need to figure out what happens next.  Would kids actually contact the library through MySpace?  And if they did, will we have anything to offer, or will all of our answers be &#8220;well, if you come into the library, we have a book</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Boone</title>
		<link>http://remainingrelevant.net/remaining/121#comment-442</link>
		<dc:creator>Tom Boone</dc:creator>
		<pubDate>Mon, 15 May 2006 18:43:13 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/remainingrelevant/?p=121#comment-442</guid>
		<description>Congratulations on your MLIS degree!

I certainly hope your optimism about the tech plan I'm drafting is contagious, because my library director still has to approve it. If and when she does, I'll then have to convince the rest of our library staff to buy into the plan -- without them staging a mutiny first.

But I'm in full agreement with you that a library is only as good as its online services, particularly in an academic environment where the majority of students are members of a generation that expects access to everything from anywhere at anytime. If we don't give them that access, someone else will. Which will make us obsolete.</description>
		<content:encoded><![CDATA[<p>Congratulations on your MLIS degree!</p>
<p>I certainly hope your optimism about the tech plan I&#8217;m drafting is contagious, because my library director still has to approve it. If and when she does, I&#8217;ll then have to convince the rest of our library staff to buy into the plan &#8212; without them staging a mutiny first.</p>
<p>But I&#8217;m in full agreement with you that a library is only as good as its online services, particularly in an academic environment where the majority of students are members of a generation that expects access to everything from anywhere at anytime. If we don&#8217;t give them that access, someone else will. Which will make us obsolete.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
