because the vignette will use the ucdenver REDCap API, a token, and one of my ssh keys, it is not reasonable to have the vignette built dynamically via R CMD BUILD. Use the same static vignette set up you used for the ensr package.

This vignette will be added to the generated R package to summarize the project. This should include the checkmate script (see #4) applied to the meta data, summary of the users.

This change is made to simplify the workflow for other contributors.

add a check for phi

Idea for a feature:

download the data dictionary and build a flowchart for the order the questions will be shown to the user in. Include the branching logic in the construction of this flow chart.

@aljensen89 reported an error on windows for a project using REDCapExporter.

Error: Unknown SSL protocol error in connection to redcap.ucdenver.edu:443

I have reproduced the error and run some tests and believe the issue comes from using RCurl to make the calls to the REDCap API. Consider using the curl or httr package instead.

For some reason having the devtools::check in the export vignette results in a R CMD check --as-cran failure, but R CMD check will pass.

To reproduce the error:

git checkout 6c88ae3
make check          # Status Ok
make check-as-cran  # Status 1 Warning, 1 Note

The warning is:

* checking re-building of vignette outputs ... WARNING
Error(s) in re-building vignettes:
  ...
--- re-building ‘api.Rmd’ using rmarkdown
--- finished re-building ‘api.Rmd’

--- re-building ‘export.Rmd’ using rmarkdown
Quitting from lines 128-130 (export.Rmd) 
Error: processing vignette 'export.Rmd' failed with diagnostics:
R CMD check found WARNINGs
--- failed re-building ‘export.Rmd’

SUMMARY: processing the following file failed:
  ‘export.Rmd’

Error: Vignette re-building failed.
Execution halted

The lines causing the issue:

head -n 130 vignettes/export.Rmd 

  ```{r warning = FALSE}
  check <- devtools::check(pkg = prj_dir, quiet = TRUE, cran = FALSE)
  check
  ```

• write and export functions
• write example
• edit the api vignette

when format_record is asked to return a data.table I have a check in place to look for S4 classes. If any S4 columns exist a warning message is given to the user. There can be several different issues that arise with respect to S4 columns in a data.table. This is not a REDCapExporter issue per se, the "best" solution will need to come with updates to data.table. However, the warning message and tracking and resolution of this issue here is needed.

Rdatatable/data.table#4315

When exporting from REDCap you can have the download in XML format. This format will likely have richer data than the csv or json exports. Add the xml format support to the export tools.

Verify all col-types are accounted for in col-type.R

Feedback from presenting the initial work to the REDCap admins at UCD on the 12th of March 2019:

I buried the lead in the vignette. I need to move the primary function to the top of the vignette and provide additional details after the primary function use is shown.