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 />Records with duplicate identifiers where either the rest of the record information is the same or <br />different <br />? <br />Missing, incomplete, or obviously incorrect location information <br />? <br />Improper data entry <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 structure capacity 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 generally passed back to the State's <br />management team representative responsible for resolving data issues and were not loaded in the <br />database. No data records were changed unless the consultant was expressly instructed to do so by the <br />State's management team. Once documentation was received from the State that the original records <br />were acceptable or the corrected records were received, these data were loaded into the database. <br />Subtask 4. Complete the development of physical characteristics Mosaic data viewing interfaces. <br />Physical characteristics data interfaces were developed using Mosaic, INFORMIX SQL scripts, <br />INFORMIX eSQL for C, and C. These interfaces display all the physical characteristics data types used. <br />Details of the software developed for this activity are found in Section 2.2.1 of the CRDSS Developers? <br />Manual . <br />Subtask 5. Coordinate physical characteristics database activities with the consumptive use task. <br />As the CU modeling task proceeded, structural changes to the database were necessary to support this <br />task. Minor amounts of additional data were added that were not originally anticipated when the scope <br />of work was written. Note that this activity continued for the duration of Phase 2. The purpose of this <br />subtask was to provide the physical characteristics database support needed by the CU task. Any <br />changes that are the result of this subtask are reflected in the tables below and in the design materials <br />found in the CRDSS Developers? Manual <br />Subtask 6. Prepare a task memorandum. <br />This subtask involves the preparation of a memorandum and the database documentation. The <br />documentation includes appropriate sections in the CRDSS Users? Manual and the CRDSS Developers? <br />Manual. <br />4 <br />a320/taskmems/ 2-04-01.doc 01/03/97 <br />