juliasilge
commented
2 years ago That sounds pretty frustrating @tbritton44! For us to figure out what is going on, can I get you and/or your research assistant to create a reprex (a minimal reproducible example) for this? The goal of a reprex is to make it easier for us to recreate your problem so that we can understand it and/or fix it. I wonder if this is related to version of R or other packages, so please the session info with session_info = TRUE.
If you've never heard of a reprex before, you may want to start with the tidyverse.org help page. You may already have reprex installed (it comes with the tidyverse package), but if not you can install it with:
install.packages("reprex")Your output (what you paste here on GitHub) should look like this, but with your info (feel free to censor any PII that shows up by replacing with XXX or similar):
library(qualtRics)
my_survey <- fetch_survey("SV_3gbwq8aJgqPwQDP", force_request = TRUE)
#> | | | 0% | |======================================================================| 100%
#>
#> ── Column specification ────────────────────────────────────────────────────────
#> cols(
#> .default = col_character(),
#> StartDate = col_datetime(format = ""),
#> EndDate = col_datetime(format = ""),
#> Progress = col_double(),
#> `Duration (in seconds)` = col_double(),
#> Finished = col_logical(),
#> RecordedDate = col_datetime(format = ""),
#> RecipientLastName = col_logical(),
#> RecipientFirstName = col_logical(),
#> RecipientEmail = col_logical(),
#> ExternalReference = col_logical(),
#> LocationLatitude = col_double(),
#> LocationLongitude = col_double(),
#> SolutionRevision = col_double()
#> )
#> ℹ Use `spec()` for the full column specifications.
#> 'StartDate', 'EndDate', and 'RecordedDate' were converted without a specific timezone
#> * To set a timezone, visit https://www.qualtrics.com/support/survey-platform/managing-your-account/
#> * Timezone information is under 'User Settings'
#> * See https://api.qualtrics.com/instructions/docs/Instructions/dates-and-times.md for more
names(my_survey)
#> [1] "StartDate" "EndDate" "Status"
#> [4] "IPAddress" "Progress" "Duration (in seconds)"
#> [7] "Finished" "RecordedDate" "ResponseId"
#> [10] "RecipientLastName" "RecipientFirstName" "RecipientEmail"
#> [13] "ExternalReference" "LocationLatitude" "LocationLongitude"
#> [16] "DistributionChannel" "UserLanguage" "Q63"
#> [19] "Q16" "Q17" "Q18"
#> [22] "Q19" "Q22" "SolutionRevision"Created on 2022-01-20 by the reprex package (v2.0.1)
tbritton44
aek501
Hi all,
Hoping to crowdsource an issue I am having lately with the qualtRics package. I am a HUGE fan and want to extend a lot of gratitude to the community members who have developed and maintained it.
A research assistant is helping me regularly process some survey data we have coming in daily. The data cleaning script I have written pulls the data directly from Qualtrics using the qualtRics package, then runs a series of code that transforms/cleans variables so I have a nice tidy output.
She has been assisting me with this for the better part of a year, but recently got a new laptop. Upon getting that new laptop, when she runs the script the variable names pulled from Qualtrics are incorrect, and so the script throws an error when asked to manipulate a certain variable for example:
pan_dat_new <- pan_dat_new %>% mutate(inconsistent_choice_girl = case_when( choose2_1 == "On" ~ 1, choose2_2 == "On" ~ 2, TRUE ~ as.numeric(NA)))
Error : ...x object 'choose2_1' not found
When I go to explore variable names, what I notice is that there has been a long string of numbers added to each variable name, and I am guessing this is something that is happening in the process of the interface between Qualtrics and R prior to the survey data "magically" existing as a dataframe in R.
Wondering if others have had this same experience and if they have found a resolution? Or if you have any insights as to what else could be going on? I have had her uninstall and reinstall qulatRics, to no avail.
Thanks in advance for any support you can offer!