This vignette provides detailed documentation and usage examples for
generating QC summary documents with the review
package. The functions, renderQCSummary()
and
renderQCReport()
, generate documents containing QC summary
tables. These are intended to aid in quality control and prioritizing QC
resourcing.
renderQCSummary()
: Generates a
document with summary tables of outstanding QC informationrenderQCReport()
: Generates a document
that provides the QC status of files in a projectrenderQCSummary()
The renderQCSummary()
function generates a QC summary
based on scripts within a given project and renders it into a PDF
report. This PDF contains multiple summaries, including:
QClog.csv
file.QClog.csv
file.To generate a QC Summary report, use the following command:
When files require QC, the following type of table will appear in the report:
Output (Example):
File | Last Author | Previous QCers |
---|---|---|
script/data-assembly.R | Jane Doe | none |
script/examp-txt.txt | John Smith | Alice Johnson |
script/pk/load-spec.R | John Smith | Jane Doe, Alice Johnson |
Each file that appears in this table requires QC. The column Previous QCers lists reviewers who previously QC’d the file.
Another section of the report identifies recently modified files not in the QC log:
Output (Example):
File | Last Author | Days Since Last Edit |
---|---|---|
script/eda-tables.R | Jane Doe | 1 |
script/eda-figures.R | Alice Johnson | 8 |
script/pk/check-sum.yaml | Alice Johnson | 20 |
This summary helps prioritize adding files to the QC log.
renderQCReport()
The renderQCReport()
function generates a comprehensive
QC status summary of all files in the QC log and renders it into a PDF
report. This report provides an overview of files that are up-to-date or
still require QC.