REDCapR (version 0.9.3)

redcap_upload_file_oneshot: Upload a file into to a REDCap project record.

Description

This function uses REDCap's API to upload a file

Usage

redcap_upload_file_oneshot(file_name, record, redcap_uri, token, field, event = "", verbose = TRUE, config_options = NULL)

Arguments

file_name

The name of the relative or full file to be uploaded into the REDCap project. Required.

record

The record ID where the file is to be imported. Required

redcap_uri

The URI (uniform resource identifier) of the REDCap project. Required.

token

The user-specific string that serves as the password for a project. Required.

field

The name of the field where the file is saved in REDCap. Required

event

The name of the event where the file is saved in REDCap. Optional

verbose

A boolean value indicating if messages should be printed to the R console during the operation. Optional.

config_options

A list of options to pass to POST method in the httr package. See the details below. Optional.

Value

Currently, a list is returned with the following elements,

1. success: A boolean value indicating if the operation was apparently successful.
2. status_code: The http status code of the operation.
3. outcome_message: A human readable string indicating the operation's outcome.
4. records_affected_count: The number of records inserted or updated.
5. affected_ids: The subject IDs of the inserted or updated records.
6. elapsed_seconds: The duration of the function.
7. raw_text: If an operation is NOT successful, the text returned by REDCap. If an operation is successful, the `raw_text` is returned as an empty string to save RAM.

Details

The `REDCapR' package includes a recent version of the Bundle of CA Root Certificates from the official cURL site. This version is used by default, unless the `cert_location` parameter is given another location.

Currently, the function doesn't modify any variable types to conform to REDCap's supported variables. See validate_for_write for a helper function that checks for some common important conflicts.

References

The official documentation can be found on the `API Help Page` and `API Examples' pages on the REDCap wiki (ie, https://iwg.devguard.com/trac/redcap/wiki/ApiDocumentation and https://iwg.devguard.com/trac/redcap/wiki/ApiExamples). If you do not have an account for the wiki, please ask your campus REDCap administrator to send you the static material.

The official cURL site discusses the process of using SSL to verify the server being connected to.

Examples

## Not run: 
# #Define some constants
# uri  <- "https://bbmc.ouhsc.edu/redcap/api/"
# token <- "D70F9ACD1EDD6F151C6EA78683944E98" #For the simple project (pid 213)
# field <- "mugshot"
# event <- "" # only for longitudinal events
# 
# #Upload a single image file.
# record <- 1
# file_path <- base::file.path(devtools::inst(name="REDCapR"), paste0("test_data/mugshot_1.jpg"))
# 
# redcap_upload_file_oneshot(file_name=file_path, redcap_uri=redcap_uri, token=token,
#                            record=record, field=field)
# 
# #Upload a collection of five images.
# records <- 1:5
# file_paths <- base::file.path(devtools::inst(name="REDCapR"),
#                               paste0("test_data/mugshot_", records, ".jpg"))
# 
# for( i in seq_along(records) ) {
#   record <- records[i]
#   file_path <- file_paths[i]
#   redcap_upload_file_oneshot(file_name=file_path, redcap_uri=redcap_uri, token=token,
#                              record=record, field=field)
# }
# ## End(Not run)