Is your feature request related to a problem? Please describe.
MMEDS current organization of data and metadata is quite complex: required metadata is stored in SQL, analysis specs are in MongoDB, mapping files (with additional metadata) and raw data sit on disk. This requires substantial amount of code to glue together, and limits what can be done (e.g. meta-analysis can only be done with SQL metadata, but not with additional metadata).
Describe the solution you'd like
Unclear what is the best solution. At a minimum, I think we should be able to generalize meta-analysis to include also additional metadata. Solutions discussed during MMEDS meeting include:
create specific SQL table for additional metadata
have mongoDB store additional metadata
check how other services (e.g. QIITA) might be doing this: larger template files to capture more metadata?
Is your feature request related to a problem? Please describe. MMEDS current organization of data and metadata is quite complex: required metadata is stored in SQL, analysis specs are in MongoDB, mapping files (with additional metadata) and raw data sit on disk. This requires substantial amount of code to glue together, and limits what can be done (e.g. meta-analysis can only be done with SQL metadata, but not with additional metadata).
Describe the solution you'd like Unclear what is the best solution. At a minimum, I think we should be able to generalize meta-analysis to include also additional metadata. Solutions discussed during MMEDS meeting include: