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

Ensure all relevant Biolink data is getting pulled #8

Open
mbrush opened this issue Sep 19, 2017 · 2 comments
Open

Ensure all relevant Biolink data is getting pulled #8

mbrush opened this issue Sep 19, 2017 · 2 comments

Comments

@mbrush
Copy link

mbrush commented Sep 19, 2017

At present there seem to be a significant number of statements from Biolink that are not making it into the aggregator. One issue is the fact that associations lacking a relation are not pulled, but this should be resolved on the Biolink end soon (see #7).

This is likely not the only cause of the problem, as there are examples of statements that have relations in Monarch. e.g. ALS phenotype annotations have asserted relationship (has_phenotype) but are not returned by tk.bio.

@kshefchek has made a preliminary fix at level of Monarch solr index that is not yet in production - it may be worth setting the beacon aggregator to pull from beta to see if fix propagates from solr through biolink and into the aggregator. We should evaluate once the fix is propagated to tk.bio.

@kshefchek
Copy link

The phenotype issue is likely the casing issue described here: #7

@RichardBruskiewich
Copy link
Collaborator

I'm suspecting some platform timeout issues. I'm close to partially resolving some of these issues. Lo and behold, more data is being retrieved. Once I get the next production prototype out the door, I'll systematically revisit issues such as this to figure out what is going on?

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

3 participants