docs (viz): updating 'data sleuth' activity prompts

mod_data-viz.qmd

@@ -94,12 +94,13 @@ As a project team, discuss the following points:
 
 1. Decide on a structure for tracking results of exploratory data checks
     - Git issues? Additional columns in your team-data-inventory google sheet? Something else?
-    - Make a list of checks you would want to apply to each dataset before inclusion
+    - Draft a list of 'generic checks' you would want to apply to each dataset before inclusion in your synthesis
 2. Use the `summarytools` and/or `datacleanr` packages to explore one exemplar dataset that you intend to include in your project
-    - Discuss any issues you discover 
-    - Revise the list of checks as necessary
-    - Complete pre-harmonization dataset "to do" for the dataset (e.g. remove 1993 due to incomplete sampling, convert concentrations from mmols to mg/L, contact dataset providers to ask about anomalous values in April 2021)
-3. If you choose to save any exploratory images and/or code for reference after running the interactive exploratory checks, decide on a naming convention and storage location
+    - Discuss any issues you discover
+    - Create a "to do" list for the exemplar dataset that details additional steps needed to make that dataset analysis ready (e.g. remove 1993 due to incomplete sampling, convert concentrations from mmols to mg/L, contact dataset providers to ask about anomalous values in April 2021)
+    - Note we will work on skills to **implement** these steps in the [Data Wrangling module](https://lter.github.io/ssecr/mod_wrangle.html) in a few weeks.
+    - Revise the list of 'generic checks' for remaining datasets as necessary
+3. If you choose to save any images and/or code you used in your exploratory data visualization, decide on a naming convention and storage location
     - Will you add these files to your `.gitignore` or do you plan on committing them?
 4. What additional plots would you ideally make that are not available through these generic tools?