My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
CRDSS_Task2_13-1_StrategyUpdatingCRDSSRelationalDatabaseData
CWCB
>
Decision Support Systems
>
DayForward
>
CRDSS_Task2_13-1_StrategyUpdatingCRDSSRelationalDatabaseData
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/25/2011 10:18:47 AM
Creation date
6/2/2008 12:06:44 PM
Metadata
Fields
Template:
Decision Support Systems
Title
CRDSS Task 2.13-1 - System Maintenance - Strategy for Updating CRDSS Relational Database Data
Description
This memorandum discusses the strategy to be used for updating CRDSS relational database data.
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.
/
11
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
CRDSS <br />TASK MEMORANDUM 2.13-1 <br />System Maintenance <br />Strategy for Updating CRDSS Relational Database Data <br />1.0 ISSUE <br />This memorandum discusses the strategy to be used for updating CRDSS relational database data. <br />2.0 DISCUSSION/ANALYSIS <br />Premise <br />The accuracy and integrity of the existing CRDSS database data must be maintained. New data from <br />outside sources (e.g., U.S. Geological Survey (USGS), National Climatic Data Center) and inside <br />sources (e.g., State Engineer?s Office) must be shown to possess the same level of accuracy before <br />being eligible as input to the database. <br />Assumptions <br />At the Division Office Level <br />The State will construct, debug, implement, and maintain basic data validation executable routines <br />that will be used by the Division offices. The purpose of these routines will be to validate field-level <br />observation data with the same kind of data integrity rules and constraints that are defined for the <br />CRDSS production database. The production database is the version of the database that is available <br />for use and can be trusted as valid by end users; however, changes to the database can still be made. <br />The process of creating data validation routines is not a trivial one, regardless of the level of data <br />accuracy enforcement. The overall complexity of the system is expanded by new modules that must <br />be maintained. The developers of these modules will be required to have a solid understanding of <br />the CRDSS database structure and all of the underlying relationships. However, there are significant <br />gains that can be realized if the modules are implemented and used correctly: <br />Raw data entry errors can be eliminated before they ever leave the field or Division level <br />? <br />office (e.g., text values in a numeric-only field). <br /> <br />Data in question can be returned in a timely manner for review and correction to the field <br />? <br />technician responsible. With each iteration of data entry and correction comes greater <br />understanding of the data requirements. <br />At the CRDSS Database Environment Level <br />The INFORMIX database engine was designed to help the database administration staff maintain the <br />integrity and accuracy of the database contents. Skills required to make effective use of the <br />INFORMIX toolkit include an understanding of the following: <br />1 <br />a320/taskmems/ 2-13-01.doc 01/03/97 <br />
The URL can be used to link to this page
Your browser does not support the video tag.