<br><br><div class="gmail_quote">On Fri, Jan 16, 2009 at 12:29 PM, Martin Langhoff <span dir="ltr"><<a href="mailto:martin.langhoff@gmail.com">martin.langhoff@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Fri, Jan 16, 2009 at 4:07 PM, Anna <<a href="mailto:aschoolf@gmail.com">aschoolf@gmail.com</a>> wrote:<br>
> Since, at least for now, we're not going to be using moodle in Birmingham<br>
> yet, I renamed<br>
<br>
</div>you break my heart with that, but it's a valid workaround :-)<br>
<div><div></div><div class="Wj3C7c"></div></div></blockquote><div><br>I'm very sorry, Martin, but I hope you understand the reasoning behind the decision. Aside from the teacher training issues regarding content creation and management, we're just not prepared to address the very serious potential for disciplinary issues surrounding the current login authentication method. The current moodle scenario might work within a small, trusting environment, but when I'm looking at schools with between 100-600 students, there's no way we can keep kids from making mischief via other logins, either accidentally or intentionally.<br>
<br>I just don't want the electronic version of a kid writing "teacher is a dummy" on the blackboard, and the current moodle configuration allows the troublemaker to do so under another kid's name. Or delete each other's homework or any number of pranks we've yet to imagine.<br>
<br>Don't get me wrong - I think Moodle is a very exciting project, and I'm looking forward to implementing it in the future, but not right now. That's why I had to find a workaround to host web content in the traditional fashion.<br>
<br>Anna Schoolfield<br>Birmingham<br></div></div>