Laserfiche WebLink
Diversion records (recommended refresh every year) <br />? <br /> <br />Climate/environmental (examples: daily_evap, monthly_pcpn) (recommended refresh <br />? <br />every year) <br /> <br />Streamflow (daily_flow) (recommended refresh every year) <br />? <br /> <br />Miscellaneous (low volume data updates to quiet, mostly static tables; examples: reservoir, <br />? <br />station, structure) (recommended refresh as needed) <br /> <br />Irrigated acreage (recommended refresh as needed - probably every 3 to 5 years) <br />? <br />The accompanying flow diagram pictorially depicts the movement of data through the various sub- <br />processes that make up the overall database refresh process. The flow diagram is provided as an aide <br />in visualizing the specific steps described below. <br />Water Rights (examples: wright, wrstatus, wrstatus use) <br />The production water rights database data can be added to but not modified because of the legal <br />nature of the historical data. Therefore, no ?verify? file should be submitted for historical water <br />rights tables. Valid new water rights may be added to the database. Existing water rights may have <br />valid new additional history added to the database. <br />Each incoming record must associate with an existing structure. Further, each subordinate water <br />rights record (wrstatus, wrstatus_use) must be associated with a valid rights record, either in the <br />production database or within the incoming wright data set (in the event of a brand new water right). <br />Each of the incoming data sets will be loaded into a temporary database table, then partitioned in up <br />to three output data sets (also temporary tables within the database). <br />Subset 1-The incoming record meets all of the necessary validation criteria discussed <br />above. The record may be taken as accurate and applied against the database. <br />Subset 2-The incoming record is not associated with an existing structure. To ensure <br />the integrity of the production database, the incoming water rights record must <br />be associated with an existing structure; therefore, this record should be set <br />aside for review by the State?s management team and for checking the record <br />counts. <br />Subset 3-The incoming subordinate water rights data record is not associated with a <br />verified water right. To ensure the integrity of the production database, any <br />incoming wrstatus or wrstatus_use data record must be associated with a <br />wright already in the production database, or must be a part of the incoming <br />water rights data; therefore, this record should be set aside for review by the <br />State?s management team and for checking the record counts. <br />5 <br />a320/taskmems/ 2-13-01.doc 01/03/97 <br />