Difference between revisions of "Sakai"
Absentminded (talk | contribs) |
Absentminded (talk | contribs) |
||
| Line 4: | Line 4: | ||
[[CUIT]] plans on using the Sakai platform to integrate the course directory, [[SSOL]], couseworks, and the bulletin into one site. They expect this to talk at least 5 years. The fact that by the time they implement an already old technology in 5 years will mean that Columbia will be close to a decade late in implementing technology around since 2002 has apparently been lost on everyone. | [[CUIT]] plans on using the Sakai platform to integrate the course directory, [[SSOL]], couseworks, and the bulletin into one site. They expect this to talk at least 5 years. The fact that by the time they implement an already old technology in 5 years will mean that Columbia will be close to a decade late in implementing technology around since 2002 has apparently been lost on everyone. | ||
| + | |||
| + | The [[Agora]] project was basically killed when it was decided to wait and see what Sakai will offer, whenever it's implemented. | ||
Revision as of 23:29, 29 March 2007
Sakai is an open source platform that Columbia intends to use in it's replacement for Courseworks.
Josh Hirschland somehow manages to mention it in every column he wrote for almost 2 years.
CUIT plans on using the Sakai platform to integrate the course directory, SSOL, couseworks, and the bulletin into one site. They expect this to talk at least 5 years. The fact that by the time they implement an already old technology in 5 years will mean that Columbia will be close to a decade late in implementing technology around since 2002 has apparently been lost on everyone.
The Agora project was basically killed when it was decided to wait and see what Sakai will offer, whenever it's implemented.
