Data Set Locations
Data sets which are to be migrated into the Rice Database are stored in the following Subversion repositories:
Application |
Repository Root |
---|---|
Rice Standalone Server |
https://svn.ucdavis.edu/svn/kuali/RiceStandaloneServer/rice-db/ |
MyInfoVault |
https://svn.ucdavis.edu/svn/kuali/RiceApplications/MyInfoVault/ |
Kuali Financial System |
https://svn.ucdavis.edu/svn/kuali/RiceApplications/KualiFinancialSystem/ |
Kuali COEUS |
https://svn.ucdavis.edu/svn/kuali/RiceApplications/KualiCoeus/ |
UCD Time Reporting System |
https://svn.ucdavis.edu/svn/kuali/RiceApplications/TimeReportingSystem/ |
Data Set Management Requirements
- Release versions of data sets must be stored in
<Repository Root/tags/<client release version>
(e.g. https://svn.ucdavis.edu/svn/kuali/RiceApplications/MyInfoVault/tags/3.5) - Only the Rice DBA and appropriate client application migrators have access to the
tags
directory in the repositories. - The data sets must come in the form of SQL scripts.
Example:DataSet1.sql
INSERT INTO KRIM_COUNTRY_T... INSERT INTO KRIM_CAMPUS_T...
Example:DataSetDriver.sql@DataSet1.sql @DataSet2.sql
Data Set Migration Process
- A migrator files a ticket in the Kuali Rice JIRA project requesting migration of a data set to the Rice database. The JIRA ticket should provide a link to the SVN location of the data files.
- Upon approval, the migrator copies the data set to the
<Repository Root/tags/<client release version>
directory, citing the Kuali Rice JIRA ticket.Example:Migrating to <tags>svn copy https://svn.ucdavis.edu/svn/kuali/RiceApplications/KualiCoeus/trunk/datasets https://svn.ucdavis.edu/svn/kuali/RiceApplications/KualiCoeus/tags/2.0 -m "<KR JIRA ticket>"
- Prior to a release, the migrator adds a task (or requests that a task be added) in the Deployment Plan stating that the data set is to be migrated.
- The Rice Service Manager creates a ticket in the Kuali Rice JIRA project that reflects this task and assigns it to the Rice DBA.
- The Rice DBA checks the data set out from the repository.
Example:Checking Out Data Set from Repository
$ svn co https://svn.ucdavis.edu/svn/kuali/RiceApplications/KualiCoeus/trunk/datasets https://svn.ucdavis.edu/svn/kuali/RiceApplications/KualiCoeus/tags/2.0 or [subversionFiles/dataSets/KualiCoeus/]$ svn update
- During a dry-run deployment, the Rice DBA executes the data set scripts against the UPSTAGE environment database.
- At deployment time, the Rice DBA executes the data set scripts against the production database.