Laserfiche WebLink
Is the value of a given decreed amount correct ?). In most cases, the consultant <br />had no way of knowing whether or not this information was correct and loaded <br />these data as received. As discussed above, the CRDSS data were spot <br />checked against the original source and, in the case of the water rights, existing <br />tabulation reports. In all cases where data appeared to be incorrect or <br />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 <br />database. The consultant did not change any data records unless expressly <br />instructed to do so by the State's management team. Once documentation was <br />received from the State that the original records were acceptable or the corrected <br />records were received, these data were loaded into the database. <br />The product of this subtask is a populated water rights database. <br />Subtask 3. Facilitate user involvement. <br />The Phase 2 scope included participation by the database consultant staff in <br />Technical Advisory Committee (TAC) meetings and Technical Subcommittee <br />(TS) meetings. The database consultant staff participated in three TAC meetings <br />and four TS meetings. Involvement at the TAC meetings included preparing part <br />of the presentation. Involvement at the TS meetings included preparing a written <br />summary of current progress and current issues. A presentation and <br />demonstration was prepared for each meeting. Copies of the database design <br />documentation were available for inspection at each of these meetings. <br />Subtask 4. Develop Mosaic -based interfaces. <br />Water rights data interfaces were developed using Mosaic, INFORMIX SQL <br />scripts, INFORMIX eSQL for C, and C. These interfaces display the water rights <br />data in formats that are similar to the report formats generated by the dBase <br />system. Details of the software developed for this activity are found in Section <br />2.2.5 of the CRDSS Developers' Manual. <br />The interfaces developed for this task all use "live" queries of the database. What <br />this means is that the programs that generate the displays query the data for the <br />current data in the database instead of displaying a static file with the display <br />data in it. The static files are generated at the time the programs are written and <br />are not part of the database. There is a small performance penalty for this <br />approach, but this penalty is easily offset by the fact that no updates are required <br />to the displays whenever new data is added to the database. <br />Derived tables that are part of the CRDSS (and Hydrobase) design are used to <br />display the tabulation report. This saves the query and processing overhead to <br />generate these net absolute values "on the fly" and allows use of the database <br />engine to accomplish the various sorts necessary for these displays. Part of any <br />data refresh to the water rights tables requires that the tabulation table be <br />updated at the same time. <br />The work products for this subtask are the programs that generate the Mosaic <br />displays. <br />