-
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
small bug: merging Multiomics drug response edges #775
Comments
I've confirmed that things work as-expected after the Prod deployment
POST to https://bte.transltr.io/v1/smartapi/adf20dd6ff23dfe18e8e012bde686e31/query (Prod instance, Multiomics drug-repsonse only through BTE)
Response (multiomics-fix.json) has two separate edges, one for TTD and one for drugcentral
Closing issue, opening a new one on a more robust fix. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I noticed an edge between imatinib - KIT, from Multiomics drug response, that had two primary_knowledge_source objects. When I dug into more, I realized that there were two records in the BioThings API that were being merged by BTE.
This can be fixed quickly by using "biolink:primary_knowledge_source" edge-attribute that is still there to identify unique edges. However, if this edge-attribute is removed later (since it's not actually needed), we'll need to figure out another way to "not merge" these records.
The text was updated successfully, but these errors were encountered: