Sakai Enterprise Repository
Right now this is a place to dump working files. More will come. Check the attachments for the latest working files.The Enterprise Repository acts as a central location for data storage and presentation to Sakai. As such, it needs to collect information from a variety of sources, and present that information in a manner amenable to the Sakai provider mechanism.
Requirements
- Support for Varied Data Sourcing: The data being provided to the Enterprise Repository can come from a number of different sources. The Repository must be able to handle most, if not all, sources of data.
- Freshness of Data: In some cases, the data being provided to Sakai must be as close to the current state of the data source as possible.
- Query Execution Speed: Given that the repository generally aggregates data from external sources, the speed by which aggregated data is provided to Sakai must be optimized.
- Synthesis of Heterogeneous Data: In some cases, multiple data sources may contain similar versions of source data. Care must be taken when synthesizing this data for presentation to Sakai.
Achitectural Design
The Enterprise Repository will be hosted on a single database server. This database will, at one end, allow data to be fed into it from various source systems on campus, and at the other end will provide a database schema readable by Sakai, and formatted to be as efficient as possible in the Sakai structure.
Database
An Oracle database will be used for the Repository. Aside from our institutional core competency, Oracle provides a number of useful mechanisms for aggregating enterprise data. In addition, a number of the campus systems providing data, especially the Banner Student Information System, are Oracle instances as well, allowing the maximum flexibility when sourcing data.
Files
| Attachments |
|---|