Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Studies with mixed data types #442

Open
cleme opened this issue Nov 11, 2022 · 0 comments
Open

Studies with mixed data types #442

cleme opened this issue Nov 11, 2022 · 0 comments
Labels
enhancement meta issue issue to be broken down into component issues and then linked to this one
Milestone

Comments

@cleme
Copy link
Member

cleme commented Nov 11, 2022

Is your feature request related to a problem? Please describe.
Some studies include more than a single microbiome data type, e.g. 16S and shotgun. It is currently unclear whether those should be stored as different studies or the same.Note this is different to studies in which we have microbiome and some other -omic datatype (metabolomics), because in that case the secondary datatype is considered (somewhat arbitrarily) "metadata".

Describe the solution you'd like
This needs to be discussed carefully. On the one hand, allowing multiple data types within the same study is more natural and might allow for cross-comparison of data types (e.g. correlation analysis btw 16S and shotgun). PICRUSt is, in a sense, already doing this, as predicted functions are included as part of a study that has 16S data. However, this will complicate code base even assuming we can call Ensemble from MMEDS. Separating into different studies (StudyX_16S vs StudyX_shotgun) simplifies things but complicates centralizing analysis.

@cleme cleme added enhancement meta issue issue to be broken down into component issues and then linked to this one labels Nov 11, 2022
@cleme cleme added this to the 0.10.0 milestone Nov 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement meta issue issue to be broken down into component issues and then linked to this one
Projects
None yet
Development

No branches or pull requests

1 participant