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 extensions: AND or OR #74

Open
pfey03 opened this issue Dec 10, 2018 · 0 comments
Open

GO extensions: AND or OR #74

pfey03 opened this issue Dec 10, 2018 · 0 comments
Assignees
Labels
🚀 enhancement 🌠 go tab Issues related to the GO tab

Comments

@pfey03
Copy link

pfey03 commented Dec 10, 2018

In P2GO, we add extensions >1 for one annotations as AND or OR

AND is separated by a comma: ,
OR is separated by a pipe: |

Attached is the GPAD from QuickGOof gene gflB (Q54L90) EXP annotations, where the long string of extensions for GO:GO:0030837/ negative regulation of Ras protein signal transduction looks all the same and thus somewhat contradictory:
happens_during (response to cAMP)
happens_during (asexual reproduction)
In the file, the last, happens_during (asexual reproduction), is separated by a Pipe thus we should introduce these OR in dictybase.

This dictybase annotation
https://testdb.dictybase.org/gene/gflB/goannotations

Current:
has_regulation_target (rasB)
has_regulation_target (rasC)
has_regulation_target (rasG)
happens_during (response to cAMP)
occurs_at (cell leading edge cell cortex)
happens_during (asexual reproduction)

Possibly, if AND, we should just separate them by Comma (saves also space) and when it's OR, we add the word 'or':

New:
has_regulation_target (rasB), has_regulation_target (rasC),
has_regulation_target (rasG), happens_during (response to cAMP),
occurs_at (cell leading edge cell cortex)
or happens_during (asexual reproduction)

Thus, if column space allows,

  • More than 1 extension can go into one line if fitting into column
  • No line breaks within extension
  • AND annotations separated by comma and a space
  • OR annotations should always start at a new line with the non italic 'or' preceding the relation instead of doing a Pipe
  • Normally there should not be > 1 OR, but I'm not sure. The above rules should apply even if >1 OR

Thanks!

QuickGO-annotations-1544477509162-20181210gpad.txt

@pfey03 pfey03 added 🚀 enhancement 🌠 go tab Issues related to the GO tab labels Dec 10, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🚀 enhancement 🌠 go tab Issues related to the GO tab
Projects
None yet
Development

No branches or pull requests

3 participants