I forked the project and started work on the upgrade of to V3 here https://github.com/seanofahey/Rmonkey. All help is welcome

If you would like, I can give you write permission here so that you can directly push updates. Interested?

@seanofahey Would you be interested in becoming maintainer of this package?

Basically, just keep doing what you're doing, but also send updates to CRAN (if you want). You would have write permission on the repository so you can make all changes here directly.

I am able to get my data out of SurveyMonkey using @seanofahey's fork 👍 So it feels like this is almost there.

Results-wise, some to-do enhancements I see there are (a) assign legal variable names to the columns and store the question text in an attribute and (b) ideally, retain ordered factor info for questions where that's applicable.

User-friendliness-wise, the README should be updated to address the new function workflow for getting data out. Some README content can come from the RMonkey Demo.R file but I don't think the new retrieval code is there. This would be best be written by @seanofahey since I've only stumbled into something that works but don't understand the organization of the functions. But, if that doesn't happen, I may write up what works for me, so my colleagues can use this.

@sfirke Thanks for the suggestions. I'll update the README content to sync it with what is available now and then get back to completing the remaining functions.

@seanofahey I've made some developments on my fork of your fork, https://github.com/sfirke/Rmonkey.

Among other things:

• renamed some functions slightly (taking the style in a tidyverse direction)
• updated the README (and did it in .Rmd)
• added a function to get an sm_survey from the survey_list by name, vs. by subsetting on index number
• the resulting data.frame with the survey data has sequenced variable names in the style of what SurveyMonkey gives you in an SPSS export (names are q1, q2, q3_1, q3_2, etc.) and the question text is stored as a label attribute on each column.

I opened and closed some issues on my fork too if you want to see what I have planned. I haven't touched any survey creation or modification functionality, those are low priority for me.

Let me know if/how you'd like to collaborate; I wanted to move on this so I could use it today but don't want to duplicate any work going forward.

@sfirke I updated the README file on my fork to more clearly explain the functions in use in the RMonkey Demo.R file. Let's sync tomorrow and we can plan the road ahead.

Hey guys, thanks to @seanofahey for upgrading to v3.

Just wanted to say that for large survey downloads (N-sizes larger than 2,000) it's really slow due to the for/repeat loops. After benchmarking, I replaced the loops with purrr::map() and it's hundreds of times faster. 2,500 respondents can be downloaded, filtered, and merged in under 5 minutes using map(). Just wanted to let you guys know incase you're looking to make it faster. Best!

@ClimateNexus I would love to see that - do you have it somewhere you could share?

@ClimateNexus could you post your updates to this package in a GitHub repo?

The PR for API v3 compatibility is pretty stale. I may need to work with SurveyMonkey in the near future and would like to have a clean interface. Are there cycles available from any maintainers to review a fresh PR in the coming weeks should this motivate me enough to contribute some bits? 😁

I'm no longer maintaining this package. If someone wants to work on it, I'm happy to grant edit rights.

Thanks, @leeper! Let me see if this project materializes to give me the needed drive to dive into this. If so, I'll reach back out to you. Thanks for all the work on this!

To anyone watching this, I built on the 2016 Rmonkey code (v 0.3.3) and rewrote the putting-the-result-in-a-tidy-data.frame part. The new package is here: https://github.com/tntp/surveymonkey It's still a work in progress but should work for most cases. I'd be eager to hear from users/devs here if you have feedback, find bugs, or can contribute to improving the code.

If it appears satisfactory I could probably clean it up and send it toward CRAN.

@sfirke I’m also happy to have you migrate that code to this repo, if you want. Will gladly give you edit rights if you’re interested.