or “ACE2”. Gene search usually returns only exact matches. Displaying related results is common in search UIs outside genomics. Mapping data to the genome enriches user experience. Showing related genes in ideograms improves scientific exploration. Gene search
results. Challenges: • Users must know genes a priori that are related to a gene they search • Scarce screen real estate for new UI components • Visualizing search results in genomic space is useful but hard Design goal
find two kinds of related genes: • Interacting genes: Adjacent nodes in the same biochemical pathway. • Paralogs: evolutionarily similar genes in same species. Often have comparable roles in different pathways.
• Knowing where something is not is useful and standard in search result maps. • Cytogenetic features (e.g. centromeres, stalks) can explain null results.
• Space efficient. Short, wide row of chromosomes uses empty page real estate. • Easy interaction. Plotting genes as large features makes them easy to see and click. • Domain specific. Users engage and recall more with tailored graphics than generic lists.
interactions for a given gene. • E.g. https://webservice.wikipathways.org/findInteractions?query=RAD51&format=json • Algorithm: ◦ Find interactions ◦ Filter by organism ◦ Omit non-genes ◦ Group pathways for each interacting gene • Explore the code: related-genes.js
conventional format -- Swagger -- and easily findable • Fast: returns interactions for a given gene in < 2 seconds • Feature-rich: easily filter by organism, immediately adjacent nodes
mouse is 21% that of human ....in Arabidopsis is 7% ... • Only 35 organisms • Often mapped from human, then not updated ◦ Yields less useful pathways due to disconnected interactions, etc.
recent pathway changes 2. User edits a source pathway 3. Bot reads list of target pathways from links in source pathway 4. Bot updates each target pathway, using fresh map of orthologous genes