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

The NOT qualifier does not seem to appear #95

Closed
kltm opened this issue May 30, 2019 · 3 comments
Closed

The NOT qualifier does not seem to appear #95

kltm opened this issue May 30, 2019 · 3 comments

Comments

@kltm
Copy link
Member

kltm commented May 30, 2019

From @krchristie

1. In the form editor

The NOT qualifier does not seem to appear at all in the form view. There are two annotations to the term 'phasphatidylinositol-4,5-bisphosphate binding' in this model, one without a NOT and one WITH a NOT. However, in the form view you cannot tell the which one has the NOT qualifier. The one that is supposed to have it is the row highlighted in gray; compare to the top row.

20190530-noNOTinForm

Similarly to the Annotation Preview, it would be fine to place the qualifier right next to the 'enabled by' relationship. However, for readability in the curation interface, it would be preferable if it was displayed as rather than <enabled by|NOT> like it does in the Annotation preview.

@krchristie
Copy link

Looks like I left out a phrase in my comment above and I can't edit the above since it was done by @kltm instead of me.

Similarly to the Annotation Preview, it would be fine to place the qualifier right next to the 'enabled by' relationship. However, for readability in the curation interface, it would be preferable if it was displayed as something like "NOT enabled by" rather than <enabled by|NOT> like it does in the Annotation preview.

@tmushayahama
Copy link
Contributor

@krchristie Yes, a little hiccup, I always forget that GP and MF are reversed. I will revise this, but is it ok if I just put it in the new Noctua Form

@vanaukenk @krchristie just to clarify. There is no NOT on the extensions?

@vanaukenk
Copy link

@tmushayahama

There is no NOT on the extensions?

That is correct; there is no NOT on the extensions. The only place the NOT value is used is to negate the GO term in the primary (i.e. unextended) annotation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Development

No branches or pull requests

4 participants