...

1. 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)
2. Only the Rice DBA and appropriate client application migrators have access to the tags directory in the repositories.
3. 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
   borderStyle solid title Example:DataSetDriver.sql
   @DataSet1.sql @DataSet2.sql

Data Set Migration Process

1. A migrator files a ticket in the Kuali Rice JIRA project requesting migration of a data set to the Rice database.
2. 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
3. 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.
4. The Rice Service Manager creates a ticket in the Kuali Rice JIRA project that reflects this task and assigns it to the Rice DBA.
5. The Rice DBA pulls the data set down from the respository.

   Code Block
   borderStyle solid title Example:Checking Out Data Set from Repository
   https://svn.ucdavis.edu/svn/kuali/RiceApplications/KualiCoeus/trunk/datasets https://svn.ucdavis.edu/svn/kuali/RiceApplications/KualiCoeus/tags/2.0