-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Evaluate and Improve Disease Node pages #750
Comments
Moni: one thing that pops to mind is that we don't have publications presenting to the UI. |
Moni: we can be creative in how improve the disease pages, we don't have to rely on just the in-KG stuff to populate a good disease summary page. |
Here are some further pages for ideas: A demo disease KG using LLM's: Some work pulling together a KG from Monarch-KG with MonarchR |
I think we could use faceting in Solr to find the distinct list of publications for all associations to an entity, or all associations for a particular category or predicate or whatever. |
Moni would like us to evaluate and consider improvements to our disease node pages in order to make them more useful as a landing page for whatever someone may want to know about the disease as a jumping off point. We may even consider custom pages for these.
Diseases of interest Alzheimer disease and Downs syndrome.
Moni and I settled on an idea for a mock-up for additional disease page utility. I realized that this may take more backend work than I had anticipated. I’m looking into what we need to make the mock-up; I still think it is realistic in a short amount of time.
Mostly, this is looking to do some roll-ups to decrease repetitive information on the table's and to change the starting disclosure in the table to more than 5 entries.
The text was updated successfully, but these errors were encountered: