Laserfiche WebLink
Subset 4-Change diversion records that are not present in the ?verify? file. <br />The records in this table would be intended to change existing diversion data <br />in the database. However, there would be no matching record present in the <br />?verify? file to confirm this change record. <br />Climate/Environmental, Streamflow, Miscellaneous <br />The remaining areas of the CRDSS database may use the same general guidelines for data to be <br />refreshed. Validated new data will be inserted into the database. Changes to existing database data <br />will be allowed only after the records containing the changes are validated against a secondary <br />?verify? file (when the source of the data is the State). <br />Each incoming ?refresh? data set may be accompanied by a secondary ?verify? data set that will <br />contain only matching records that are to be applied as ?changes? to the production database. The <br />presence of the ?verify? file will help to separate ?change? data pertinent to the refresh process from <br />other data items that are not to be used. Each incoming data set may contain much more than the <br />actual data that is to refresh the database. There may be non-applicable historical data interwoven <br />with the ?refresh year? data. There may be data that references stations/structures that are outside the <br />scope of the CRDSS project (i.e., stations outside the state of Colorado). <br />The overall goals of the verification exercise are as follows: <br />Produce a table of validated new data that are to be inserted into the database <br />? <br />Produce a table of validated changes to be applied against existing historical data (optional) <br />? <br />Produce a table of data that do not match any existing keys in the production table <br />? <br />Produce a table of change data that do not match any records in the ?verify? table (optional) <br />? <br />The incoming ?refresh? data will be loaded into a temporary database table. If present, the ?verify? <br />data will also be loaded into a temporary database table. <br />The data administration staff will have prepared a set of SQL scripts that use the various rules and <br />constraints of the CRDSS database. The process of verifying the incoming data consists of running <br />these stored SQL scripts within the INFORMIX DB-Access environment against the contents of each <br />temporary table. <br />As the result of this script activity, the table containing the ?refresh? data will be partitioned in up to <br />four output data subsets (also temporary tables within the database): <br />Subset 1-New records that can be inserted into the database. <br />Records in this category would be instances of the top-level entity in the <br />database (geoloc), or a new instance of an intermediate entity that has minimal <br />dependencies within the database (e.g., station, structure, and irrig_acre all <br />depend only on the existence of a geoloc record). <br />Subset 2-Change records that may or may not be applied against previously recorded <br />production data. <br />7 <br />a320/taskmems/ 2-13-01.doc 01/03/97 <br />