Laserfiche WebLink
CRDSS database contains many data types not found in the Hydrobase design, <br />and the Hydrobase design also contains many data types not needed for <br />CRDSS, which were not included in the CRDSS database. The State does plan <br />at some point to build the Hydrobase design, so the consultant tried to make the <br />CRDSS database compatible with the Hydrobase design as much as practical. <br />The compatibility was limited by the schedule and funding available to the <br />consultant to resolve design and data issues. <br />To help maintain consistency with the State's Hydrobase design and to make <br />migration to the design easier, the consultant was asked to include all the State's <br />data found in the original dBase files directly associated with the data included in <br />the CRDSS database. <br />As the Year 2 project proceeded, a memorandum was written (to Ross Bethel <br />and Will Burt from Doug Greer and Larry Brazil, March 29, 1996) describing <br />differences in the designs at the entity level for both Hydrobase and the CRDSS <br />database. The design used in the Phase 2b project is essentially the design <br />delivered to the State at the end of Phase 2a with minor changes. <br />The activities under this subtask included completing the database design and <br />populating the database. The State's management team was instrumental in <br />designing the table structure that was ultimately found to be workable for the <br />CRDSS. All the data in the water rights database came from the State in <br />machine - readable form. The State was responsible for a quality assurance task, <br />and the consultant assumed that the State's data were correct as received. <br />However, the consultant did perform quality assurance checks during the loading <br />process. If any data issues were discovered, these issues were returned to the <br />State for resolution. <br />The database was populated according to the procedures outlined in Section <br />2.2.3 of the CRDSS Developers' Manual. The procedures briefly consist of <br />receiving the dBase files that have been checked by the State. The consultant <br />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 <br />table prior to being loaded into the database to make sure that all the data meet <br />the constraints of the database and to allow manipulation through use of the <br />database system utility programs. Only once the data are checked and all data <br />records are accounted for are the records loaded into the permanent tables. A <br />number of quality assurance checks are performed before any data becomes <br />part of the CRDSS database. These checks are outlined below: <br />As related tables are populated, the integrity of the relationships among tables is <br />checked. It is important to ensure that the data are associated with correct values <br />used as keys in related tables. <br />