I'm diving into Sakai project with intention to evaluate it as Learning Management System for my University.
Description from original web site:
It's mature and well supported platform, targeted for large institutions. It uses some parts of J2EE technology with light approach. It's built on Spring framework and can work on Tomcat server.
Probably there will be need to customize some parts of platform to conform local requirements, so I have to check architecture and enchantment possibilities.
Description from original web site:
"Sakai is a set of software tools designed to help instructors, researchers and students create websites on the web. For coursework, Sakai provides features to supplement and enhance teaching and learning. For collaboration, Sakai has tools to help organize communication and collaborative work on campus and around the world."
It's mature and well supported platform, targeted for large institutions. It uses some parts of J2EE technology with light approach. It's built on Spring framework and can work on Tomcat server.
Probably there will be need to customize some parts of platform to conform local requirements, so I have to check architecture and enchantment possibilities.
IT Pro Life
3 comments:
How's the Sakai evaluation implementation goin?
Sakai is really promising and meeting expectations of University I'm working for. The core features are ok, but some of University requirements are so specific that Sakai will need some customization. I've checked system architecture and it looks reasonable. A couple of java programmers and graphic designer will do the job. I'm waiting for start of deployment of the new elearning project.
I'd be interested in hearing what local requirements you're looking at. In addition to the selfish interest of working for an organization that provides service & support around Sakai, I've been very interested in identifying common local needs and better defining extension points in the central codebase.
Post a Comment