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] Optimize read_redcap for Batch processing #103

Open
4 of 5 tasks
rsh52 opened this issue Dec 8, 2022 · 0 comments
Open
4 of 5 tasks

[FEATURE] Optimize read_redcap for Batch processing #103

rsh52 opened this issue Dec 8, 2022 · 0 comments
Labels
backlog not to be worked on now enhancement New feature or request

Comments

@rsh52
Copy link
Collaborator

rsh52 commented Dec 8, 2022

Feature Request Description

The following is resultant of meeting with Will on 2022-12-08

For extremely large databases, the preferred method of data extraction from REDCap switches between oneshot and "batch" methods (i.e. those supplied by REDCapR::redcap_read).

For smaller databases, reading in REDCaps using batches can be slower, so it is not always a great solution. We should determine a way to assess REDCap database size at onset and then send the extraction call to the appropriate function.

To note, the real draw to this is an increase in reliability that batch reading can provide over oneshot methods, even though oneshot is simpler and faster for most databases.

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
@rsh52 rsh52 added the enhancement New feature or request label Dec 8, 2022
@rsh52 rsh52 added this to the 0.3 milestone Dec 8, 2022
@rsh52 rsh52 added the backlog not to be worked on now label Dec 8, 2022
@rsh52 rsh52 modified the milestones: 0.3, 0.4 Feb 20, 2023
@rsh52 rsh52 removed this from the 0.4 milestone May 23, 2023
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

1 participant