Laserfiche WebLink
CRDSS <br />TASK MEMORANDUM 2.05-1 <br />Historical Database <br />Year 2 Summary <br />1.0 ISSUE <br />The purpose of this task memorandum is to document the historical database task activities performed <br />during Year 2. <br />2.0 DISCUSSION/ANALYSIS <br />The primary focus of the database effort was to create a populated database to support the modeling <br />efforts. During Phase I, the database design was formulated, and construction of the database began. <br />Beginning in Phase II, the database design was refined, and database construction and population <br />continued. As part of this effort, database utility programs were created to partially automate the <br />population process and to make administration of the database easier. Once this important database <br />creation and population phase produced a workable and populated structure, data management interface <br />(DMI) libraries were built to allow access to the database. Character-based displays were built using the <br />INFORMIX tools as a prototyping tool, debugging tool, and a tool to verify database contents. Also, <br />other displays were built to prototype other ways of viewing the time series data and to test different <br />ways to access the database. Comments from potential users were collected through the user <br />involvement process, and this user input was used to improve the database and displays as part of Phase <br />IIb. The Mosaic based database interfaces now part of the system are the result of this process. <br />The progress on the historical database task is summarized first by a brief discussion of the scope of <br />work. Then, important parts of the work plan will be discussed, particularly where products were <br />produced that were not discussed in the work products section. <br />Subtask 1. Review historical data and populate the database. <br />The entity relationship diagram and schema found in Section 5.2 of the CRDSS Developers? Manual <br />were used as the starting points for the database development in Year 2. <br />The CRDSS database design was derived directly from the Hydrobase design. The consultant was <br />directed to build a database that supported the CRDSS effort and followed the Hydrobase design as <br />closely as possible in the context of the CRDSS effort. However, the consultant was not directed to build <br />Hydrobase. The CRDSS database contains many data types not found in the Hydrobase design, and the <br />Hydrobase design also contains many data types not needed for CRDSS, which were not included in the <br />CRDSS database. The State does plan at some point to build the Hydrobase design, so the consultant <br />tried to make the CRDSS database compatible with the Hydrobase design as much as practical. The <br />compatibility was limited by the schedule and funding available to the consultant to resolve design and <br />data issues. <br />1 <br />a320/taskmems/ 2-05-01.doc 01/03/97 <br />