<?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>Kommentare zu: Students, Security, Prosuming and Social-Software</title>
	<atom:link href="http://andreasauwaerter.de/blogline/2009/07/25/students-security-prosuming-and-social-software/feed/" rel="self" type="application/rss+xml" />
	<link>http://andreasauwaerter.de/blogline/2009/07/25/students-security-prosuming-and-social-software/</link>
	<description>Podcasting unter der pädagogischen Lupe</description>
	<lastBuildDate>Fri, 15 May 2020 05:17:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=4.2.39</generator>
	<item>
		<title>Von: Pat Parslow</title>
		<link>http://andreasauwaerter.de/blogline/2009/07/25/students-security-prosuming-and-social-software/comment-page-1/#comment-191</link>
		<dc:creator><![CDATA[Pat Parslow]]></dc:creator>
		<pubDate>Sun, 26 Jul 2009 15:04:26 +0000</pubDate>
		<guid isPermaLink="false">http://userpages.uni-koblenz.de/~dkauwaer/blogline/?p=835#comment-191</guid>
		<description><![CDATA[I think the best practice is probably to encourage learners to do two things:

1) keep multiple copies of things they produce, so that if a 3rd party app, or an institutional server, becomes unavailable to them, they can still access their materials.

2) keep an &#039;index&#039; of material they produce.  If they can do this and include a reflection on what the material means to them, and what it provides as evidence about their learning or skills, then that is even better.

The reflections kept in step 2) above should be dynamic, I think, in that the learners should probably update them in the light of experience they gain later.

In this way, it should be practical to maintain pointers to all the work they have done - and if the institution needs to access those materials, all they really need is a list of the learners&#039; index pages (which could be on an institutional server, or, better, on a couple of 3rd party applications which the user can continue to access after they have left the institution)]]></description>
		<content:encoded><![CDATA[<p>I think the best practice is probably to encourage learners to do two things:</p>
<p>1) keep multiple copies of things they produce, so that if a 3rd party app, or an institutional server, becomes unavailable to them, they can still access their materials.</p>
<p>2) keep an &#8218;index&#8216; of material they produce.  If they can do this and include a reflection on what the material means to them, and what it provides as evidence about their learning or skills, then that is even better.</p>
<p>The reflections kept in step 2) above should be dynamic, I think, in that the learners should probably update them in the light of experience they gain later.</p>
<p>In this way, it should be practical to maintain pointers to all the work they have done &#8211; and if the institution needs to access those materials, all they really need is a list of the learners&#8216; index pages (which could be on an institutional server, or, better, on a couple of 3rd party applications which the user can continue to access after they have left the institution)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
