<?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: The Podcast: Sharing Flipcharts</title>
	<atom:link href="http://budtheteacher.com/blog/2009/01/10/the-podcast-sharing-flipcharts/feed/" rel="self" type="application/rss+xml" />
	<link>http://budtheteacher.com/blog/2009/01/10/the-podcast-sharing-flipcharts/</link>
	<description>Inquiry &#38; Reflection for Better Learning</description>
	<lastBuildDate>Tue, 22 May 2012 11:05:27 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Michelle Bourgeois</title>
		<link>http://budtheteacher.com/blog/2009/01/10/the-podcast-sharing-flipcharts/comment-page-1/#comment-2095</link>
		<dc:creator>Michelle Bourgeois</dc:creator>
		<pubDate>Sun, 11 Jan 2009 02:02:19 +0000</pubDate>
		<guid isPermaLink="false">http://budtheteacher.com/blog/?p=776#comment-2095</guid>
		<description>Instead of giving you answers, can I offer questions  and thoughts?
1.  Your audience consists of teachers of different grade levels and subject areas.  Would a universal feed be of use to them? Is there a tool that would allow a customizable feed based on their teaching needs?
2.  One of the things I find lacking in a site that is designed solely to share assets is the inability to support conversations around those resources.  Is there a tool that would allow for discussion threads/ratings/conversations to spring up around each asset?
3.  Where are your users in terms of their comfort level with resource sharing and &quot;one more thing&quot; syndrome?
4.  Another powerful concept to think about is allowing the community to take ownership of the resource.  Is there a tool that would allow dedicated &quot;power users&quot; to manage and organize content in their area of interest for the benefit of all users? 
Will a blog fit your needs? A wiki? Moodle? Maybe Drupal is something to explore.  Just make sure to &quot;think like a teacher&quot; and you&#039;ll come up with the right solution. Whatever you use, I know you&#039;ll make it more about the outcomes than about the tool.

&lt;abbr&gt;&lt;em&gt;Michelle Bourgeoiss last blog post..&lt;a href=&quot;http://milobo.edublogs.org/2009/01/07/seven-things/&quot; rel=&quot;nofollow&quot;&gt;Seven Things&lt;/a&gt;&lt;/abbr&gt;&lt;/em&gt;</description>
		<content:encoded><![CDATA[<p>Instead of giving you answers, can I offer questions  and thoughts?<br />
1.  Your audience consists of teachers of different grade levels and subject areas.  Would a universal feed be of use to them? Is there a tool that would allow a customizable feed based on their teaching needs?<br />
2.  One of the things I find lacking in a site that is designed solely to share assets is the inability to support conversations around those resources.  Is there a tool that would allow for discussion threads/ratings/conversations to spring up around each asset?<br />
3.  Where are your users in terms of their comfort level with resource sharing and &#8220;one more thing&#8221; syndrome?<br />
4.  Another powerful concept to think about is allowing the community to take ownership of the resource.  Is there a tool that would allow dedicated &#8220;power users&#8221; to manage and organize content in their area of interest for the benefit of all users?<br />
Will a blog fit your needs? A wiki? Moodle? Maybe Drupal is something to explore.  Just make sure to &#8220;think like a teacher&#8221; and you&#8217;ll come up with the right solution. Whatever you use, I know you&#8217;ll make it more about the outcomes than about the tool.</p>
<p><abbr><em>Michelle Bourgeoiss last blog post..<a href="http://milobo.edublogs.org/2009/01/07/seven-things/" rel="nofollow">Seven Things</a></em></abbr></p>
]]></content:encoded>
	</item>
</channel>
</rss>

