<p> Enterprise GIS Dataset Stewardship</p><p>Archiving & Maintenance Plan</p><p>Dataset: Bulletin 118 Groundwater Basin Boundaries</p><p>Primary Steward: Brett Wyckoff</p><p>Primary Steward Division/Office/Program: DIRWM/RPB/ Conjunctive Water Management</p><p>Description of archiving and maintenance plan:</p><p>- The dataset is updated by the following procedure:</p><p> o A request is made to modify a basin boundary or related attribute data within the dataset. This request could come from groundwater agencies operating within the basin, or from DWR staff. Superficial corrections, such as fixing typographical errors within the dataset can be processed immediately. Modifications to the dataset related to the basin boundaries or attributes must follow a public process because the existing dataset was finalized within a public process. The public vetting process is not included here, but would be the last step before actual substantial edits to the data are completed. What follows is the process leading up to public vetting, and subsequent completion of the geodatabase edits.</p><p> o Regional office staff will evaluate the proposed request, including the technical merits. If staff does not agree with the proposal, they will report to the requesting entity with the reasons why. If they concur with the changes, they will initiate the public vetting process.</p><p> o After successful public vetting of the data changes, the proposed changes will be provided to the B-118 Groundwater Basin Boundaries dataset sub-steward for the applicable region office. The region office sub-steward will notify the HQ data steward, who will work with the sub-steward in transmitting the changes to the geodatabase manager, and making any necessary updates to the metadata, lineage, or versioning. The CASGEM Program must be notified to changes to the dataset, as the CASGEM Online System uses the groundwater basin data in its application and GIS viewer.</p><p>- Types and frequency of data updates </p><p>Not very frequent - Estimated annual cost for dataset maintenance</p><p>Unkown</p><p>- Frequency of re-certifying data meet standards, including positional accuracy</p><p>Once every two years</p><p>- Criteria for determining if EGC needs to be involved in evaluating maintenance or standard compliance</p><p>TBD</p><p>- Metadata update plan</p><p>Metadata is updated when changes to the dataset are made. It is the responsibility of the steward and sub-stewards to ensure that the appropriate updates to the metadata are made.</p><p>- Is there a requirement for archiving? </p><p>The old version of the dataset should be archived whenever an update is completed.</p><p>- Frequency of archiving</p><p>Not anticipated to be very frequent because of the public vetting process that goes along with substantial changes to the dataset</p><p>- Naming conventions on archiving?</p><p>Naming conventions will be an incremental numbering system, such as Basins_4.1, Basins_4.2, Basins_5.0, etc.</p><p>- What portions of dataset need to be archived?</p><p>The entire old dataset will be archived when an update occurs.</p>