Skip to content
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

ICEES diseases -> ROBOKOP genes #52

Open
karafecho opened this issue Dec 21, 2019 · 2 comments
Open

ICEES diseases -> ROBOKOP genes #52

karafecho opened this issue Dec 21, 2019 · 2 comments

Comments

@karafecho
Copy link
Collaborator

karafecho commented Dec 21, 2019

Regardless of queries tested, transitions from ICEES diseases (pink nodes) to ROBOKOP genes (yellow nodes) are incomplete.

image

@YaphetKG
Copy link
Collaborator

Looking at all the diseases returned back from ICEES @karafecho explained to me that those Ids are High level concepts. And when I was looking at the equivalent identifiers for those concepts, I see some that have might mean separate entities in robokop exist on the list of equivalent ids for a node,
Here is an example to illustrate:

'AsthmaDx': (id: SCTID:195967001) -- > this is not used by ROBOKOP
 IN AsthmaDx equivalent ids these are some of them used 
  'MONDO:0011805' 
  'MONDO:0043919' -- 
  'MONDO:0041850'
  'MONDO:0012577'
  'MONDO:0004649'
  'HP:0002105' 
  and they exist as seperate entities 
....

On solution to this might be going over the list of equivalent ids and generating more questions for the rest of the query when crossing from one KG to another

@karafecho
Copy link
Collaborator Author

So, the identifier spreadsheet that I created includes different identifier schemes for each entity. If I'm not mistaken, our original plan was to attach all of them to each ICEES concept, such as 'AsthmaDx'. That way, the transition to ROBOKOP would return a broad range of downstream nodes.

I don't think that additional questions will solve this issue, as any solution should be high-level and query-agnostic. We may want to meet and discuss this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants