<?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/"
		>
<channel>
	<title>Comments on: Valuing Users by Allowing Comments</title>
	<atom:link href="http://www.davidleeking.com/2007/11/05/valuing-users-by-allowing-comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.davidleeking.com/2007/11/05/valuing-users-by-allowing-comments/</link>
	<description>David Lee King is the Digital Branch &#38; Services Manager at the Topeka &#38; Shawnee County Public Library, where he plans, implements, and experiments with emerging technology trends. He has spoken in the U.S. and Canada about emerging trends, website usability and management, digital experience planning, and managing techie staff, and has been published in many library-related journals. David writes the Internet Spotlight column in Public Libraries Magazine with Michael Porter. David maintains a blog at http://www.davidleeking.com</description>
	<lastBuildDate>Fri, 19 Mar 2010 16:04:12 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: davidleeking</title>
		<link>http://www.davidleeking.com/2007/11/05/valuing-users-by-allowing-comments/comment-page-1/#comment-23556</link>
		<dc:creator>davidleeking</dc:creator>
		<pubDate>Mon, 14 Dec 2009 12:53:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidleeking.com/2007/11/05/valuing-users-by-allowing-comments/#comment-23556</guid>
		<description>I agree, most definitely. I think that including the ability to comment on our new site will alleviate some of the confusion you&#039;re addressing. A lot of the ability to comment on the new site will be context-based, sort of like our blog comments are now. So if you posted something to our papercuts blog, if someone wanted to comment, they&#039;d most likely be commenting about your post. So the context is sort of built-in.&lt;br&gt;&lt;br&gt;There will still be email, IM, etc comments that have the potential to be way more vague... but still, I think the digital branch, when opened, won&#039;t have too many problems in that regard (of course, I could be wrong - we&#039;ll see what happens).</description>
		<content:encoded><![CDATA[<p>I agree, most definitely. I think that including the ability to comment on our new site will alleviate some of the confusion you&#39;re addressing. A lot of the ability to comment on the new site will be context-based, sort of like our blog comments are now. So if you posted something to our papercuts blog, if someone wanted to comment, they&#39;d most likely be commenting about your post. So the context is sort of built-in.</p>
<p>There will still be email, IM, etc comments that have the potential to be way more vague&#8230; but still, I think the digital branch, when opened, won&#39;t have too many problems in that regard (of course, I could be wrong &#8211; we&#39;ll see what happens).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: P&#225;ginas de biblioteca en la red &#171; Alusión&#8230;Llamada Virtual</title>
		<link>http://www.davidleeking.com/2007/11/05/valuing-users-by-allowing-comments/comment-page-1/#comment-16390</link>
		<dc:creator>P&#225;ginas de biblioteca en la red &#171; Alusión&#8230;Llamada Virtual</dc:creator>
		<pubDate>Tue, 29 Jan 2008 10:49:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidleeking.com/2007/11/05/valuing-users-by-allowing-comments/#comment-16390</guid>
		<description>[...] David Lee King elabora una lista de razones por las cuales esto debe ser todo lo contrario.&#160; Los usuarios deben tener voz en en nuestras famosas páginas institucionales llenas de información sobre base de datos, horarios, tutoriales, etc., etc., etc., etc., &#8230; y aburridas y paralizadas a más no poder,&#160; sin que atraigan a esta generación de estudiantes que están acostumbrados a la rapidez del mensaje de texto en los celulares (entre mil otras cosas). [...]</description>
		<content:encoded><![CDATA[<p>[...] David Lee King elabora una lista de razones por las cuales esto debe ser todo lo contrario.&nbsp; Los usuarios deben tener voz en en nuestras famosas páginas institucionales llenas de información sobre base de datos, horarios, tutoriales, etc., etc., etc., etc., &#8230; y aburridas y paralizadas a más no poder,&nbsp; sin que atraigan a esta generación de estudiantes que están acostumbrados a la rapidez del mensaje de texto en los celulares (entre mil otras cosas). [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Project Play &#187; Blog Archive &#187; Weeks 10-12</title>
		<link>http://www.davidleeking.com/2007/11/05/valuing-users-by-allowing-comments/comment-page-1/#comment-12067</link>
		<dc:creator>Project Play &#187; Blog Archive &#187; Weeks 10-12</dc:creator>
		<pubDate>Mon, 19 Nov 2007 14:24:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidleeking.com/2007/11/05/valuing-users-by-allowing-comments/#comment-12067</guid>
		<description>[...] them and want to provide the best service possible. Take a look at David Lee King&#8217;s post, Valuing Users by Allowing Comments. He does a great job of talking about why inviting participation is so [...]</description>
		<content:encoded><![CDATA[<p>[...] them and want to provide the best service possible. Take a look at David Lee King&#8217;s post, Valuing Users by Allowing Comments. He does a great job of talking about why inviting participation is so [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MJ Ray</title>
		<link>http://www.davidleeking.com/2007/11/05/valuing-users-by-allowing-comments/comment-page-1/#comment-11792</link>
		<dc:creator>MJ Ray</dc:creator>
		<pubDate>Thu, 15 Nov 2007 15:28:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidleeking.com/2007/11/05/valuing-users-by-allowing-comments/#comment-11792</guid>
		<description>I&#039;ve written a bit more about these link-sploggers at http://mjr.towers.org.uk/blog/2007/badtech#pingbacksploggers</description>
		<content:encoded><![CDATA[<p>I&#8217;ve written a bit more about these link-sploggers at <a href="http://mjr.towers.org.uk/blog/2007/badtech#pingbacksploggers" rel="nofollow">http://mjr.towers.org.uk/blog/2007/badtech#pingbacksploggers</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Social Software in Libraries &#187; links for 2007-11-08</title>
		<link>http://www.davidleeking.com/2007/11/05/valuing-users-by-allowing-comments/comment-page-1/#comment-11601</link>
		<dc:creator>Social Software in Libraries &#187; links for 2007-11-08</dc:creator>
		<pubDate>Mon, 12 Nov 2007 23:43:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidleeking.com/2007/11/05/valuing-users-by-allowing-comments/#comment-11601</guid>
		<description>[...] Valuing Users by Allowing Comments : David Lee King (tags: chapter2 chapter14) [...]</description>
		<content:encoded><![CDATA[<p>[...] Valuing Users by Allowing Comments : David Lee King (tags: chapter2 chapter14) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: LIS651 &#187; Blog Archive &#187; Valuing Users by Allowing Comments</title>
		<link>http://www.davidleeking.com/2007/11/05/valuing-users-by-allowing-comments/comment-page-1/#comment-11587</link>
		<dc:creator>LIS651 &#187; Blog Archive &#187; Valuing Users by Allowing Comments</dc:creator>
		<pubDate>Mon, 12 Nov 2007 05:28:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidleeking.com/2007/11/05/valuing-users-by-allowing-comments/#comment-11587</guid>
		<description>[...] http://www.davidleeking.com/2007/11/05/valuing-users-by-allowing-comments/ [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://www.davidleeking.com/2007/11/05/valuing-users-by-allowing-comments/" rel="nofollow">http://www.davidleeking.com/2007/11/05/valuing-users-by-allowing-comments/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MJ Ray</title>
		<link>http://www.davidleeking.com/2007/11/05/valuing-users-by-allowing-comments/comment-page-1/#comment-11342</link>
		<dc:creator>MJ Ray</dc:creator>
		<pubDate>Thu, 08 Nov 2007 11:56:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidleeking.com/2007/11/05/valuing-users-by-allowing-comments/#comment-11342</guid>
		<description>I agree with most of the above.  I&#039;ve written more about how I comment and why comment routes are a big part of my decision whether or not to keep reading a site at http://mjr.towers.org.uk/blog/2007/webcss#blogfeedback

Of course, one problem with comments is comment-spam, like the &quot;so-and-so write an interesting post today on such-and-such. Here&#039;s a quick...&quot; ones currently shown at the start of these comments!  Does the value of comments outweigh the cost of needing to fight that spam?  It does for me...</description>
		<content:encoded><![CDATA[<p>I agree with most of the above.  I&#8217;ve written more about how I comment and why comment routes are a big part of my decision whether or not to keep reading a site at <a href="http://mjr.towers.org.uk/blog/2007/webcss#blogfeedback" rel="nofollow">http://mjr.towers.org.uk/blog/2007/webcss#blogfeedback</a></p>
<p>Of course, one problem with comments is comment-spam, like the &#8220;so-and-so write an interesting post today on such-and-such. Here&#8217;s a quick&#8230;&#8221; ones currently shown at the start of these comments!  Does the value of comments outweigh the cost of needing to fight that spam?  It does for me&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: OK-ACRL conference 2007 &#171; Into the Stacks</title>
		<link>http://www.davidleeking.com/2007/11/05/valuing-users-by-allowing-comments/comment-page-1/#comment-11291</link>
		<dc:creator>OK-ACRL conference 2007 &#171; Into the Stacks</dc:creator>
		<pubDate>Tue, 06 Nov 2007 23:15:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidleeking.com/2007/11/05/valuing-users-by-allowing-comments/#comment-11291</guid>
		<description>[...] and while all this was going on, David Lee King posted some thoughts on how allowing comments shows that you value customers that are very in keeping with the whole &#8220;2.0 as conversation&#8221; idea that David Silver [...]</description>
		<content:encoded><![CDATA[<p>[...] and while all this was going on, David Lee King posted some thoughts on how allowing comments shows that you value customers that are very in keeping with the whole &#8220;2.0 as conversation&#8221; idea that David Silver [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: davidleeking</title>
		<link>http://www.davidleeking.com/2007/11/05/valuing-users-by-allowing-comments/comment-page-1/#comment-11285</link>
		<dc:creator>davidleeking</dc:creator>
		<pubDate>Tue, 06 Nov 2007 16:53:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidleeking.com/2007/11/05/valuing-users-by-allowing-comments/#comment-11285</guid>
		<description>I agree, most definitely. I think that including the ability to comment on our new site will alleviate some of the confusion you&#039;re addressing. A lot of the ability to comment on the new site will be context-based, sort of like our blog comments are now. So if you posted something to our papercuts blog, if someone wanted to comment, they&#039;d most likely be commenting about your post. So the context is sort of built-in.

There will still be email, IM, etc comments that have the potential to be way more vague... but still, I think the digital branch, when opened, won&#039;t have too many problems in that regard (of course, I could be wrong - we&#039;ll see what happens).</description>
		<content:encoded><![CDATA[<p>I agree, most definitely. I think that including the ability to comment on our new site will alleviate some of the confusion you&#8217;re addressing. A lot of the ability to comment on the new site will be context-based, sort of like our blog comments are now. So if you posted something to our papercuts blog, if someone wanted to comment, they&#8217;d most likely be commenting about your post. So the context is sort of built-in.</p>
<p>There will still be email, IM, etc comments that have the potential to be way more vague&#8230; but still, I think the digital branch, when opened, won&#8217;t have too many problems in that regard (of course, I could be wrong &#8211; we&#8217;ll see what happens).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob</title>
		<link>http://www.davidleeking.com/2007/11/05/valuing-users-by-allowing-comments/comment-page-1/#comment-11283</link>
		<dc:creator>Rob</dc:creator>
		<pubDate>Tue, 06 Nov 2007 14:44:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidleeking.com/2007/11/05/valuing-users-by-allowing-comments/#comment-11283</guid>
		<description>David,
I agree with what Casey says about allowing comments in multiple places.  In fact, you and I have talked about that as we develop our digital branch.  From the recieving side of this, if all of the comment options lead back to a generic email or phone number it can be very frustrating when you try to help someone.  The customer assumes that when they click on a contact button in a specific program box and write &quot;Sign me up,&quot; the reciever will know what that program was.  I have gotten into email conversations with people who don&#039;t understand that I have no idea which program they want signed up for. I don&#039;t know if the technology is in place to make that connection but it would make both the customer, who is assuming and the reciever who is clueless both very happy.  While this is a purposly simple example, I can see opportunities for the customers to feel that they are not valued, similar to Casey&#039;s example of the 800 number thing with ebay simply because information is not widely available to all participants.  We just want to be careful that we don&#039;t inadvertently make the situation worse instead of better as we add points of contact.</description>
		<content:encoded><![CDATA[<p>David,<br />
I agree with what Casey says about allowing comments in multiple places.  In fact, you and I have talked about that as we develop our digital branch.  From the recieving side of this, if all of the comment options lead back to a generic email or phone number it can be very frustrating when you try to help someone.  The customer assumes that when they click on a contact button in a specific program box and write &#8220;Sign me up,&#8221; the reciever will know what that program was.  I have gotten into email conversations with people who don&#8217;t understand that I have no idea which program they want signed up for. I don&#8217;t know if the technology is in place to make that connection but it would make both the customer, who is assuming and the reciever who is clueless both very happy.  While this is a purposly simple example, I can see opportunities for the customers to feel that they are not valued, similar to Casey&#8217;s example of the 800 number thing with ebay simply because information is not widely available to all participants.  We just want to be careful that we don&#8217;t inadvertently make the situation worse instead of better as we add points of contact.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
