Local Implementations
- Former user (Deleted)
- Former user (Deleted)
- Former user (Deleted)
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 |
||
University of Michigan |
Custom Implementation |
2.4 |
In development |
contact Former user (Deleted) |
|
Stanford |
Synchronizing with CMgt & legacy customizations (Event-based XML document) |
2.4.x |
In production under 2.3.x |
contact Former user (Deleted) |
|
Whitman College |
Custom Implementation (web services) |
2.3.x |
CM API integration not started |
contact Former user (Deleted) |
|
Stockholm University |
Custom implementation of CM API for 2.3 vis-à-vis SIS data replicated to enterprise directory |
2.3.1 |
In production |
contact Former user (Deleted) 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 Former user (Deleted) |
|
UC Davis |
Custom Implementation (Hibernate) |
2.4 |
In QA |
contact Former user (Deleted) |
|
Rutgers |
Custom Implementation (LDAP) |
2.3.1 |
In Production |
contact Former user (Deleted) |
|
Johns Hopkins U |
Custom Implementation (Spring JDBC) |
2.4 |
In devlopment |
contact Former user (Deleted) |
|
Leidse Onderwijsinstellingen |
Custom Implementation (IMS Enterprise webservices) |
2.4.x |
In development |
contact Former user (Deleted) |
|