Closed mike-caarg closed 8 months ago
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 REDCapTidieR
on main now with your respective databases and use allow_mixed_structure = TRUE
to see if it handles your use cases? When allowed, non-repeating versions of mixed-structure instruments should appear in repeating tibbles as single repeating instances.
Please use below to install:
devtools::install_github("CHOP-CGTInformatics/REDCapTidieR")
Thank you!
Hi @rsh52 Great! it works. Everything is fine. Thank you very much for your work
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, Thank you for adding the functionality. It's perfect, everything works correctly on our test data.
Hi, I have not had time for extensive testing, but this seems to fix this issue! Thanks!
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: