Open james-eda opened 7 months ago
Good idea re: double-QC using git. We can use Github to track status of dev and qc pgms and outputs. Still, a log must be produced (at least at the very end) to confirm that the prescribed level of validation has been performed on all of the reports included in the CSR. It may also be used as a single-source of titles and footnotes for our TLFs (titles and footnotes can change before the final CSR is submitted). Maybe we split the QC log and the titles/footnotes source into separate files. The QC log also includes SDTM, ADaM datasets...
This worksheet will be used for titles/footnotes and qc tracking. For each output, assign column values for:
the output name will serve as the file name, the program name, etc and should follow rules like (t, l, f_ .[filetype] and , vt, vl, vf[filetype] for the corresponding QC or validation programs and outputs. Filetypes include ".r" ".sas" ".rtf" ".pdf" ".xpt").