...
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/ |
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.
Code Block borderStyle solid title Example:DataSet1.sql INSERT INTO KRIM_COUNTRY_T... INSERT INTO KRIM_CAMPUS_T...
Code Block | ||||
---|---|---|---|---|
| ||||
@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.
- Upon approval, the migrator copies the data set to the
<Repository Root/tags/<client release version>
directory, citing the Kuali Rice JIRA ticket.Code Block borderStyle solid title 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>"
- The Rice DBA will pull