Laserfiche WebLink
<br />ut:.......-.l~ .L:;>:;;H;l ~.-,.._~~ <br /> <br />.!J J l,I J.JH I l::.K KC:,UI_I;-;:\..l::.::::l <br /> <br />.JCJ~ ODO ",),,)0:' <br /> <br />I .u...........,. <br /> <br />Testing. As tables are populated, R Ii will verify the integrity of the relationships among <br />the tables, and the conversion of data into the tables. TI,e results of the table population <br />will be checked for errors and for records that that did not load. Data that does Dot 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 are <br />associated with the correct key identifiers. <br /> <br />Error Handling. RTi is not responsible for correcting bad data. Whenever bad data is <br />encountered, an error log will be submitted to the State. If these data are corrected and <br />delivered to R Ii 4 weeks prior to tbe end oftbis (',ontmet, RTi will re-convert the records <br />for t11at particular Water Distrkt. If there are minor changes that are made by RTi after <br />approval by tbe State, a fixed log will be provided to the State. <br /> <br />RTi ",ill document tbe results of this task for inc.lusioll as a new section in the Developers <br />Manual. <br /> <br />Deliverables <br />RTi will pro\ide; <br />I. A populated HE . CRDSS database with DWR data. This includes DWR's irrigated <br />aCteage, histone streamflow, streams, strlSCtures (headgates, reservoirs, small dams, <br />jurisdictional dams). diversions (daily, monthly, =U3l. time series), diversion <br />comments. and derived water rights (transactions, net amounts, a.ug_ wr). <br />2. All routines, programs, and/or scripts used to perfonn the population. These routines <br />should be sufficient for 311 experienced database administrator to redo the conversion; <br />beginning with source (typically Dbase) files and ending with a populated InformilC " <br />database. 'The objective is to allow the conversion to be reproduced in a "delete and' <br />re-build" fashion. . , <br />3. Provide a draft section of the Developers Manual which describes the HB - CRDSS ' <br />population of DWR data. This section, which may be called Population ofDWR, '. <br />data, is expected to be approximately 15 pages in length. It will include the results of <br />the relationship and constraint checking, the population verification, the accounting of <br />records, and the spot-checks. <br />4. Incorporate State comments. <br />5. PrOvide a final section oflhe Developers Manual in the follov"ing formats: one hard <br />copy, one version in Microsoft Word, one version included in the existing on line <br />(HTML) Developers Manual. <br />6. An error lag of ail records that could not be loaded. <br />7. Aped log of all records that were tiKed. <br /> <br />SIlO,," of Work. HB . CROSS, 12/ I 0196 <br /> <br />\j~I\~ <br /> <br />6 <br />