...
- No direct integration
- Banner provides a synthesized view of data to Middleware
- THRCSDB - person registrary info
- SWVITSI - courses and instructors
- SWVITRG - students and the courses they are in
- Middleware further processes the data against the person registry
- Web services API is used to provision Sakai
- Three custom java applications are used for this provisioning
- sakai_load_users - creates the main sakai account for each user. Does not assign the user to any sites.
- sakai_load_courses - creates all of the new course sites in Sakai. This is the process that assigns the Sakai site ID for the course.
- sakai_load_students - adds/removes the students from each of the courses that they are assigned to
- for more information please see Rice-Sakai-Atlanta.ppt
The Sakai Web Service API routines that we use are:
...
- We are not using Course Management API.. Course Management API did not exist when we started using Sakai in 2006.
----
| Note |
|---|
Salah DamiAssistant |
| Note |
|---|
Juan Estrada |
| Note |
|---|
Arios Jules, Network Engineer and Jabed Abutaher, Programmer |
Sakai Provisioning Code
I've put together a subversion repository with the code we use to provision courses, instructors, and students into Sakai.
The repository can be found via a web browser at
| Code Block |
|---|
https://www.it.svn.rice.edu/
|
You will need to authenticate using your guest account. Look for the repository named Middleware_Public.
The repository can be accessed with a subversion client using the following URL:
| Code Block |
|---|
https://it.svn.rice.edu/r/Middleware_Public/
|