...
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
...
- master schema from Rice project
- OLE Data Overlay
- Liquibase
- Workflow
...
Demo vs. Bootstrap Datasets
All of the Kuali projects have the concept of a development dataset (hence the ole-cfg-dbs/development path), a demo dataset, and a bootstrap dataset. In most cases, the development and demo datasets are the same. The main difference between these is the removal of Kuali environment-specific URLs or email addresses.
The bootstrap dataset is pared back even further, with almost all the non-essential data elements removed, leaving the database empty and ready for import of institutional data.
Starting versions of these scripts (from the KFS project) can be found here:
ole/work/db/ole-demo.sqlole/work/db/ole-bootstrap.sql
These scripts would be run during the creation of the distribution and then their results re-exported into the ole-cfg-dbs SVN project for inclusion in the release. These scripts do not affect the Rice data. For that, the appropriate data files under ole/work/db/rice-data must be modified.