Open xiamaz opened 4 weeks ago
This ticket is required for implementation necessary changes for fulfilling processing needs in the model initiative.
Can only be solved in the new data flows application.
Can be solved via case manifest attributes in imported phenopacket format.
Is your feature request related to a problem? Please describe. Currently it is only possible to ignore entire projects for background database computation. While this allows ignoring data in test projects, there are use-cases, where samples need to be duplicated in multiple cases (analysis of a second index in the same family). The repeated samples from existing samples should not be included in the background database computation, whereas new samples should be.
Describe the solution you'd like During case-creation a flag should exist, which can be used excluded individual samples from background database computation.
Describe alternatives you've considered Cases with existing samples could be created in a separate project which is not included in background database computation. This would still not allow inclusion of new data in background database computation.
Additional context Further in the future relatedness information in the form of a fingerprint should be made available to allow for more generalizable identification of duplicated samples.