-
Notifications
You must be signed in to change notification settings - Fork 8
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
[BUG] Package does not support forms used in both repeating and non-repeating contexts #176
Comments
Hi @mike-caarg, thank you for raising this to our attention. You can see our discussion in another issue #169 It was intended originally to keep this as a barrier due to conflicts between tidy data principles and REDCap database design. However, we will likely be looking into a solution to help with this for v1.1. |
@mike-caarg, @brianmsm, @bcuer (from issue #169 ) Can you try the development version on Please use below to install: devtools::install_github("CHOP-CGTInformatics/REDCapTidieR") Thank you! |
Hi @rsh52 |
Hi @mike-caarg and @bcuer, is there any chance we can get confirmation from you as well? We would like to submit a new release of the package at the end of this week. |
Hi, |
Hi, I have not had time for extensive testing, but this seems to fix this issue! |
Thank you all! Considering this closed from #177 |
Expected Behavior
When a form is used in both a repeating and non-repeating manner, I expect REDCapTidieR to know the difference and partition the data accordingly
Current Behavior
Currently, if a form is used in both a repeating and non-repeating manner, REDCapTidieR throws an error.
How to Reproduce the Bug:
Screenshots
Example output from using "read_redcap()" on a database with a form used in repeating and non-repeating contexts
Failure Logs
NA
Checklist
Before submitting this issue, please check and verify below that the submission meets the below criteria:
The text was updated successfully, but these errors were encountered: