Skip to content
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

Export Survey Time-stamps #159

Closed
lynatruong opened this issue Jun 27, 2017 · 8 comments
Closed

Export Survey Time-stamps #159

lynatruong opened this issue Jun 27, 2017 · 8 comments
Assignees

Comments

@lynatruong
Copy link

Is it possible to export the time-stamps for the entered records? The redcap_read_oneshot function doesn't seem to do this. This would be helpful for my project because I would like to do a filter logic on dates.

@wibeasley wibeasley self-assigned this Jun 28, 2017
@wibeasley
Copy link
Member

I'm pretty sure that there's not an automatic timestamp available through the API. If you can get one through the API playground, please let me know and reopen the issue.

However I bet it's relatively easy to (a) create your own field, (b) populate it with the '@now' action tag, and (c) hide or disable it from the user (with another action tag). You may have to play with the settings so that it sets the timestamp for only the records that were modified in the GUI.

@firaswehbe
Copy link

firaswehbe commented Jan 18, 2018

@wibeasley I think you can get the timestamp for surveys see exportSurveyFields='true' below from the api playground. I'm trying to get that as well using this package

#!/usr/bin/env Rscript
library(RCurl)
result <- postForm(
    uri='https://redcap.nubic.northwestern.edu/redcap/api/',
    token='B000BE5427163CF44ADDC4EFB88xxxx',
    content='record',
    format='json',
    type='flat',
    rawOrLabel='raw',
    rawOrLabelHeaders='raw',
    exportCheckboxLabel='false',
    exportSurveyFields='true',
    exportDataAccessGroups='false',
    returnFormat='json'
)
print(result)

@wibeasley
Copy link
Member

@firaswehbe, thanks for the tip. I'll look into it. We've never needed that, but I'm happy to support it if other will.

@wibeasley wibeasley reopened this Jan 18, 2018
@firaswehbe
Copy link

Typical use case for us of the surveyform_timestamp survey variable is to plot survey cumulative response over time for our public surveys. When the curves flatten out we know to send reminders or post on other forums if we still need more responders. e.g. here

@rparrish
Copy link
Contributor

Adding my vote for this as well. Will use @now in the meantime.

@isaactpetersen
Copy link

Adding my vote for this, as well. Looking to do this with the redcap_read() function. (sorry I didn't see that this issue already existed!

@kevinmoran805
Copy link

I think this would make a great addition too. We use survey completion timestamps for automating things like payment and study randomization.

wibeasley added a commit that referenced this issue Mar 6, 2018
wibeasley added a commit that referenced this issue Mar 7, 2018
@wibeasley
Copy link
Member

Thanks everyone on this thread for your input. This is now available on the master. Please tell me if it's not working the way you expected by starting a new issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants