UC Davis Data Provisioning

Sakai, when deployed in a University setting, must rely on external sources of data to satisfy a number of informational needs. These needs include:

• Course Information
• Registration Information
• Identity Information
• Role and Membership Information

Data provisioning in Sakai can occur using one of two methods: direct loading of data into the internal Sakai database, or loading of data from an external data repository via a provider mechanism. We have chosen to follow the second approach.

Additionally, Sakai stores and displays rich content as one of its primary functions. In order to provide a robust system for making content available across multiple application servers, as well as provide backup and failover, we will be storing content for Sakai in AFS.

Requirements for Data Provisioning using Providers and Batch Processes

Sakai Providers

The Sakai Providers will handle provisioning data into Sakai when user, affiliation, course information is requested. The providers, including the UCDavisUserDirectoryProvider, UCDavisGroupProvider, and UCDavisCourseManagementProvider will supply data to Sakai in order for Sakai to create sites, users, and roles dynamically.

Sakai External Database

The Sakai External Database will be the central location for all data to be provisioned to Sakai. As such, it will collect data from systems around Campus and present it to Sakai in a format amenable to the Sakai provider structure.

Sakai Data Storage

Given that Sakai will be run as a clustered service, content created in or uploaded to Sakai must be stored in a location accessible by all servers. We will be using AFS for this storage.