Major outcomes from L1 feedback meeting 2023-11-29

[bpbond]

• Significant preference for units as part of research_name (e.g. soil_vwc_10cm_degC). Roy and Ben both groan :) but many find this a lot easier! At that point I might vote just to restore the units column
• Have L1 data include basic visualizations for all variables Write basic data viz plot for each L1 data file #61
• Include OOB limit values in metadata Add out-of-bounds values to L1 metadata #62
• How to handle out-of-service events recorded by techs?
• BBL and SP to work towards design_link tables for all sites Add all synoptic sites to design table #63 Add new test data, from all sites; fix design table mistakes #68
• Want a mechanism to handle the issue of e.g. sapflux sensor being shifted to a new tree after original dies -- basically need a valid_through column in design link table and code to handle that Multiple design_link handling  #60
• RR gave good example of hierarchical flag: fluctuating voltage flag should cascade to inform all sensors on that datalogger

[bpbond]

Hierarchy examples

• Fluctuating voltage flag should cascade to inform all sensors on that datalogger
• Bad voltage on a troll informs all sensors on it
• Does a bad TEROS temperature reading informs VWC and EC on same probe? That would be trickier

[bpbond]

Hierarchy. With the addition of a single parent column in the design_link table, we can do something like this:

This visualizes how a flag on the solar battery voltage would flow (propagate) to the sapflow, TEROS, and AquaTroll sensors.