Laserfiche WebLink
<br />.. <br /> <br />the constraints and indexing strategy for each table, The SQL scripts available from <br />ERWIN in the development of Exhibit I will be used as a starting point, but will need to <br />be modified to include any indexing strategy necessary for the current CRDSS utility <br />programs, The SQL scripts used to create the CRDSS specific tables (station data, cu <br />model, etc,) may be modified and used to build HB - CRDSS <br /> <br />RTi will document the results of this task for inclusion as a new section in the Developers <br />11anual. ~ <br /> <br />Deliverable <br />RTi will: <br />I, Provide a draft section of the Developers 11anual which describes the HB - CRDSS <br />database construction, This section, which may be called Database Creation, is <br />expected to be approximately 1-2 pages in length, <br />2, Incorporate State comments, <br />3, Provide a final section of the Developers 11anual in the following formats: one hard <br />copy, one version in 11icrosoft Word, one version included in the existing on line <br />(HT11L) Developers 11anual. <br /> <br />l' <br /> <br />Task R4 - Populate HB - CRDSS with DWR data. <br /> <br />Approach <br />In this Task, RTi will populate all the HB - CRDSS database tables (Exhibit I) with data <br />available from the DWR, These files are expected to contain information up to irrigation <br />year 1995 (10/31/1995), <br /> <br />Goals, RTi will design the database population to run as automatically as possible so that <br />once the database is built, deleting and re-building the database can be performed easily <br />with revised or new data sets, This approach is defined herein as a 'delete and re-build', <br /> <br />Procedures, RTi will develop scripts and/or utilities to prepare the data to be load into HB <br />- CRDSS, These scripts and/or utilities may include data manipulation using Dbase, <br />operating system routines and temporary/working tables within the database, Changes to <br />the relationships, constraints, and keys may be made during the conversion, to ease the <br />population of tables, However the final production database schema must reflect the <br />relationships presented in Exhibit 1. Note, reference tables such as which water districts <br />are in which division or which county is associated with a county ID are included in the <br />HB-CRDSS database design, Exhibit 1. <br /> <br />Integrating Derived Water Rights, RTi will integrate the data for the three Derived Water <br />Rights tables called Transactions, Net Amounts, and Aug_ wr. The State will provide <br />these tables to the RTi in a stand-alone fashion, (11eaning that they are not directly <br />related to any other table in the HB - CRDSS database,) It is RTi's responsibility to use <br />the Alternate Keys defined in Exhibit I (WD+ID), to build a relationship between the <br />main Structure table by back filling the foreign key (structure_num), <br /> <br />0919 <br /> <br />Scope of Work, HB - CRDSS, 12/20/96 <br /> <br />5 <br />