e.g. when a new sequencing-reads.gz hits seqauto, run a pre-canned bactopia workflow. Ideally we can configure this in the bucket section for a tributary. it can probably be configured for any bucket, but clean ones are the only known use case right now (unless we were to configure etls and daps in the same way)
This will require some pretty significant book keeping and should support checking status of the DAP. Given the frontend will only have a chance to establish tracking data (i.e. an id we can link raw to clean to dap) at the time of initial upload of raw data, we'll need to institute something like a workflow/job id (careful not to use a word that's already overloaded) that we can use to check many parts of the data lifecycle (e.g. etl status, dap status, etc)
e.g. when a new
sequencing-reads.gzhits seqauto, run a pre-canned bactopia workflow. Ideally we can configure this in the bucket section for a tributary. it can probably be configured for any bucket, but clean ones are the only known use case right now (unless we were to configure etls and daps in the same way)This will require some pretty significant book keeping and should support checking status of the DAP. Given the frontend will only have a chance to establish tracking data (i.e. an id we can link raw to clean to dap) at the time of initial upload of raw data, we'll need to institute something like a workflow/job id (careful not to use a word that's already overloaded) that we can use to check many parts of the data lifecycle (e.g. etl status, dap status, etc)