<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0cm;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
span.EmailStyle17
        {mso-style-type:personal-compose;
        font-family:"Calibri","sans-serif";
        color:windowtext;}
.MsoChpDefault
        {mso-style-type:export-only;}
@page Section1
        {size:612.0pt 792.0pt;
        margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
        {page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-NZ link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal>Hi,<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I would like to understand the vision for content management
on the server using Moodle. <o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Up to this point (with version 0.4), we have been using browsable
folders of HTML content (including expanded SCORMs with customised index files,
for instance from the Wikieducator’s IMS package export utility), and
also PDF material. Both work fine. HTML is more flexible and easier to port –
PDF material needs reformatting for the XO,to make it more readable.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I am fairly familiar with Moodle as we have one in our DLCP
project <a href="http://www.schoolnet.net.sb">www.schoolnet.net.sb</a> but the
focus is on “courses” not “content” so I was wondering
how this fits with the OLPC content vision, collections and the rest.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>On another minor point, I want to provide the option to go
to browsable folders or moodle on first acess to the school server. So far I
have done this by editing the who.php file and adding a link “click to
browse folders”. But maybe I am missing something that can be better
managed by Moodle.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I would also like to see a collaboration platform (we used
the JoinNet Home Meeting one with DLCP, using National Sun Yat Sen University
of Taiwan’s CCC LMS server). That would combine video chat with sharing a
whiteboard, with ability to post slides, annotate them etc.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Also, an offline wiki on the server would be useful. <o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Any ideas would be appreciated.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><b><i>David Leeming<o:p></o:p></i></b></p>
<p class=MsoNormal><i>OLPC Coordinator, Secretariat of the Pacific Community
(SPC) www.spc.int<o:p></o:p></i></p>
<p class=MsoNormal><i>Technical Advisor, People First Network<o:p></o:p></i></p>
<p class=MsoNormal><i>P.O. Box 652, Honiara, Solomon Islands, South Pacific<o:p></o:p></i></p>
<p class=MsoNormal><i>Tel: +677 76396(m) 24419(h) 26358 (o-PFnet) <o:p></o:p></i></p>
<p class=MsoNormal><i>http://wikieducator.org/User:Leeming <o:p></o:p></i></p>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>