Comments (5)
Could you not use the 'lastResponseId' parameter for this?
I don't know how you store your results. I store them in a database and append each time I update results. Then it's just a matter of querying the last row in the table.
If you don't want to do this, I recommend that you take the last response Id and simply write it to a file in your working directory!
from qualtrics.
from qualtrics.
Sorry for not being clear. You have to supply the response ID. What I mean is that it would be relatively simple for you to implement this yourself. All you'd need to do is set up the following pipeline:
pipeline <- function(surveyID, ...) {
# 1. Search for 'lastResponseId.rds' in working directory. If it exists, load.
# 2. If you loaded the last Response ID in step 1, pass it to the 'getSurveys' function, else, run the getSurveys function without this parameter.
# 3. Take the last responseid from the survey you collected and save it to 'lastResponseId.rds' in your working directory.
... rinse and repeat
}
This should work fine for what you're trying to do.
Let me know if you need more help with that.
Best,
J.
from qualtrics.
from qualtrics.
from qualtrics.
Related Issues (20)
- exporting csv as numeric values HOT 2
- Automatic coercion from logical to character was deprecated in purrr 1.0.0. HOT 1
- fetch_survey and save_dir HOT 4
- fetch_survey doesn't seem to pull a retaken response HOT 2
- Support for OAuth (vs. API Token)? HOT 2
- Issue with fetching surveys HOT 3
- fetch distribution summary information? HOT 2
- error on fetching distribution history (i.e., full list of survey invitees along with distribution status) HOT 3
- `dplyr::case_when()` within `dplyr::mutate()` loses `qualtRics` variable labels HOT 7
- lag / incomplete pull of list_distribution_links() HOT 1
- feature discussion: custom temporary directory HOT 4
- Future look: Funding support from Qualtrics? HOT 2
- fetch_survey error; filename issue? HOT 18
- results from all_surveys() and list_surveys is different HOT 5
- fetch_survey produces "Error: Qualtrics API raised a bad request (400) error" HOT 5
- Overhaul of credentialling system
- Error parsing file: The file does not appear to be a valid survey. Save as qsf - am I doing it wrong? import doesn't work HOT 5
- write_qsf() currently enables only encoding UTF-8 that doesn't handle Hebrew and Arabic HOT 16
- Release qualtRics 3.2.0 HOT 1
- Qualtrics API reported a bad request error (400) HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from qualtrics.