-
Notifications
You must be signed in to change notification settings - Fork 11
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
Refining creative-mode templates for Sept 2023 release #461
Comments
TDLR: There's still work:
From Slack discussions:
|
I'm going to close #237, but just noting here that orthology-based templates could also be good for drug-disease templates for creative mode... |
@colleenXu @andrewsu Just taking a brief browse through the TAQA triage board, looks like this issue may come from us. I think we could avoid this with some changes to make the directionality of |
Based on today's meeting it seems we want to make the template more specific, but duplicate the less-specific version as a template with lower execution priority. |
Keep in mind: UI has a 3-hop limit and subclass edges from node-expansion will count as 1. So templates should be only 1 / 2 hops right now... |
Also, can modify templates now that "qualifier hierarchy expansion" is now supported. See #598 |
As discussed in today's meeting, the scope of this issue (defined for Sept release) is: |
Originally, this issue was addressed by biothings/bte_trapi_query_graph_handler#167. But after #699 and #701 were identified, I adjusted the templates. The two main asks of this issue are still addressed by the adjusted templates + templateGroups. Details of the adjustments made can be seen in #699 and #701 and in the PR that addresses them biothings/bte_trapi_query_graph_handler#169 (comment). I include basic info on the latest testing in this PR. |
Tracking will continue in linked and future issues, closing this one as completed |
Making a new issue to track the work related to writing creative-model query templates (involves testing them against diseases in individual queries, and deciding the order to run them in....).
Related to previous comments in #449 and #453.
The text was updated successfully, but these errors were encountered: