I just want to add to Bryan's email about our plans for the school
server in Nepal, and how we might wanna manage content so that it is
easier for kids to use the XO with the server.<br><br>On Moodle:<br>> <br>> I am just thinking out loud. These might be really bad ideas.<br>
> <br>> 1. Authentication : Can we use a client side script to secure autologin so that<br>> kids dont have to remember login info. The login should take kids to<br>> whatever (predefined) course they are enrolled in. No front page, no<br>
> selecting etc. This login info should be tied to the XO.? How big a<br>> concern is security ? <br>> <br>> 2. Really simplify the UI. Use feature like Chat, Workshop, Database<br>> and maybe assignments and thats it. More modules, more confusing it<br>
> is. <br>> <br>> 3. Create groups and separate them and make other groups invisible,<br>> and tie each user to whatever group they fall under. Like grade 2 will<br>> only view Group 2 and work within it.<br>
> <br>> 4. Question: How do we let students save their documents in the server<br>> (not as a part of moodle, but something done outside moodle)? Something that is tied to the journal would be perfect. Can<br>> moodle handle something like this? Some sort of archiving that will<br>
> let students easily save and retrieve files? I guess we should be able<br>> to write a custom web page to do this and access it from within<br>> moodle.<br>Maybe even a Puttyssh or ssh with a GUI ?<br>> <br>
> let me know what you guys think.<br>> best,<br>> -Sulochan<br>