My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
CRDSS_Task2_05-1_HistoricalDatabaseYear2Summary
CWCB
>
Decision Support Systems
>
DayForward
>
CRDSS_Task2_05-1_HistoricalDatabaseYear2Summary
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/25/2011 10:18:47 AM
Creation date
6/2/2008 11:48:07 AM
Metadata
Fields
Template:
Decision Support Systems
Title
CRDSS Task 2.05-1 - Historical Database - Year 2 Summary
Description
The purpose of this task memorandum is to document the historical database task activities performed during Year 2.
Decision Support - Doc Type
Task Memorandum
Date
1/3/1997
DSS Category
HydroBase
DSS
Colorado River
Basin
Colorado Mainstem
Contract/PO #
C153658, C153727, C153752
Grant Type
Non-Reimbursable
Bill Number
SB92-87, HB93-1273, SB94-029, HB95-1155, SB96-153, HB97-008
Prepared By
Riverside Technology inc.
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
5
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
this penalty is easily offset by the fact that no updates are required to the displays whenever new data is <br />added to the database. <br />Derived tables that are part of the CRDSS (and Hydrobase) design are used to display monthly records. <br />This saves the query and processing overhead to generate these values "on the fly." Part of any data <br />refresh to the time series tables with daily data and monthly derived tables requires that the monthly <br />tables be updated at the same time. <br />The work products for this subtask are the programs that generate the Mosaic displays. <br />Subtask 4. 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 />3.0 CONCLUSIONS AND RECOMMENDATIONS <br />The following recommendations are made for consideration now that the CRDSS databases are basically <br />complete: <br />Continue to coordinate the CRDSS database design with the Hydrobase design. However, <br />? <br />there are different needs between the current CRDSS tasks and the ultimate users of <br />Hydrobase. Discussions need to continue to determine the best way for the two systems to <br />evolve. <br /> <br />As part of the scoping process, decisions need to be made and time needs to be allocated to <br />? <br />update the CRDSS as new data become available. <br /> <br />Once the State actively begins to use the CRDSS database, resources need to be allocated <br />? <br />within the State structure to administer and maintain the database. <br />4 <br />a320/taskmems/ 2-05-01.doc 01/03/97 <br />
The URL can be used to link to this page
Your browser does not support the video tag.