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

Is GOOSE still being updated? #509

Closed
pgaudet opened this issue Jun 7, 2018 · 3 comments
Closed

Is GOOSE still being updated? #509

pgaudet opened this issue Jun 7, 2018 · 3 comments
Assignees
Labels

Comments

@pgaudet
Copy link

pgaudet commented Jun 7, 2018

Hello,

When I run this query in GOOSE (corresponding to GORULE:0000008):
SELECT gene_product.symbol,
CONCAT(gpx.xref_dbname, ':', gpx.xref_key) AS gpxref,
IF(association.is_not=1,"NOT","") AS 'not',
term.acc,
term.name,
term.term_type,
evidence.code,
db.name AS assigned_by
FROM association
INNER JOIN gene_product
ON association.gene_product_id = gene_product.id
INNER JOIN dbxref AS gpx
ON gene_product.dbxref_id = gpx.id
INNER JOIN term
ON association.term_id = term.id
INNER JOIN evidence
ON association.id = evidence.association_id
INNER JOIN db
ON association.source_db_id=db.id
WHERE evidence.code = 'IEP'
AND term.term_type != 'biological_process'

I get 0 results in GOOSE, but there are 47 annotations according to AmiGO.

Any idea why there is a discrepancy ?

Thanks, Pascale

@kltm
Copy link
Member

kltm commented Jun 7, 2018

No rules should use the SQL--it is no longer supported.
geneontology/helpdesk#4
It may be sporadically updated, but may no longer fit many use cases.

@kltm kltm closed this as completed Jun 7, 2018
@kltm kltm added the question label Jun 7, 2018
@pgaudet
Copy link
Author

pgaudet commented Jun 7, 2018

This wasn't really about the rules - it was about the fact that if the SQL is not supported, it shouldn't be available at all - or is there a reason to keep it, if the data returned are incorrect ?

@kltm
Copy link
Member

kltm commented Jun 7, 2018

There are plans to remove it from service, but we are in the transition period now and premature removal would likely cause more issues for users.

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

No branches or pull requests

2 participants