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

Create new rule to prevent propagation of certain terms by orthology/similarity #2106

Closed
pgaudet opened this issue Nov 24, 2017 · 4 comments
Closed
Assignees

Comments

@pgaudet
Copy link
Contributor

pgaudet commented Nov 24, 2017

From @pgaudet on November 23, 2017 12:23

Hello,

Following up on #13004, we need to implement a rule to prevent propagation of GO:0001618 virus receptor activity annotations.

It may make sense to also include other terms - to be discussed with the Virus team at Swiss-Prot.

Copied from original issue: geneontology/go-ontology#14641

@pgaudet
Copy link
Contributor Author

pgaudet commented Nov 27, 2017

Only allow EXP (ECO:0000006) and subclasses in ECO (to confirm with Virus Swiss-Prot group)

@cmungall
Copy link
Member

OK, as discussed on the call, @dougli1sqrd will start with a check that highlights any association to GO:0001618 that has evidence other than subClassOf* of ECO:0000006

@pgaudet pgaudet changed the title Create new rule to prevent propagation of GO:0001618 virus receptor activity annotations Create new rule to prevent propagation of sertain terms by orthology/similarity Nov 29, 2017
@ValWood ValWood changed the title Create new rule to prevent propagation of sertain terms by orthology/similarity Create new rule to prevent propagation of certain terms by orthology/similarity Nov 29, 2017
@ValWood
Copy link
Contributor

ValWood commented Dec 1, 2017

Other terms which maybe should not be propagated
"response to....." (at least high level ones)
from geneontology/go-annotation#1344

@pgaudet pgaudet transferred this issue from geneontology/go-annotation Oct 12, 2023
@kltm kltm moved this to To spec out & prioritize in GORULES (low-hanging fruit) Aug 22, 2024
@pgaudet
Copy link
Contributor Author

pgaudet commented Jan 23, 2025

Current mechanisms (taxon constraints and do-not annotate) are covering this usecase.

@pgaudet pgaudet closed this as not planned Won't fix, can't repro, duplicate, stale Jan 23, 2025
@pgaudet pgaudet moved this from To spec out & prioritize to Wont fix in GORULES (low-hanging fruit) Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

4 participants