Processing table would be one row per transduce file
unique ID to link to readings table (or locationid + datetime); Diane strongly prefers unique ID
drift parameters or NA if not estimated
quality measure
status approved vs. preliminary; at minimum approved should go through a few QA/QC routines and manual inspection of a graph; if some bad manual measurements at end, likely should wait until better manual measurements at end before making approved
process person ID
process used (maybe software version or something?)
Can create a new function to generate this info, using the drift_info table that comes out of logger loader, which already has drift and quality estimates. Could add unique ID to both row and readings data as part of Drifting function and then add in status, process personn ID and process used as part of a function
Processing table would be one row per transduce file
Can create a new function to generate this info, using the drift_info table that comes out of logger loader, which already has drift and quality estimates. Could add unique ID to both row and readings data as part of Drifting function and then add in status, process personn ID and process used as part of a function