Page History

...

• 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.

----

...

I've put together a subversion repository with the code we use to provision courses, instructors, and students into Sakai.

If any of you would like to get access to this code, I need you to create a guest account here at Rice.

Please visit: *http://guest.rice.edu/*^{Image Removed}

Click on "Apply for a new account" on the upper left corner of the page.

For Sponsor's Email use: dlane@rice.edu

I'll approve your account and then give you access to the repository.

Once your guest account has been created and permission have been setup:

The repository can be found via a web browser at

...