<?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: A Comment About Comments</title>
	<atom:link href="http://libraryrevolution.com/2007/06/22/a-comment-about-comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://libraryrevolution.com/2007/06/22/a-comment-about-comments/</link>
	<description>The Library Status Quo Must Go!</description>
	<pubDate>Thu, 24 Jul 2008 02:36:36 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Thing 1: Blogs : kongtemplation</title>
		<link>http://libraryrevolution.com/2007/06/22/a-comment-about-comments/#comment-609</link>
		<dc:creator>Thing 1: Blogs : kongtemplation</dc:creator>
		<pubDate>Thu, 04 Oct 2007 06:31:13 +0000</pubDate>
		<guid isPermaLink="false">http://libraryrevolution.com/2007/06/22/a-comment-about-comments/#comment-609</guid>
		<description>[...] on the library&#8217;s websites is a big deal imho. And speaking of comments, take a look at this entry from a blog I enjoy reading; it addresses the important question of how to handle the dearth of [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] on the library&#8217;s websites is a big deal imho. And speaking of comments, take a look at this entry from a blog I enjoy reading; it addresses the important question of how to handle the dearth of [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anne</title>
		<link>http://libraryrevolution.com/2007/06/22/a-comment-about-comments/#comment-281</link>
		<dc:creator>Anne</dc:creator>
		<pubDate>Sat, 07 Jul 2007 19:27:42 +0000</pubDate>
		<guid isPermaLink="false">http://libraryrevolution.com/2007/06/22/a-comment-about-comments/#comment-281</guid>
		<description>tramadol</description>
		<content:encoded><![CDATA[<p>tramadol</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sam</title>
		<link>http://libraryrevolution.com/2007/06/22/a-comment-about-comments/#comment-245</link>
		<dc:creator>sam</dc:creator>
		<pubDate>Tue, 26 Jun 2007 16:47:43 +0000</pubDate>
		<guid isPermaLink="false">http://libraryrevolution.com/2007/06/22/a-comment-about-comments/#comment-245</guid>
		<description>Thanks, I've been thinking about comments a lot lately in relation to our library blog so this is very timely.  Our blog is only a few months old and it's been interesting to see which posts draw comments and which don't--your points really hold up.  The informational posts are useful to "get the message out," but not very interactive.

I also second your point that comments don't reflect readership.  Because I am a stats-obsessed librarian, I installed "Counterize" on our blog so I can track how many unique visitors we get and how they are referred to us.  Seeing which random google searches have led searchers to us has been a nice bonus too.

One other thought: we have a pretty targeted clientele (branch library within an academic system) and when we started the blog I was curious to see the extent to which we could begin to rely on blog posts + comments for feedback instead of mass emails and so far I think privacy trumps ease so that a post asking for thoughts on a new database or product or purchase will draw off-line replies by email.  Wonder if that will change over time?</description>
		<content:encoded><![CDATA[<p>Thanks, I&#8217;ve been thinking about comments a lot lately in relation to our library blog so this is very timely.  Our blog is only a few months old and it&#8217;s been interesting to see which posts draw comments and which don&#8217;t&#8211;your points really hold up.  The informational posts are useful to &#8220;get the message out,&#8221; but not very interactive.</p>
<p>I also second your point that comments don&#8217;t reflect readership.  Because I am a stats-obsessed librarian, I installed &#8220;Counterize&#8221; on our blog so I can track how many unique visitors we get and how they are referred to us.  Seeing which random google searches have led searchers to us has been a nice bonus too.</p>
<p>One other thought: we have a pretty targeted clientele (branch library within an academic system) and when we started the blog I was curious to see the extent to which we could begin to rely on blog posts + comments for feedback instead of mass emails and so far I think privacy trumps ease so that a post asking for thoughts on a new database or product or purchase will draw off-line replies by email.  Wonder if that will change over time?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Not getting many comments?</title>
		<link>http://libraryrevolution.com/2007/06/22/a-comment-about-comments/#comment-244</link>
		<dc:creator>Not getting many comments?</dc:creator>
		<pubDate>Mon, 25 Jun 2007 15:50:15 +0000</pubDate>
		<guid isPermaLink="false">http://libraryrevolution.com/2007/06/22/a-comment-about-comments/#comment-244</guid>
		<description>[...] This post has several ideas about how to get your patrons involved in your website. A few gems: 1. First and foremost, write something worth commenting on. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] This post has several ideas about how to get your patrons involved in your website. A few gems: 1. First and foremost, write something worth commenting on. [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2007-06-25 &#171; Off the trolley</title>
		<link>http://libraryrevolution.com/2007/06/22/a-comment-about-comments/#comment-243</link>
		<dc:creator>links for 2007-06-25 &#171; Off the trolley</dc:creator>
		<pubDate>Mon, 25 Jun 2007 04:21:02 +0000</pubDate>
		<guid isPermaLink="false">http://libraryrevolution.com/2007/06/22/a-comment-about-comments/#comment-243</guid>
		<description>[...] Library Revolution » Blog Archive » A Comment About Comments (tags: library2.0 libraryblogs) [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Library Revolution » Blog Archive » A Comment About Comments (tags: library2.0 libraryblogs) [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
