The CHaMP Data Management System is currently designed to support the data collection, processing and product generation. Current efforts are now focusing on improving product exposure and availability to interested parties, including CHaMP participants, analysts, and interested managers.
From 2011-2013 CHaMP focused most of the Data Management efforts on streamlining data collection, processing, and metric generation. This included mechanisms to electronically capture and perform quality assurance checks while in the field, post-process data
Data Flow
Spring 2013: Data Collection switched from Juniper Data Loggers to iPad technology
Summer 2015: Documentation of the existing data management strategy summarizing the CHaMP Data Management System. Crews begin use of Issue Tracking System (JIRA)
Winter 2015: Hydraulic model and Habitat Suitability model engines retired from champmonitoring.org and run in Amazon Web Services environment
Summer 2016: Proposal to Modularize the CHaMP Data Management System to simplify the management and curation of CHaMP data.
Fall 2016: Transition of RBT engines from champmonitoring.org begins and RBT engines are manually triggered in a non-champmonitoring.org server environment (SFR).
Summer 2017: Update of Data Management Plan, Modularization Effort wrap up, including retirement of laptop Data Broker and RBT engines. Laptop Data Broker was replaced by the Field Data Upload Utility and the RBT engine was replaced with the Topographic Metric scripts.