You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
Feature Request Description
For extremely large databases, the preferred method of data extraction from REDCap switches between
oneshot
and "batch" methods (i.e. those supplied byREDCapR::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 thoughoneshot
is simpler and faster for most databases.Checklist
The text was updated successfully, but these errors were encountered: