Laserfiche WebLink
<br />Ut:.l..-l~-l':;l':;b l:..1::: .;:..d <br /> <br />01lJ '..lJRTl:.R Rc.;:;UU~LI::.~ <br /> <br />2)1l.:. l:::lbb .,j;)i:5:t i.t:JO....l.'t <br /> <br />the constraints and indexing strategy for each cable. The SQL scripts available from <br />ERWIN in the development of Exhibit 1 will be used as a starting point, but will need to <br />be modified to include any indexing strategy necessary for the c=ot CRDSS utility <br />programs. The SQL scripts used to create the CRDSS specific tables (station data, ell <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 Dew section in the Developers <br />Manual. <br /> <br />Deliverable <br />RTi will: <br />1. Provide a draft section of the Developers Manual which describes the HB _ CRDSS <br />database construction. nus section, which may be called Database Creation, is <br />expected to be approximately 1.2 pages in lenl!th. <br />2. Incorporate State comments. <br />3. Provide a f1J1a1 sectiou ofrhe Developers Manual in the following fonnats: one hard <br />copy, one version in Microsoft Word, one version included in the existing on line <br />(HTML) Developers Manual. <br /> <br />Task R4 - Populate lIB - CRDSS with DWR data. <br /> <br />Approach <br />In tllis Task, RTi will populate all the HB - CRDSS database tables (Exhibit I) with data <br />available from the D:R~TheSe files are expected to contain information up to irrigation <br />j'ear 1995) (tD{311 . <br />/'(<; <br />:. 'I; <br />~ RTi \~iJl design the da1abase population to nm as automatically as possible so that <br />Once the database is built, deleting and Ie-building the database can be perforni.~ easily <br />....ith revised or new data sets. This approach is defIned herein as a . delete and re-build'. i ~ <br /> <br />Procedures RTi "'111 develop scripts and/or utilities to prepare the data to be load into /JJ.J- <br />- CRDSS. These scripts and/or utilities may include data manipulation using Dbase,:1 (~ C"l.-- <br />UNIX level routines and temporary/working tables within the database.-E"hanges to the loo/!..~" ~ <br />relationships, constraints, and keys may be made during the oonversion, to ease the e. ,~rfo , <br />population of tables. However the final production database schema must reflect the ~ ~', <br />relationships presemed in Exhibit 1. E1. ~ ~,~ , <br /> <br />Integratin~ Derived Water Riahts. RTi v.ill integrate the data for the three Derived Wata -k> .Sf. ~r<1 \ <br />Rights tables called Transactions, Net Amounts, and Aug"" "'T. The State wiil provide 0. <:.to fo <br />these tables to the RTi in a stand-alone fashion. (Meaning that they are not directly ~. ~1>.....; I <br />related to any other table in rhe HB, - CRDSS database.) It is RTi's responsibility to use c-. ~.v_~. \ll'\ I <br />the Alternate Keys defined in Exhibit I (WD+ID), to build a relationship between the ~......., ""'-t.. W;. <br />main StruCture table by back filling the foreign key (structure_ num). 1-0" ~ /' <br /> <br />,,-------- <br /> <br />[;/ \,11-1... <br />U.k' <br />5 <br /> <br />1, <br />\, <br />A <br />r}~ <br /> <br />\~ <br /> <br />$cop. or WO"', HB - CRDSS, 121101% <br /> <br />0943 <br />