Laserfiche WebLink
The product that resulted from the activities under this subtask was an updated design that included all <br />data that had been omitted from the Year 1 design. This design was subsequently populated. <br />Subtask 2. Facilitate user involvement. <br />The Phase 2 scope included participation by the database consultant staff in Technical Advisory <br />Committee (TAC) meetings and Technical Subcommittee (TS) meetings. The database consultant staff <br />participated in three TAC meetings and four TS meetings. Involvement at the TAC meetings included <br />preparing part of the presentation to the TAC. Involvement at the TS meetings included preparing a <br />written summary of current progress and current issues. A presentation and demonstration was prepared <br />for each meeting. Copies of the database design documentation were available for inspection at each of <br />these meetings. <br />Subtask 3. Populate the Physical data. <br />The current design of the CRDSS database is found in Section 2.0 of the CRDSS Developers? Manual. <br />The entity relationship diagram and schema found in Section 5.2.2 of the CRDSS Developers? Manual <br />were the starting point for the Phase 2b effort. These materials have been updated to reflect the activities <br />that occurred as part of Phase 2b. The data types that were populated during Phase 2b are listed in <br />Table 1. <br />The schedule of the data population for all the database tasks was driven by the need to keep the water <br />resources planning model task and consumptive use task on schedule as much as possible. The first data <br />populated from the State's dBase files were the structures information to support the population of the <br />diversion records and water rights. As construction and population of the Phase 2 database continued, a <br />number of data issues were encountered that delayed the database tasks. These issues are discussed later. <br />The primary database activities in Phase 2 involved completing the database design, populating the <br />database, and constructing of database displays. Only minor data collection was done. Most of the data <br />in the Physical Characteristics database came from the State in machine-readable form. The State was <br />responsible for a quality assurance task, and the consultant assumed that the State's data were correct as <br />received. However, the consultant did perform quality assurance checks during the loading process. If <br />any data issues were discovered, these issues were returned to the State for resolution. <br />The database was populated according to the procedures outlined in the Section 2.2.3 of the CRDSS <br />Developers? Manual. The procedures briefly consist of receiving the dBase files that have been checked <br />by the State. The consultant then parses the data in these files to the correct format to prepare them for <br />loading into the database. The data are then loaded into a temporary database table prior to being loaded <br />into the database to make sure that the data meet the constraints of the database and to allow <br />manipulation through use of the database system utility programs. Only once the data are checked and <br />accounted for are they loaded into the permanent tables. <br />A number of quality assurance checks are performed before any data becomes part of the CRDSS <br />database. These checks are as follows: <br />? <br />As related tables are populated, the integrity of the relationships among tables is checked. It is <br />important to ensure that the data are associated with correct values used as keys in related tables. <br />2 <br />a320/taskmems/ 2-04-01.doc 01/03/97 <br />