search

mattroumaya / surveymonkey

Access your SurveyMonkey data directly from R!
https://mattroumaya.github.io/surveymonkey/
Other
42 stars 10 forks source link

Multiple choice parsing error? #119

Open arthurriedel opened 1 year ago

arthurriedel commented 1 year ago

Failure with:

fetch_survey_obj(foo) %>% parse_survey()

Error in x$q_unique_id[x$question_type == "multiple_choice" | x$question_subtype == : NAs are not allowed in subscripted assignments

libbyseline commented 4 months ago

Was there ever a fix to this? Im having the same error right now. I've tried to work around it, but I fail to parse it correctly every time

mattroumaya commented 4 months ago

Hi @libbyseline - sorry that there has not been a resolution to this issue. I no longer have a SurveyMonkey account and am not able to replicate the issue, but am happy to try to troubleshoot if you can provide any additional details.

As another route, SurveyMonkey basically forked this R package (initially developed by @sfirke and his team at TNTP) and released it as their own V1 open-source package without ever posting on this repo or attempting to collaborate, and then added some more opinionated functionality. The authors section highlights the history of this package, and it appears SurveyMonkey has taken on responsibility of their "own" package.

With that said, I'd imagine they should have the resources to help you out!

sfirke commented 4 months ago

@mattroumaya fascinating, I had no idea. I think it would have been good open-source etiquette to post in this repo before forking and releasing. Though I appreciate that we are acknowledged in the README and the fork maintains the commit history.

I am thinking of this post I read last week: http://www.catb.org/esr/writings/homesteading/cathedral-bazaar/ar01s02.html

In particular:

When you lose interest in a program, your last duty to it is to hand it off to a competent successor.

Matt, as you note, you and I no longer use SurveyMonkey, and the company should be able to maintain and expand their fork of the package. If you want you could add a notice about svmkR replacing this project and archive this repo, though it's entirely your call. I see @libbyseline opened this issue as https://github.com/soubhikbarari/svmkR/issues/29, that is probably the best bet for getting this fixed.