TADAShiny flagging functionality in TADA

[ehinman]

Is your feature request related to a problem? Please describe. Currently, the TADA vignette walks an R user through steps to run the different QC functions and uses a "new assignment" approach, where every step creates a new data object. This was initially implemented to be able to keep track of a dataset that presumably shrinks with each QC screen and return to a previous "version object" of the data if needed. However, as the shiny app has undergone development, it has become a workflow that "flags" records for removal based on user decisions without actually removing anything. This is a less linear, more flexible approach that has nonetheless diverged from the TADA vignette. Would it be possible to align the TADA vignette in a way that more closely resembles the TADAShiny workflow?

Describe the solution you'd like The vignette could run all of the flagging functions in one chunk. Each flagging function adds subject-specific columns with content the user reviews to make a decision on whether to "keep" or "remove" a result from consideration. The user could then have a function, spreadsheet, or set of specifications they use to determine which flags destine a result for removal. Like the app, these decisions would be used to populate a "Removed" = TRUE/FALSE column in the dataframe that could then be used to create a summary detailing how many records were removed for each QC flag reason.

Describe alternatives you've considered The user determines a custom R script workflow for removing results that do not pass QC screens.

Additional context Add any other context or screenshots about the feature request here.