Closed josephholler closed 1 year ago
The API is pretty handy. I pushed some code to get it working in this commit: 623fbde78b94e12f14f728568fdda59cdf001953 in 00-qualtRics.R
We'd make our lives easier by either customizing the question names or question labels in Qualtrics to something more meaningful than Q1 .. Q10a, etc, but also easy and unique.
My API worked for most functions except for pulling the data from this survey. I think that may be because the survey primarily lives in the Arizona instance of Qualtrics, as I had no problem creating a fake survey & data on my Middlebury acct and downloading it.
this API is really helpful because it allows us to import data as it was originally designed (e.g. as ordered factors for ordinal responses) and allows us to query metadata & create a data dictionary that is much more readable (and usable in R) than the json QSF file.
I've updated the code base to pull the survey data using the API. I did not add question labels to the reproducibility survey, however, these have been included in the replicability survey.
Let's use https://cran.r-project.org/web/packages/qualtRics/vignettes/qualtRics.html to connect to our survey with an API. This will allow us to pull in useful things like metadata, and we should use it for data import with the next survey. It may also help with the dissociation of numeric codes from qualitative labels in responses.
I am reaching out to admins at Middlebury to enable the API for our license. Maybe ASU already has it working?