Laserfiche WebLink
Tables with fields used as keys are checked for null and duplicate records so that <br />searches and sorts done on these fields will yield efficient and unambiguous <br />results. <br />The results of table loading are checked for errors and for records that did not <br />load so problems can be resolved. <br />Once the data are loaded into the final tables, the data are spot- checked against <br />the original source of the data to ensure that the values are correct and are <br />associated with the correct identifiers. Note that one objective of the database <br />population activities is to make sure that the data are traceable to the original <br />source. <br />In the case of the water rights data, the water rights reports were checked <br />against those generated previously by the State from dBase. A sample from each <br />division was carefully checked to make sure that the records matched exactly. <br />Some differences were allowed. One allowable set of differences was the result <br />when a newer data set was used to populate the CRDSS database than the one <br />that was used to generate the report; the other allowable set of differences was <br />formatting differences that resulted from how the CRDSS database stored the <br />status codes. <br />The consultant team built the water rights structure as discussed at the end of <br />Year 1. Once the structure had been populated, many problems became <br />apparent when an attempt was made to generate the net absolute decrees and <br />match the standard reports generated by the State. The water rights tables were <br />redesigned and repopulated several times until it was possible to match records <br />in the original reports or understand exactly how the reports generated by the <br />CRDSS database were different. The following list is a summary of the issues <br />encountered during the database construction and population effort: <br />• Missing or incomplete identifiers (wd and id) <br />• Records with duplicate identifiers where either the rest of the record <br />information is the same or different <br />• Missing, incomplete, or obviously incorrect location information <br />• Improper data entry <br />• Improperly coded water rights data as received from the State <br />• Incomplete water rights data files as received from the State (The files did <br />not contain all original data in the dBase files that would allow original <br />reports to be duplicated) <br />• Water rights which had no associated structure (An underlying assumption <br />of the design is that all water rights are associated with structures. <br />These issues affect how the database is loaded and whether or not each data <br />item can be correctly associated with other data items as specified in the design. <br />There were a number of other issues regarding whether or not other information <br />associated with structures information in particular appeared to be correct (i.e., - <br />