I had seen Moodle before (2003), through searches about Open Source, Open Access, and "Open Knowledge Initiative" in learning contexts. ![]() Curt Bonk also has interesting things to say about Sakai, though people may have taken some of his comments the hard way. I also enjoyed discussions about the project from members of IU's Sakai team. I didn't have that much of an occasion to put it to thorough testing, but I quite enjoyed Sakai from what I could see. I've used Sakai as a (full-time) visiting lecturer at IU South Bend ('04-'05) and as a graduate student at IU Bloomington (using Sakai occasionally). Especially since it's quite possible that I wasn't clear. There's still a number of reasons for me to prefer Moodle over Sakai, but I would still advise administrators to give Sakai a try to see if it's compatible with learners' needs for the context in which they operate.Īs someone who did talk about the two projects, I actually wonder how my impressions have been taken. I would also say that support for Sakai has been pretty efficient, at least at the time I started using Oncourse CL. In fact, project members have been quite explicit about the mission of Sakai outside academic environments. So, it's a nice platform for the kind of formal teamwork expected in corporate environments. It's also pretty clean in terms of announcements and assignments. It has WebDAV support and allows uploaders to add details about copyright and such. I personally find it more flexible for filemanagement in general, including sharing documents. One strength of Sakai, IMHO, is the workspace/worksite focus. So, in that sense, it's a bit less bazaar and a bit more cathedral than what ESR described, ten years ago. Contrary to the typical FLOSS project, Sakai isn't really meant to be played with by individual software developers. They had a special type of license as partners in the project. At the same time, several key institutions were already investing money (and time) in the project. ![]() He was describing the development process as more open than typical Open Source (because licenses are less restrictive). A key participant in the project gave an IU-wide presentation on Sakai back in 2005. ![]() Like Steve describes it, development on Sakai is pretty formal. IU has been using Sakai (as " Oncourse CL") as a replacement for their previous IIS-based Oncourse and their "locker" filemanager as well as for project management. Put simply, Sakai is a bit more like a Drupal-like CMS well-adapted for courses while Moodle was mostly built for learning. It's different in design and both platforms have strengths. I've been using Sakai informally since 2005.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |