Pre-clean the APS data: One row per case number

[mbcann01]

Right now, in detect_pilot_test_1y_refine_matches.Rmd, the APS data has a row for each reporter, as opposed to each case. This is causing some issues with merging the data (#27). Specifically, it affects our ability to identify the most proximal APS investigation to each DETECT screening. And we can't just arbitrarily pick one row from each case because we found differing investigation outcomes in some cases.

So, we want to retain the information related to multiple reporters, but we want to do it in a wide format.

• [ ] Resolve within case discrepancies between rows
• [x] Widen reporter information by creating dummy variables
• [ ] Create min and max investigation date variables
• [ ] Create a number of reporters variable
• [ ] Check to see how what effect, if any, this has on the RecordLinkage results.
  • Changed ems dummy variable from "ems" to "reporter_ems". See how that affects the DDD code.
• [ ] Push wide APS data frame through downstream code

Addressing in the bug-31-aps-one-row-per-case branch.

[mbcann01]

Left off at 54. I just finished replacing the old "mutate_if" code with "mutate(across())" code. Keep checking code down to 136, and then remove within case discrepancies between rows.

[mbcann01]

Left off on line 300 of data_aps_02_variable management.Rmd in the bug-31-aps-one-row-per-case branch.

• I finished identify within-case value discrepancies.
• I still need to resolve them.