You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a maintainer, I want to be able to update the processing pipeline of a single organism at a time without bumping versions of the pipelines of other organisms (which then also leads to the reprocessing of data of the other organisms).
At the moment, the backend maintains a single processing pipeline version and only accepts data that have the current version or a higher version. This is maintained across all organisms. I.e., if we want to upgrade the pipeline for one organism, we have to upgrade the pipelines for all other organisms as well.
This should be changed. We should be able to have pipelines with different version numbers for different organisms. I think that we would add an organism column to the current_processing_pipeline.
The text was updated successfully, but these errors were encountered:
As a maintainer, I want to be able to update the processing pipeline of a single organism at a time without bumping versions of the pipelines of other organisms (which then also leads to the reprocessing of data of the other organisms).
At the moment, the backend maintains a single processing pipeline version and only accepts data that have the current version or a higher version. This is maintained across all organisms. I.e., if we want to upgrade the pipeline for one organism, we have to upgrade the pipelines for all other organisms as well.
This should be changed. We should be able to have pipelines with different version numbers for different organisms. I think that we would add an
organism
column to thecurrent_processing_pipeline
.The text was updated successfully, but these errors were encountered: