Adding to and editing slides

Author: lkrovetz

index.qmd

@@ -82,8 +82,8 @@ Please fill out this  survey:
 if (Sys.getenv("QUALTRICS_API_KEY") != "") {
   data.raw <- fetch_survey(surveyID = QUALTRICS_SURVEY, verbose = TRUE) 
   data <- data.raw |>
-          filter(Status != "Survey Preview") |>
           filter(consent == "Yes") |>
+          filter(Status != "Survey Preview") |>
           filter(StartDate > QUALTRICS_STIME & EndDate < QUALTRICS_ETIME) |>
     # renaming variables
     select(StartDate,EndDate,Status,Finished,RecordedDate,ResponseId,consent,age_1,gender,education,num_tabs_1,name_confidential,number_confidential)

presentation/.ipynb_checkpoints/00-introduction-checkpoint.md

@@ -0,0 +1,5 @@
+## Quick tutorial on preserving survey data
+
+In this presentation we'll show you how to process and preserve survey data. 
+
+We'll use an API to retrieve the data, show you how to clean and strip the data of confidential information and non-consenting responses in order to create a publishable dataset.

presentation/.ipynb_checkpoints/00-introduction1-checkpoint.md

@@ -0,0 +1,3 @@
+## Quick tutorial on preserving survey data
+
+We've created a short survey for demonstration that you can fill out if you want to contribute your own responses. 

presentation/.ipynb_checkpoints/00-introduction2-checkpoint.md

@@ -0,0 +1,5 @@
+## Goals
+- [ ] Create a survey in Qualtrics for data collection.
+- [ ] Load the latest responses from the server using an API token.
+- [ ] Clean and process the data to remove non-consenting responses and any confidential data.
+- [ ] Create and publish usable data that does not reveal any confidential data.

presentation/.ipynb_checkpoints/01-goal-checkpoint.md

@@ -1,3 +1,5 @@
 ## Creating a survey in Qualtrics
 
+You'll typically have access to a Qualtrics account through your university or organization. Then it is easy to construct a survey using the web tool.
+
 ![](images/qualtrics-edit.png)

presentation/.ipynb_checkpoints/01-goals-checkpoint.md

@@ -1,3 +1,5 @@
 ## Survey responses in Qualtrics
 
+Responses can be easily checked at a glance in the `Data and Analytics` tab. You can download data directly from this page, but to make sure you are always using the most up to date data, downloading directly via an API token is a more efficient way to access your data.
+
 ![](images/qualtricsc-data)

presentation/.ipynb_checkpoints/10-creating-survey-checkpoint.md

@@ -1,6 +1,6 @@
-## Loading data from Qualtrics using API
+## Loading data from Qualtrics using an API
 
-In order to always be analyzing the most up to data survey responses, we can load the data directly from the web using a Qualtrics API:
+In order to always be analyzing the most up to date survey responses, load the data directly from the web using a Qualtrics API. Here is some initial set up:
 
 ```{.R}
 # qualtrics URL components
@@ -12,8 +12,4 @@ QUALTRICS_SURVEY <- "second part of survey URL, usually starts with SV"
 QUALTRICS_STIME <- ymd_hms("2025-07-01 00:00:01")
 QUALTRICS_ETIME <- ymd_hms("2025-08-26 23:59:00")
 
-if (!dir.exists(here::here("data"))) {
-  dir.create(here::here("data"))
-}
-
 ```

presentation/.ipynb_checkpoints/11-qualtrics-data-checkpoint.md

@@ -2,12 +2,11 @@
 
 An API token is assigned to your Qualtrics account and is used to request data from a survey. 
 
-The API token is stored as a secret in Github using environmental variables:
+You can set it directly in your R code:
 
-```plaintext
-echo "QUALTRICS_API_KEY=${{ secrets.QUALTRICS_API_KEY }}" >> $GITHUB_ENV
+``` {.R}
+Sys.setenv(QUALTRICS_API_KEY = "your-token")
 ```
+However, this token is your secret token and you don't want this appearing in your published code.
 
-Then, in your publishable R code, you can simply refer to "`QUALTRICS_API_KEY`" in your code so as to not give away your API token. 
-
-Let's see how this works in the next slide:
+We'll revisit in later slides how to fix this issue for sharable code.