This page lists the (known) local implementations of the CourseManagement APIs. There are two typical approaches to implementing CM:
- Synchronizing implementations - these populate the CM reference implementation from an external system via quartz jobs or other synchronization tasks
- Custom CM Implementations - these implement the API from the ground up, making use of local datasources other than the sakai database.
| Organization | CM Approach | Sakai version | Status | Code and/or Examples | CM Service Coverage |
|---|---|---|---|---|---|
| UC Berkeley | Custom Implementation (Spring JDBC) | 2.4 | In production | contrib snapshot | See Coverage -- UC Berkeley |
| University of Michigan | Custom Implementation | 2.4 | In development | contact Zhen Qian | |
| Stanford | Synchronizing with CMgt & legacy customizations (Event-based XML document) | 2.4.x | In production under 2.3.x | contact casey dunn | |
| Whitman College | Custom Implementation (web services) | 2.3.x | CM API integration not started | contact Mike Osterman | |
| Stockholm University | Custom implementation of CM API for 2.3 vis-à-vis SIS data replicated to enterprise directory | 2.3.1 | In production | contact Per Wising code available at svn://anonsvn.it.su.se/su-groups/ | |
| The University of the Arts |
Synchronizing our Sakai with an external Datasource |
2.3.x |
In Planning |
contact Duran Goodyear |
|
| UC Davis | Custom Implementation (Hibernate) | 2.4 | In QA | contact Jon Gorrono https://source.sakaiproject.org/contrib/ucd/cm-ucd-impl/ |
See Coverage -- UC Davis |
| Rutgers | Custom Implementation (LDAP) | 2.3.1 | In Production | contact Jason Shao | |
| Johns Hopkins U | Custom Implementation (Spring JDBC) | 2.4 | In devlopment | contact Elliot Metsger | Coverage - Johns Hopkins U |
| Leidse Onderwijsinstellingen | Custom Implementation (IMS Enterprise webservices) | 2.4.x | In development | contact Mark Breuker |
