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

[FEATURE] tidy exports from csv instead of API #207

Open
5 tasks
shannonpileggi opened this issue Sep 23, 2024 · 3 comments
Open
5 tasks

[FEATURE] tidy exports from csv instead of API #207

shannonpileggi opened this issue Sep 23, 2024 · 3 comments
Labels
backlog not to be worked on now enhancement New feature or request

Comments

@shannonpileggi
Copy link

Feature Request Description

You have such amazing functionality to tidy redcap data! It would be nice if there were user facing functions that could do the same for csvs exported from redcap as well.

Describe alternatives you've considered

Pain and suffering.

Additional Context

We were recently contracted for short term support for a database hosted in REDCap at an instution at which we did not have API access, and we received the data via csvs. Granting us API access was not feasible. Thank you for considering!

Checklist

  • The issue is atomic
  • The issue description is documented
  • The issue title describes the problem succinctly
  • Developers are assigned to the issue
  • Labels are assigned to the issue
@shannonpileggi shannonpileggi added the enhancement New feature or request label Sep 23, 2024
@skadauke
Copy link
Collaborator

skadauke commented Sep 23, 2024

This would indeed be awesome but without API access and access to metadata some key information we use to slice and dice the tables is missing. We looked into this and I believe it is a hard problem. For your present use case, wouldn't it be possible to ask someone who does have API access to use REDCapTidieR to pull the data and then email you the RDS file?

library(REDCapTidieR)
data <- read_redcap(uri, token)

data |> saveRDS("data.rds")

@shannonpileggi
Copy link
Author

No, that is not an option in this case.

I do appreciate the additional complexity not having API access generates!

@rsh52
Copy link
Collaborator

rsh52 commented Sep 23, 2024

Shannon and I discussed this a bit today, and Stephan's right it wouldn't be possible to make a supertibble without the metadata. However, if the team you work with is able to export the data and can also export the metadata then I don't think it would be that much effort to enable accepting via files instead of the API. They would just need to go to the API Playground and export the metadata as a JSON/CSV/XML:

image

I also mentioned how using these interim files as a workflow opens up more opportunity for data structure changes that would be tough to debug, but I figured it was worth having a record of this use case.

Describe alternatives you've considered
Pain and suffering.

Ah, so a nice and normal experience 😆

@rsh52 rsh52 added the backlog not to be worked on now label Oct 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog not to be worked on now enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants