<?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: Wiki for gathering a list, and the need for comments and notifications</title>
	<link>http://libraryclips.blogsome.com/2008/04/28/wiki-for-gathering-a-list-and-the-need-for-comments-and-notifications/</link>
	<description>sharing ideas thoughts and feedback</description>
	<pubDate>Sat, 28 Nov 2009 14:24:12 +0000</pubDate>
	<generator>http://wordpress.org/?v=1.5.1-alpha</generator>

	<item>
		<title>by: John Tropea</title>
		<link>http://libraryclips.blogsome.com/2008/04/28/wiki-for-gathering-a-list-and-the-need-for-comments-and-notifications/#comment-32654</link>
		<pubDate>Wed, 29 Oct 2008 22:42:10 +0000</pubDate>
		<guid>http://libraryclips.blogsome.com/2008/04/28/wiki-for-gathering-a-list-and-the-need-for-comments-and-notifications/#comment-32654</guid>
					<description>Nice Comment Jonathan,

I like your point about &quot;process-based aspects of collaboration&quot;, it brings up a new area of a self-made structured way to do knowledge work...assemble your own workflow.

That is, the tools (wiki, blog) are unstructured which is good, but how do we assemble them into a work flow. How do I join (not necessarily mashup) web 2.0 tools into a flow eg. make your own &quot;basecamp&quot;, the way you can make your own &quot;ning&quot;.

How do I make my own task management system, there are heaps of existing ones with web 2.0 tools, which is great, but I also want to glue my own together, assemble the flow of how you move from one part of the task to the next.

I guess this is possible in the wikis these days that are more like CMS's, as we have themed wikipages. Each wikipage could be structured to be a part in the process.

In addition to this it would be good to wikify and blogify tools that are not blogs or wikis. I believe an &quot;edit this&quot; button can be a feature without having to be a wiki, or be able to &quot;blog this&quot; piece of information.
This way we are incorporating what is actually &quot;practiced&quot; right from the &quot;process&quot; tools. Rather than having to remember to go and write a blog post afterwards, or make sure you add something to the wiki after the fact, we often forget or move on to our next task, so to do it at the time you are doing your task is more effective.

http://libraryclips.blogsome.com/2008/09/26/the-ubiquity-of-social-tools-in-context-of-workflows/

http://libraryclips.blogsome.com/2008/10/16/taskonomy-assembling-for-use/
</description>
		<content:encoded><![CDATA[	<p>Nice Comment Jonathan,</p>
	<p>I like your point about &#8220;process-based aspects of collaboration&#8221;, it brings up a new area of a self-made structured way to do knowledge work&#8230;assemble your own workflow.</p>
	<p>That is, the tools (wiki, blog) are unstructured which is good, but how do we assemble them into a work flow. How do I join (not necessarily mashup) web 2.0 tools into a flow eg. make your own &#8220;basecamp&#8221;, the way you can make your own &#8220;ning&#8221;.</p>
	<p>How do I make my own task management system, there are heaps of existing ones with web 2.0 tools, which is great, but I also want to glue my own together, assemble the flow of how you move from one part of the task to the next.</p>
	<p>I guess this is possible in the wikis these days that are more like CMS&#8217;s, as we have themed wikipages. Each wikipage could be structured to be a part in the process.</p>
	<p>In addition to this it would be good to wikify and blogify tools that are not blogs or wikis. I believe an &#8220;edit this&#8221; button can be a feature without having to be a wiki, or be able to &#8220;blog this&#8221; piece of information.<br />
This way we are incorporating what is actually &#8220;practiced&#8221; right from the &#8220;process&#8221; tools. Rather than having to remember to go and write a blog post afterwards, or make sure you add something to the wiki after the fact, we often forget or move on to our next task, so to do it at the time you are doing your task is more effective.</p>
	<p><a href='http://libraryclips.blogsome.com/2008/09/26/the-ubiquity-of-social-tools-in-context-of-workflows/' rel='nofollow'>http://libraryclips.blogsome.com/2008/09/26/the-ubiquity-of-social-tools-in-context-of-workflows/</a></p>
	<p><a href='http://libraryclips.blogsome.com/2008/10/16/taskonomy-assembling-for-use/' rel='nofollow'>http://libraryclips.blogsome.com/2008/10/16/taskonomy-assembling-for-use/</a>
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Jonathan Barel</title>
		<link>http://libraryclips.blogsome.com/2008/04/28/wiki-for-gathering-a-list-and-the-need-for-comments-and-notifications/#comment-32647</link>
		<pubDate>Tue, 28 Oct 2008 10:22:12 +0000</pubDate>
		<guid>http://libraryclips.blogsome.com/2008/04/28/wiki-for-gathering-a-list-and-the-need-for-comments-and-notifications/#comment-32647</guid>
					<description>There's a lot to be said for Wikis. They're a great platform for hashing ideas and brainstorming.
In fact, I remember reading about Lawrence Lessig &quot;wikifying&quot; his new project before going on vacation, so the community can help develop it. That was the first time I saw it used as a verb.
In the enterprise, it's also important to see the chronological/process-based aspects of collaboration. It's why BPM is such a big thing these days.
Wikis fill a need for a non-structured format -- you can do anything you like with them -- but the whole field of &quot;Human Process Management&quot; is still in its infancy. In many businesses it's hard to train people to use &quot;new-fangled&quot; tools like these, as you witnessed yourself with people who &quot;reply-to-all&quot;.
Yeah for progess!</description>
		<content:encoded><![CDATA[	<p>There&#8217;s a lot to be said for Wikis. They&#8217;re a great platform for hashing ideas and brainstorming.<br />
In fact, I remember reading about Lawrence Lessig &#8220;wikifying&#8221; his new project before going on vacation, so the community can help develop it. That was the first time I saw it used as a verb.<br />
In the enterprise, it&#8217;s also important to see the chronological/process-based aspects of collaboration. It&#8217;s why BPM is such a big thing these days.<br />
Wikis fill a need for a non-structured format &#8212; you can do anything you like with them &#8212; but the whole field of &#8220;Human Process Management&#8221; is still in its infancy. In many businesses it&#8217;s hard to train people to use &#8220;new-fangled&#8221; tools like these, as you witnessed yourself with people who &#8220;reply-to-all&#8221;.<br />
Yeah for progess!
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: klecu</title>
		<link>http://libraryclips.blogsome.com/2008/04/28/wiki-for-gathering-a-list-and-the-need-for-comments-and-notifications/#comment-32645</link>
		<pubDate>Mon, 27 Oct 2008 21:46:44 +0000</pubDate>
		<guid>http://libraryclips.blogsome.com/2008/04/28/wiki-for-gathering-a-list-and-the-need-for-comments-and-notifications/#comment-32645</guid>
					<description>I have not used any commercial wiki apps, but have researched a few like &lt;a href=&quot;http://www.atlassian.com/software/confluence/&quot; rel=&quot;nofollow&quot;&gt;Confluence&lt;/a&gt; that might have more of the features you're looking for. If you are in a good-sized organization you might try something like that.</description>
		<content:encoded><![CDATA[	<p>I have not used any commercial wiki apps, but have researched a few like <a href="http://www.atlassian.com/software/confluence/" rel="nofollow">Confluence</a> that might have more of the features you&#8217;re looking for. If you are in a good-sized organization you might try something like that.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
