Capture feedback about proposed table with "all associations together"

[monicacecilia]

Following the Directors' recommendations, our Monarch Tech Team advanced a proposal to combine all the results tables into a single page, without drop-down menus, when users explore the knowledge graph with the Monarch website. It includes a navigation "column" on the left, allowing users to easily return to any sections.

For an example of the proposed changes, please visit the Monarch development website and navigate to the Gene Page for apolipoprotein E (APOE) here: APOE | Monarch Initiative.

Please provide your feedback on this ticket.

This ticket concerns how results are displayed and how easy it is to navigate through them. We are also working on updating some table headers (see #835 and #837); please feel free to provide additional feedback if desired.

FYI: @kevinschaper 👀 👆🏽

[cmungall]

I vastly prefer this style of display. This is commonly used for all knowledge bases.

I think there are a few things that could be improved or minor bugs. I will list a few to give a flavor. But to be clear, I think this new change should go ahead, and we can incrementally improve on some aspects.

Minor:

• If there are exactly 5 associations, it allows me to advance to next to show an empty list in the range "6-5". Off by one error?
• The ordering of association on the page can be improved. Interactions is not useful and not in Monarch's core area. In contrast, diseases are. Put these before interactions
• for orthologs there may be a more intuitive column order
• it may make sense to bundle GO
• why is external info not along with the other metadata? Some seems duplicative eg. ensembl mappings
• it's clunky to say "Phenotype to Gene" and confusing since the gene is on the left. If the context/focus is already gene, then just say phenotype
• there are many cases where you can collapse redundant annotations
• GO annotations seem to have lost their publications