<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/1.5.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Evocative information tool</title>
	<link>http://theirwork.org/blog/2005/10/02/evocative-information-tool/</link>
	<description>Online community mapping</description>
	<pubDate>Sat, 19 May 2012 02:36:12 +0000</pubDate>
	<generator>http://wordpress.org/?v=1.5.2</generator>

	<item>
 		<title>Comment on Evocative information tool by: TheirWork Blog &#187; Blog Archive &#187; Looking forward</title>
		<link>http://theirwork.org/blog/2005/10/02/evocative-information-tool/#comment-15</link>
		<pubDate>Wed, 12 Oct 2005 23:17:45 +0000</pubDate>
		<guid>http://theirwork.org/blog/2005/10/02/evocative-information-tool/#comment-15</guid>
					<description>[...] We agreed that the wiki could become the database that drives the map and that the interface will allow soft data to get added. We also agreed that hard data might start to reveal itself. We agreed that handling data like this, keeping it in reserve, would enable us to develop a more suggestive tool. It would also keep in check that the project didn&amp;#8217;t get too data heavy. We know we don&amp;#8217;t want the project to be top heavy. In fact, at this point of the discussion, I shared with Emmet old meeting notes from earlier research I had carried out, (that I will later put up here or on the wiki) that demonstrate this was the model I was being guided towards in the past - a project that is driven government wise, data wise and design wise from the top down.  We are developing a tool by working from the bottom up - by way of workshops, interviews and an open online presence [...]</description>
		<content:encoded><![CDATA[	<p>[&#8230;] We agreed that the wiki could become the database that drives the map and that the interface will allow soft data to get added. We also agreed that hard data might start to reveal itself. We agreed that handling data like this, keeping it in reserve, would enable us to develop a more suggestive tool. It would also keep in check that the project didn&#8217;t get too data heavy. We know we don&#8217;t want the project to be top heavy. In fact, at this point of the discussion, I shared with Emmet old meeting notes from earlier research I had carried out, (that I will later put up here or on the wiki) that demonstrate this was the model I was being guided towards in the past - a project that is driven government wise, data wise and design wise from the top down.  We are developing a tool by working from the bottom up - by way of workshops, interviews and an open online presence [&#8230;]
</p>
]]></content:encoded>
				</item>
</channel>
</rss>

