We want to ensure the overarching goal of ORCESTRA is clear to new users and data contained is obvious. This means a clear ORCESTRA mission goal and ensuring data types have unique descriptions breaking down their contents and what to expect from them.
This means a creation of a new datatypes collection which will be referenced to render the different datatype bubbles.
datatypes ex:
{
name: 'Pharmacogenomics',
fieldTotals: ['Datasets: 33', 'Canonical: 16', 'TCL Cell Lines: 39'], # to be calculated on the fly, not directly part of DB
contains: ['rnaseq', 'cnv', 'mutation', 'methylation'], # to be calculated on the fly, not directly part of DB
description:
"Data focused with how an individual's genetic attributes affect the likely response to therapeutic drugs.",
img: 'pharmacogenomics.png',
path: 'pset'
}
Mission Statement Example:

We want to ensure the overarching goal of ORCESTRA is clear to new users and data contained is obvious. This means a clear ORCESTRA mission goal and ensuring data types have unique descriptions breaking down their contents and what to expect from them.
This means a creation of a new datatypes collection which will be referenced to render the different datatype bubbles.
datatypes ex:
Mission Statement Example: