<?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: Self-designed centralization</title>
	<atom:link href="http://szanne.edublogs.org/2007/01/25/self-designed-centralization/feed/" rel="self" type="application/rss+xml" />
	<link>http://szanne.edublogs.org/2007/01/25/self-designed-centralization/</link>
	<description>blogging about .edu stuff</description>
	<lastBuildDate>Thu, 08 Mar 2007 20:12:07 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Steve Ehrmann</title>
		<link>http://szanne.edublogs.org/2007/01/25/self-designed-centralization/comment-page-1/#comment-308</link>
		<dc:creator>Steve Ehrmann</dc:creator>
		<pubDate>Thu, 01 Feb 2007 20:24:30 +0000</pubDate>
		<guid isPermaLink="false">http://szanne.edublogs.org/2007/01/25/self-designed-centralization/#comment-308</guid>
		<description>MERLOT is working on including some stories, thanks to a FIPSE grant for a project called ELIXR that is just getting underway. 

Some years ago I wrote a report on the use of stories for faculty development:
http://www.tltgroup.org/ProFacDev/video-uses-for-profacdev.html
A group of us spent a day watching videos and looking at web sites. We concluded, among other things, that we had seen two types of materials, both of which could be classed as stories:
a) stories intended to help the user visualize a way of teaching and become interested in trying it
b) stories intended to give the user, interested in a particular way of teaching, the vicarious experience of getting into trouble so that the reader (usually in a seminar with others) could learn how to identify and analyze that type of problem, and figure out how to deal with it (e.g., how to turn it into a teachable moment).

These kinds of stories, especially &quot;b&quot;, are very important for educational uses of technology, but I&#039;ve seen almost none in use. The University of Victoria in Canada has, I believe, developed a DVD of type &quot;b&quot; stories arising from educational uses of technology. The DVD is intended for use in faculty development.  Has anyone seen and used it? Seen and used any other faculty development materials designed for this purpose?</description>
		<content:encoded><![CDATA[<p>MERLOT is working on including some stories, thanks to a FIPSE grant for a project called ELIXR that is just getting underway. </p>
<p>Some years ago I wrote a report on the use of stories for faculty development:<br />
<a href="http://www.tltgroup.org/ProFacDev/video-uses-for-profacdev.html" rel="nofollow">http://www.tltgroup.org/ProFacDev/video-uses-for-profacdev.html</a><br />
A group of us spent a day watching videos and looking at web sites. We concluded, among other things, that we had seen two types of materials, both of which could be classed as stories:<br />
a) stories intended to help the user visualize a way of teaching and become interested in trying it<br />
b) stories intended to give the user, interested in a particular way of teaching, the vicarious experience of getting into trouble so that the reader (usually in a seminar with others) could learn how to identify and analyze that type of problem, and figure out how to deal with it (e.g., how to turn it into a teachable moment).</p>
<p>These kinds of stories, especially &#8220;b&#8221;, are very important for educational uses of technology, but I&#8217;ve seen almost none in use. The University of Victoria in Canada has, I believe, developed a DVD of type &#8220;b&#8221; stories arising from educational uses of technology. The DVD is intended for use in faculty development.  Has anyone seen and used it? Seen and used any other faculty development materials designed for this purpose?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
