|
<br />RTi will check the number of stations and period of record populated in this task to that
<br />in the existing CRDSS database, Discrepancies, other than the anticipated extension of
<br />time series data to present (approximately 1995), will be identified by RTi. If
<br />discrepancies are caused by the loading process, they will be resolved by RTi, If
<br />discrepancies are not related to the loading process, RTi will document why they occur.
<br />
<br />RTi will document the results of this task for inclusion as a new section in the Developers
<br />ManuaL
<br />
<br />Deliverables
<br />RTi will provide:
<br />L A populated HB - CRDSS database with all the Non DWR data currently in the
<br />CRDSS database,
<br />2, All routines, programs, and/or scripts used to perform the data population, These
<br />routines should be sufficient for an experienced database administrator to replicate the
<br />conversion, beginning with source 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, Ajixed log of all records that were fixed,
<br />5, A draft section of the Developers Manual which describes the population of HB -
<br />CRDSS database with Non - DWR data, This section, which may be called NON -
<br />DWR Data Population, is expected to contain approximately 10 pages of text and will
<br />include the results of the relationship and constraint checking, the population
<br />verification, the 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 R6 - Revise CRDSS Software.
<br />
<br />Approach
<br />Software to be revised in this Task falls into two categories, I) Existing low-level DMI
<br />routines, and 2) DMI Utilities, All low-level DMI routines use embedded SQL that
<br />perform selects on the database, These routines are coded in .ec files that are translated to
<br />C by the compiler and are then put into a DMllibrary,
<br />
<br />DMI Utilities call the low-level routines in standard C fashion, Ideally, only the low-
<br />level routines will need to be modified because the interfaces to the utilities are governed
<br />by functionality, not data storage, However, in some cases, the functionality of a DMI
<br />Utility may need to be revised because of a change in database structure, For example,
<br />additional data items may need to be passed to a DMI Utility or a DMI Utility may be
<br />able to take advantage of a derived table,
<br />
<br />Scope of Wark, HB - CRDSS, 1/30/97
<br />
<br />0871
<br />
<br />8
<br />
|