Gene.iobio STTR requirements

This is a succinct list of requirements to satisfy the goals of the gene.iobio STTR:

[x] 1 - 3.2.1. Get patient HPO terms from Mosaic (gene 4.8)
[x] 2 - 3.2.1. Include gene:phenotype associations (see clin.iobio demo and image in #844)
[x] 3 - 3.2.2. Gene speed-up - launch saved analysis from Mosaic and gene.iobio loads instantaneously from saved object
[x] 4 - 3.2.2. If a new gene is selected, there is some time to analyse new variants, but once loaded, user will be able to move between genes with almost zero lag. Clicking on variants will be extremely quick
[ ] 5 - 3.2.2. Keep track of when a saved analysis was saved and what resources are included. This will be available to see in gene.iobio. After a period of time, if the analysis is relaunched, the user will be prompted to reanalyse based on up-to-date resources
[x] 6 - 3.2.3. Get annotations from the VCF INFO field. Modal allows user to pick the annotations they want to see (use the VCF header to provide a list of available annotations)
[ ] 7 - 3.2.3. Gene.iobio should have a mode to only show variants pulled from the VCF or Mosaic - no real-time annotation. This would be super quick and allow the user to see the annotations they want
- This will be implemented in upcoming gene.iobio release 4.10 (@tonydisera)
[x] 8 - 3.2.3. Mosaic gene.iobio launcher gives an option to select annotations and gene.iobio would pull these from Mosaic
[ ] 9 - 3.3.2. Saved gene.iobio analyses in Mosaic can be versioned
[ ] 10 - 3.3.3. Update gene.iobio dependencies (javascript framework Vue, framework Vuetify, node etc.)
[ ] 11 - 3.3.4. Allow gene.iobio and Mosaic to exchange conversations
- Gene.iobio variant notes will be saved as variant conversations in upcoming gene.iobio version 4.0 (@tonydisera)

iobio / gene.iobio

Gene.iobio STTR requirements #900