|
<br />will be checked for errors and for records that that did not load, Data that does not load
<br />will be inspected by RTi and reported to the State, RTi will account for all data during
<br />the loading sequence by insuring the same number of records contained in the Dbase file
<br />equal the number populated in HB - CRDSS or returned for checking, RTi will spot-
<br />check against the original data source (Dbase) to ensure that the values are correct and ared. b.a.
<br />associated with the correct key identifiers, ~ ,~ ~
<br />
<br />Error Handling, R Ti is not responsible for correcting bad data, Whenever bad data is \>l :\(~
<br />encountered, an error log will be submitted to the State, If these data are corrected and . # (\'1 \
<br />delivered to RTi 4 weeks prior to the end of this contract, RTi will re-convert the records Jfl,;>rtiI' /' ' \J,..
<br />for that particular Water District. If there are minor changes that are made by R Ti after q , ~ t'\
<br />approval by the State, afixed log will be provided to the State, 110 ~\
<br />I
<br />~\,f
<br />
<br />RTi will document the results of this task for inclusion as a new section in the Developers
<br />Manual.
<br />
<br />De/iverables
<br />RTi will provide:
<br />1. A populated HB - CRDSS database with DWR data, This includes DWR's
<br />streamflow, irrigated acreage, stream, structures (headgates, reservoirs, small dams,
<br />jurisdictional dams), diversions (daily, monthly, annual time series), diversion
<br />comments, and derived water rights (transactions, net amounts, aug_ wr),
<br />2, All routines, programs, and/or scripts used to perform the population, These routines
<br />should be sufficient for an experienced database administrator to redo the conversion,
<br />beginning with source (typically Dbase) files and ending with a populated Informix
<br />database, The objective is to allow the conversion to be reproduced in a "delete and
<br />re-build" fashion,
<br />3, An error log of all records that could not be loaded,
<br />4, Afixed log of all records that were fixed,
<br />5, A draft section of the Developers Manual which describes the population ofHB -
<br />CRDSS database with DWR data, This section, which may be called DWR Data
<br />Population, is expected to contain approximately 10 pages of text and will include the
<br />results of the relationship and constraint checking, the population verification, the
<br />accounting ofrecords, and the spot-checks,
<br />6. Incorporate State comments,
<br />7, Provide a final section of the Developers Manual in the following formats: one hard
<br />copy, one version in Microsoft Word, one version included in the existing on line
<br />(HTML) Developers Manual.
<br />
<br />Task R5 - Populate and Refresh Non DWR Data.
<br />
<br />Approach
<br />In this Task, RTi will populate all the HB - CRDSS database tables (Exhibit I) with data
<br />not obtained from the DWR. Time series files to be populated in this task are expected to
<br />
<br />Scope of Work, HB - CRDSS, ]2/11/96
<br />
<br />0930
<br />
<br />6
<br />
|