Laserfiche WebLink
A number of issues arose as the consultant attempted to populate these data. The main issues are <br />outlined below: <br />? <br />Missing or incomplete identifiers (wd and id) <br /> <br />? <br />Records with duplicate identifiers where either the rest of the record information is the same or <br />different <br /> <br />? <br />Missing, incomplete, or obviously incorrect location information <br /> <br />? <br />Improper data entry <br /> <br />? <br />Improperly filled diversion records as received from the State. <br />These issues affect how the database is loaded and whether or not each data item can be correctly <br />associated with other data items as specified in the design. There were a number of other issues <br />regarding whether or not other information associated with structures information in particular appeared <br />to be correct (i.e., - Is the value of a given diversion amount correct?). In most cases, the consultant had <br />no way of knowing whether or not this information was correct and loaded these data as received. As <br />discussed above, the CRDSS data were spot checked against the original source. In cases where data <br />appeared to be incorrect or questionable, those records were passed back to the State's management team <br />representative responsible for resolving data issues and were not loaded in the database. No data records <br />were changed unless the consultant was expressly instructed to do so by the State's management team. <br />Once documentation was received from the State that the original records were acceptable or the <br />corrected records were received, these data were loaded into the database. <br />The product of this subtask is a populated historical database. The present data types and record contents <br />are found in Table 1. <br />Subtask 2. Facilitate user involvement. <br />The Phase 2 scope included participation by the database consultant staff in TAC meetings and TS <br />meetings. The database consultant staff participated in three TAC meetings and four TS meetings. <br />Involvement at the TAC meetings included preparing part of the presentation to the TAC. Involvement <br />at the TS meetings included preparing a written summary of current progress and current issues. A <br />presentation and demonstration was prepared for each meeting. Copies of the database design <br />documentation were available for inspection at each of these meetings. <br />Subtask 3. Develop Mosaic-based interfaces. <br />Historical time series data interfaces were developed using Mosaic, INFORMIX SQL scripts, <br />INFORMIX eSQL for C, and C. These interfaces display all the historical data types used. Details of <br />the software developed for this activity are found in Section 2.2.1 of the CRDSS Developers? Manual . <br />The interfaces developed for this task all use "live" queries of the database. What this means is that the <br />programs that generate the displays query the data for the current data in the database instead of <br />displaying a static file with the display data in it. The static files are generated at the time the programs <br />are written and are not part of the database. There is a small performance penalty for this approach, but <br />3 <br />a320/taskmems/ 2-05-01.doc 01/03/97 <br />