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

GO curation workflow #78

Closed
cthoyt opened this issue Mar 9, 2022 · 0 comments · Fixed by #79
Closed

GO curation workflow #78

cthoyt opened this issue Mar 9, 2022 · 0 comments · Fixed by #79

Comments

@cthoyt
Copy link
Member

cthoyt commented Mar 9, 2022

Here's a rough sketch of what a curation workflow for a GO term might look like

Query

  1. Get GO term as input
  2. Get all genes associated with a GO term and children of GO term
  3. Get all statements (that have text evidence) from a union of several queries
    • Statements between genes
    • Pairs of statements mediated by an unassociated entity
    • Optional - pairs of statements that both have associated genes as subjects but a shared unassociated entity as the downstream target
    • Optional - pairs of statements that both have associated genes as targets but a shared unassociated entity as the upstream controller

Curation

  1. Convert statements to directed graph
  2. Sort edges by importance taking into account potentially several factors
    • Evidence counts (depending on if you want to prioritize curating canonical or potentially obscure biology)
    • Belief score
    • Edge centrality / betweenness centrality
  3. Filter and re-sort by previous curation
    • If a statement has conflicting curations (e.g., both more 1 positive and more 1 negative curation), then it should be curated a third time. These should be put all the way at the top
    • If a statement has been curated positive or negative 2 or more times and doesn't have conflicts, it doesn't need to be curated again.
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

Successfully merging a pull request may close this issue.

1 participant