-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parsing error with updated response options #309
Comments
That would be my strong guess, yes--though as for what we should do about it directly I'm less clear. I'm suspicious that much of That said, this does make me wonder about some stuff. To help with that, @EMWPhD, is when you were "looking at the metadata", was that from Also, what exactly did you mean had been done when you said "where the response choice options for any questions have been updated in Qualtrics"? (Again, sorry--your wording was fine, I just have to ask for some subtle technical reasons). |
No need to apologize @jmobrien! I am happy to clarify as best I can. When I said the response choice options were updated in Qualtrics, I was referring to the "variable naming" feature that shows up in the "recode values" section of the platform for each question. For a multiple choice question, this feature allows you to display a set of response options to the respondent, but change the wording on those response options for the exported results. I am including the documentation from Qualtrics and an example below. In the example, the text displayed to the respondent is on the right and the updated text that is to be exported is in the middle column in pink (e.g. "Full-time", "Part-time" without the parentheticals). When this feature is used, The example that I included above was using I tried using And the renames values are under: "Variable Naming" Documentation: Example: |
Thanks for the extra info. Yes, that seems about right. Looking at this more closely, I think it's a v2/v3 issue in the sense that we're looking at the kinds of extra features things that they tried to build around in v3, but as you have probably noticed it's complex either way. Fortunately, I'm now thinking it might be possible to fix this for now in a relatively simple way, without requiring it to be a part of a more wholesale redesign. But I need to check a few things first, and could use your help. With a configuration exactly as you screenshotted just above, would you mind copying here the full content (from |
Absolutely, happy to help in any way that I can. Below is the full list that prints from that QID. I hope this helps, but if there is any additional information that I can provide please let me know.
|
Great, this is useful. Could you perhaps do the same using Don't need to post both outputs, necessarily, but I'm guessing there might be one or two elements that vary and what those are would be good to note what those are if you see them. (And thanks. I would usually check these sorts of thing myself but I'm limited right now). |
Sure thing, happy to help. Below are the three examples. I ran using
using
using
|
Awesome package! I think the issue that I am experiencing is related to issue #278, but I am experiencing some different functionality that I was hoping to understand more about.
When I use
fetch_survey()
I seem to receive a parsing error for any field where the response choice options for any questions have been updated in Qualtrics. Looking at the metadata for the survey, the original response choice seems to be stored under "choiceText" whereas the updated values are stored under "description" (example below).Oddly enough, if I run
fetch_survey()
with the optionimport_id = T
I do not get a parsing error and the updated text appears as the value labels and the columns are labelled using the QIDs (as expected).I am just trying to understand this functionality better and see if there is a way to avoid these parsing errors using qnames instead of qids.
2
$choices
[1] "2"
$choices$2$ description
[1] "Updated Text"
$choices$2$ choiceText
[1] "Original Text"
The text was updated successfully, but these errors were encountered: