We have a good amount of data in our nodes and are starting to also host richer data. Many of the richer data have at least some longitudinal information on phenotypic data - and we cannot model this because we model phenotypic information at the subject level. This will allow us to provide much richer queries in the near future and is, from the tool and data model side, a relatively easy thing to do.
Context
We have a good amount of data in our nodes and are starting to also host richer data. Many of the richer data have at least some longitudinal information on phenotypic data - and we cannot model this because we model phenotypic information at the subject level. This will allow us to provide much richer queries in the near future and is, from the tool and data model side, a relatively easy thing to do.
There is also BEP36 making its way towards completion, and we want to both have some ideas on that and be able to model BEP36 information once it merges.
The overall design ideas live here: https://miro.com/app/board/uXjVNIzFV9w=/
IMportant stuff
Why
Outcomes
What
CLI
Annotation tool
"Work"
API
Federation API
Query tool
Documentation-related
What it is not
To close it all out