| Note | ||
|---|---|---|
| ||
This document describes the mechanics of the database version control process. How the changes get into the master schema must still be decided by the OLE development team. |
| Table of Contents |
|---|
Process Overview
To manage and track database changes, the Kuali OLE project utilizes Subversion to track the master state of the database at any given point in time. The ole-cfg-dbs project in the Subversion repository is considered the definitive source and is stored as a combination of XML (for database structure) and flat files (for data.)
...
Directory | Description |
|---|---|
| Rice KNS and KIM data. (Parameters, Roles, Permissions, etc...) |
| OLE workflow document definitions. |
The non-workflow Rice data scripts use Liquibase for inserting the data into the Rice tables. Most of them (for practical reasons), simply load a CSV file with the OLE data into the needed tables. Review the Liquibase XML files in the ole/work/db/rice-data for the details. They are split up into two sets, demo and bootstrap. Under normal operation, both are executed. Usually, the demo scripts add data not in the bootstrap scripts but in at least one case (system parameters), it overlays the entire set of OLE parameters.
OLEDBA Master Schema
All changes to the base OLE database structure and baseline demonstration data must be done within this schema. The schema is located at:
JDBC URL: | jdbc:oracle:thin:@oracle.ole.kuali.org:1521:XE |
|---|---|
Username: | OLEDBA |
Changes made there will be exported into the ole-cfg-dbs SVN project nightly and used to refresh the OLELOCAL, OLEDEV, and OLECI databases. (as well as any developer satellite instances the next time they run the process)
Document TODO Notes
| Note |
|---|
|