form fiss 2023 QA workflow

[lucy-schick]

Documenting how we QA the form fiss 2023 so others can understand the process. Hoping we can use this to update onboarding or https://github.com/NewGraphEnvironment/fish_passage_template_reporting at some point. This is based off my understanding while QA the data so please correct anything that is wrong.

While in the field, crews collected data on both the digital field forms and the fiss site cards, so it's okay if there are some data on the fiss site cards that aren't in the form, and vice versa.

The following changes were done to the skeena 2023 form fiss data and issues were not created for these changes because it happened very frequently. If an issue was created for other edits, then these changes were mentioned in the issue, see example here https://github.com/NewGraphEnvironment/fish_passage_skeena_2023_reporting/issues/78

• Certain data are collected at only one ef site but need to be transferred to all other ef sites within the greater site. For example, temperature, ph, conductivity, and turbidity were only collected at 8525_ds_ef1 but this data will be used for all other 8525_ds and 8525_us sites. When QAing data in Q, we will copy temperature, ph, conductivity, and turbidity from 8525_ds_ef1 to all other 8525 sites. Sometimes crews will collect this data at one us site and one ds site, then we will copy this data to all us and ds sites respectively. The following data is often only collected at one site:
  • Temperature
  • pH
  • Conductivity
  • turbidity
  • stage

In the future we should script the above process using tidyr::fill() function. https://tidyr.tidyverse.org/reference/fill.html

[lucy-schick]

• [x] Need to change dates once in R because we are having the same issue as here https://github.com/NewGraphEnvironment/fish_passage_skeena_2023_reporting/issues/49