<?xml version="1.0" encoding="utf-8"?><!-- generator="wordpress/1.5.1-alpha" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: The ubiquity of social tools in context of workflows</title>
	<link>http://libraryclips.blogsome.com/2008/09/26/the-ubiquity-of-social-tools-in-context-of-workflows/</link>
	<description>sharing ideas thoughts and feedback</description>
	<pubDate>Sun, 12 Feb 2012 17:54:33 +0000</pubDate>
	<generator>http://wordpress.org/?v=1.5.1-alpha</generator>

	<item>
		<title>by: Portals and KM</title>
		<link>http://libraryclips.blogsome.com/2008/09/26/the-ubiquity-of-social-tools-in-context-of-workflows/#comment-32626</link>
		<pubDate>Tue, 30 Sep 2008 06:44:13 +0100</pubDate>
		<guid>http://libraryclips.blogsome.com/2008/09/26/the-ubiquity-of-social-tools-in-context-of-workflows/#comment-32626</guid>
					<description>&lt;strong&gt;Library Clips on Knowledge Management, Social Software and Workflow&lt;/strong&gt;

The blogger at Library Clips recently wrote an interesting post on the ubiquity of social tools in context of workflows. Library Clips begins with a quote from a prior post, “I really think blogs and the like need to be</description>
		<content:encoded><![CDATA[	<p><strong>Library Clips on Knowledge Management, Social Software and Workflow</strong></p>
	<p>The blogger at Library Clips recently wrote an interesting post on the ubiquity of social tools in context of workflows. Library Clips begins with a quote from a prior post, “I really think blogs and the like need to be
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Daniel J. Pritchett</title>
		<link>http://libraryclips.blogsome.com/2008/09/26/the-ubiquity-of-social-tools-in-context-of-workflows/#comment-32622</link>
		<pubDate>Fri, 26 Sep 2008 21:57:29 +0100</pubDate>
		<guid>http://libraryclips.blogsome.com/2008/09/26/the-ubiquity-of-social-tools-in-context-of-workflows/#comment-32622</guid>
					<description>I like it!  It's really easy to fall into the trap of wanting your newest tool to replace all of your previous tools.  Seems much better to add a wiki (for instance) to things that already worked rather than trying to load everything you touch into a wiki.</description>
		<content:encoded><![CDATA[	<p>I like it!  It&#8217;s really easy to fall into the trap of wanting your newest tool to replace all of your previous tools.  Seems much better to add a wiki (for instance) to things that already worked rather than trying to load everything you touch into a wiki.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>

