REDCap data can include files: ideally, these should be downloaded from REDCap and included in the data package alongside tabular data. The exact details of how file download fits in the pipeline or how files are referenced in the data package have yet to be worked out.
We currently have CGM readings as files on visit 2 (besoegsdag_2.cgm_glucosedata_upload_v2) in REDCap.
To download the file, we need:
- record ID, i.e.
record_id_s in REDCap
- name of the file field that contains the file name
- name of the event that the form belongs to
request_data = {
"content": "file",
"action": "export",
"record": "01",
"field": "cgm_glucosedata_upload_v2",
"event": "besg_2_arm_1",
"returnFormat": "json",
}
When the file is tabular data, do we want to parse it and save it as Parquet? Either as a new resource or part of the resource it came from.
REDCap data can include files: ideally, these should be downloaded from REDCap and included in the data package alongside tabular data. The exact details of how file download fits in the pipeline or how files are referenced in the data package have yet to be worked out.
We currently have CGM readings as files on visit 2 (
besoegsdag_2.cgm_glucosedata_upload_v2) in REDCap.To download the file, we need:
record_id_sin REDCapWhen the file is tabular data, do we want to parse it and save it as Parquet? Either as a new resource or part of the resource it came from.