Open chris-s-friedman opened 5 years ago
Thanks so much for your thoughts here @chris-s-friedman! 🙌
I was looking a bit in detail at this tonight. What would you like to see from a function such as this, say called read_qsf()
? How would it be different from simply jsonlite::fromJSON(<YOUR-QSF-FILE>)
? Is there value in some processing of the file for analysis? As I look at this, it's not clear to me what would be most helpful to folks in your situation, beyond an extremely thin wrapper around the jsonlite import.
Just want to say, that idk why I never tried this method, but this is sweet! I can check out the whole survey in a dataframe. Thanks for helping me connect the dots @juliasilge.
@juliasilge that's what I was thinking except I used jsonlite::read_json()
when I probably should have just used fromJSON()
😉
I was looking for something that can give me the same abilities as read_survey
... that said I have a feeling that there aren't too many folks in my situation that can't use the API so it may be a bit much to have a dedicated function for handling these files. Thanks for the feedback!
For projects where you can't access the qualtrics API, it would be helpful to have a function that can read the qualtrics survey output. Although I think having API access is the gold standard here (and is my preference), this becomes a challenge if a project is hosted by another organization where getting an API key would also require getting credential for the hosting organization's system.
I'm proposing a function similiar to
read_survey()
in that it reads a downloaded .qsf file instead of downloading data from the API.In this case, the survey can be downloaded on the survey page as seen in the screenshot below. The result is downloading a .qsf file that is in JSON and has information about the survey (and can actually be loaded into qualtrics to import the survey).