ideafast / middleware-services

Python API containing endpoints for smartphone hub applications and transfer to data portal
0 stars 0 forks source link

Manually trigger upload to DMP #78

Open jawrainey opened 3 years ago

jawrainey commented 3 years ago

The current pipeline runs per-patient and only uploads data if all all records (metadata) in the database is marked as being downloaded, i.e., that we have access to the raw recordings. For dreem, this means that if there is one patient and 14 records, but one of those records has not been downloaded, then the undownloaded recording must be modified to be skipped. The pipeline running in this way was designed so that all data would be uploaded in one zip.

We need to resolve this after FS, and could do this in two ways:

  1. Modify the pipeline to skip data that is not downloaded
  2. Allow clinical staff to initiate/trigger the pipeline if something went wrong?

It is likely that (2) would be useful regardless given there won't be much technical support in the CoS.

Making this issue now for future discussions.