<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: The joys of teaching students about RSS</title>
	<atom:link href="http://drbadgr.wordpress.com/2008/10/13/teaching-students-about-rss/feed/" rel="self" type="application/rss+xml" />
	<link>http://drbadgr.wordpress.com/2008/10/13/teaching-students-about-rss/</link>
	<description>Trying to think aloud online</description>
	<lastBuildDate>Fri, 18 Dec 2009 18:09:35 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: ajcann</title>
		<link>http://drbadgr.wordpress.com/2008/10/13/teaching-students-about-rss/#comment-67</link>
		<dc:creator>ajcann</dc:creator>
		<pubDate>Tue, 14 Oct 2008 08:50:31 +0000</pubDate>
		<guid isPermaLink="false">http://drbadgr.wordpress.com/?p=62#comment-67</guid>
		<description>Timetable limitations and student numbers prevent f2f peer-assessment for this exercise. I&#039;m in the process of radical simplification (e.g. removing references to peer-review), but my biggest concern is now how to give them feedback. The Bb gradebook makes this as difficult as possible, but is also the wrong solution. I&#039;m in favour of separating feedback from assessment (which we do in this assessment by delaying the marks until the end of term), but feedback needs to be located inline with the assessment tool - we already have lots of data showing that students will not visit an alternative destination (e.g. the Bb gradebook) and so will never see the feedback. This is a limitation of the Google reader shared items architecture - there&#039;s not way to add a comment to  a shared item. Solution?</description>
		<content:encoded><![CDATA[<p>Timetable limitations and student numbers prevent f2f peer-assessment for this exercise. I&#8217;m in the process of radical simplification (e.g. removing references to peer-review), but my biggest concern is now how to give them feedback. The Bb gradebook makes this as difficult as possible, but is also the wrong solution. I&#8217;m in favour of separating feedback from assessment (which we do in this assessment by delaying the marks until the end of term), but feedback needs to be located inline with the assessment tool &#8211; we already have lots of data showing that students will not visit an alternative destination (e.g. the Bb gradebook) and so will never see the feedback. This is a limitation of the Google reader shared items architecture &#8211; there&#8217;s not way to add a comment to  a shared item. Solution?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jobadge</title>
		<link>http://drbadgr.wordpress.com/2008/10/13/teaching-students-about-rss/#comment-66</link>
		<dc:creator>jobadge</dc:creator>
		<pubDate>Tue, 14 Oct 2008 08:38:32 +0000</pubDate>
		<guid isPermaLink="false">http://drbadgr.wordpress.com/?p=62#comment-66</guid>
		<description>Thanks Moira - yes, we are looking at peer review (using either Bb 8 or turnitin) for next year. I like the idea and agree that showing them each others feeds and shared items is a great way to build community. We have got them to add their shared GR URLs to a wiki on Bb, so they can look at each other&#039;s already. We wanted to make the sharing a continuous exercise over 7 weeks, to try and embed some habits of reading, tagging and sharing information regularly. Perhaps the peer assessment should happen at the end of the period?

Unfortunately our biggest computing room holds 80 students, so we would have to have three sessions just to cover this....</description>
		<content:encoded><![CDATA[<p>Thanks Moira &#8211; yes, we are looking at peer review (using either Bb 8 or turnitin) for next year. I like the idea and agree that showing them each others feeds and shared items is a great way to build community. We have got them to add their shared GR URLs to a wiki on Bb, so they can look at each other&#8217;s already. We wanted to make the sharing a continuous exercise over 7 weeks, to try and embed some habits of reading, tagging and sharing information regularly. Perhaps the peer assessment should happen at the end of the period?</p>
<p>Unfortunately our biggest computing room holds 80 students, so we would have to have three sessions just to cover this&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Moira</title>
		<link>http://drbadgr.wordpress.com/2008/10/13/teaching-students-about-rss/#comment-65</link>
		<dc:creator>Moira</dc:creator>
		<pubDate>Tue, 14 Oct 2008 08:29:18 +0000</pubDate>
		<guid isPermaLink="false">http://drbadgr.wordpress.com/?p=62#comment-65</guid>
		<description>Assessment ideas

1. Peer assessment, altogether in a computer lab. Each person must assess the Google Reader page of x others with marks and comments.

2. In small group tutorials - each person demos and talks about their Google Reader page for 2-3 minutes + questions. Marked by the tutor (+/- peers). Could get through 10 in a session?

In either case there would be lots of possibilities for cross fertilisation of ideas, though they would be in the students&#039; heads rather than in their browsers.</description>
		<content:encoded><![CDATA[<p>Assessment ideas</p>
<p>1. Peer assessment, altogether in a computer lab. Each person must assess the Google Reader page of x others with marks and comments.</p>
<p>2. In small group tutorials &#8211; each person demos and talks about their Google Reader page for 2-3 minutes + questions. Marked by the tutor (+/- peers). Could get through 10 in a session?</p>
<p>In either case there would be lots of possibilities for cross fertilisation of ideas, though they would be in the students&#8217; heads rather than in their browsers.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
