<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.5" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Bodington Review, Part I</title>
	<link>http://mfeldstein.com/bodington_review_part_i/</link>
	<description>What Michael Feldstein Is Learning About Online Learning...Online</description>
	<pubDate>Thu, 21 Aug 2008 05:41:09 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.5</generator>

	<item>
		<title>by: Paul Trafford</title>
		<link>http://mfeldstein.com/bodington_review_part_i/#comment-568</link>
		<pubDate>Thu, 26 Oct 2006 19:08:16 +0000</pubDate>
		<guid>http://mfeldstein.com/bodington_review_part_i/#comment-568</guid>
					<description>&lt;p&gt;Dave,&lt;/p&gt;

&lt;p&gt;The permission model was designed with the user in mind from the beginning - I think it was in '96 when Jon Maber developed the first discussion board-type tool (now called the &lt;em&gt;Group Communication Room&lt;/em&gt; ) for student support where there was limited face-to-face contact.  They needed to restrict access to particular groups of users etc.  I understand he tried Hypermail and some CGI scripts, but they didn't provide what he needed, so he developed his own Web application tools in Java, which would have included the interface for setting permissions.  I don't know how similar it was to what we have now in Bodington, though.
&lt;/p&gt;

&lt;p&gt;You can hear Jon mention the early days in Chuck Severance's &lt;a href="http://www.youtube.com/watch?v=JSd3HnJh6tQ"&gt;video on Jon Maber&lt;/a&gt;, available from Youtube.
&lt;/p&gt;

&lt;p&gt;You can see the interface in an &lt;a href="http://www.weblearn.ox.ac.uk/site/info/docs/about/accessrights/"&gt;overview of access rights&lt;/a&gt; (especially sections 5 and 6) that we provide at Oxford.  If you're happy installing Web apps, then you can see how it works by downloading a Quickstart .war file from &lt;a href="http://sourceforge.net/project/showfiles.php?group_id=87659"&gt;Bodington's area in SourceForge.Net&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;- Paul&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Dave,</p>
<p>The permission model was designed with the user in mind from the beginning - I think it was in &#8216;96 when Jon Maber developed the first discussion board-type tool (now called the <em>Group Communication Room</em> ) for student support where there was limited face-to-face contact.  They needed to restrict access to particular groups of users etc.  I understand he tried Hypermail and some CGI scripts, but they didn&#8217;t provide what he needed, so he developed his own Web application tools in Java, which would have included the interface for setting permissions.  I don&#8217;t know how similar it was to what we have now in Bodington, though.
</p>
<p>You can hear Jon mention the early days in Chuck Severance&#8217;s <a href="http://www.youtube.com/watch?v=JSd3HnJh6tQ">video on Jon Maber</a>, available from Youtube.
</p>
<p>You can see the interface in an <a href="http://www.weblearn.ox.ac.uk/site/info/docs/about/accessrights/">overview of access rights</a> (especially sections 5 and 6) that we provide at Oxford.  If you&#8217;re happy installing Web apps, then you can see how it works by downloading a Quickstart .war file from <a href="http://sourceforge.net/project/showfiles.php?group_id=87659">Bodington&#8217;s area in SourceForge.Net</a></p>
<p>- Paul</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Dave Bauer</title>
		<link>http://mfeldstein.com/bodington_review_part_i/#comment-565</link>
		<pubDate>Mon, 23 Oct 2006 04:00:11 +0000</pubDate>
		<guid>http://mfeldstein.com/bodington_review_part_i/#comment-565</guid>
					<description>Michael this sounds great, I'd love to see how it is integrated into the user interface. Of course, .LRN/OpenACS has an infinitely flexible permissions model, but getting that power to users is always the trick.</description>
		<content:encoded><![CDATA[<p>Michael this sounds great, I&#8217;d love to see how it is integrated into the user interface. Of course, .LRN/OpenACS has an infinitely flexible permissions model, but getting that power to users is always the trick.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.199 seconds -->
