Custom Gene search UI

[mitalia]

We have the need in multiple projects that integrate genomic data to have a solid gene search capability. While I'm most interested in getting this going for Varify, I think this is likely to have utility beyond that in PCGC, AudGenDB, and other stuff I'm probably forgetting. It is at least as generally applicable as the diagnosis browser. I'm certain external users would have a use for this. It's essentially a modification of our existing ID-type search.

The mock-up is a little sloppy as far as layout, but the key behavior is that you don't get a paginated list of genes, but a search area that hits the backend and displays only what you search for (though once results come back they could be paginated so as to allow someone to do a broad search and flip through results). Note that the search should be smart and hit multiple fields including aliases.

[naegelyd]

Can this be generalized? I would be hesitant to include a gene search UI control within Cilantro proper since Harvest itself is not branded as a genomics specific data discovery platform but instead as a general one. @mitalia, @bruth do you think this would have more utility as a multi-field search tool? If this needs to be a specific instance of a gene search tool then we might want to move this issue Varify or a new cilantro-controls repo which holds a bunch of custom UI controls that people can contribute to and use at their discretion but aren't bundled with Cilantro itself in order to keep Cilantro at the generic level it stands at today.

[bruth]

As of 2.2.6, controls can be specified as AMD module paths in the configuration. So that means the opportunity for creating a repository of Cilantro controls that can be dropped into a project and simply added to the configuration.

That being said, it should not go into Cilantro core, but developed as it's own control (similar to the vocab browser). It can then be downloaded and included for the projects that need them.

[bruth]

So.. I agree with @naegelyd :)

[mitalia]

This can certainly be implemented as something more general. This will be used as is across PCGC, AudGenDB, and Varify, so it is at least as useful as the diagnosis browser in its own right. I am just cognizant that a production version of Varify needs to get out the door soon, and I know that generic solutions often take longer than non-generic ones.

[bruth]

Agreed, establishing a separately managed repository can come later, but this control should be developed in Varify first and then broken out later rather than in Cilantro proper.

[naegelyd]

Closed in favor of chop-dbhi/varify#97