-
Notifications
You must be signed in to change notification settings - Fork 7
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
cant edit annotations #2815
Comments
or this one but some, I could cc @PCarme |
I just tried to add an annotation in c56a652b8b068e66 and that worked (I removed it afterwards). Which term were you trying to use in the annotation and which ontology was it? |
i was trying to add |
There are some edit buttons greyed out for annotations that are part of genotype-genotype interactions: Changing the genotype would change the interaction in those cases. |
I also had this problem with phenotypes of genotypes involved in multi-locus interactions yesterday. Even for phenotypes that are not involved in the interactions themselves. I had to remove the interactions to be able to edit them. |
in this case I'm trying to change the annotation not the genotype, and the specific annotation isn't used in an interaction. |
In the database it is using the whole annotation because the interactions with a phenotype need the term and extension as well as the genotype. So the whole annotation referenced by the interaction: We decided to prevent editing in this case so that changes to the genotype annotation wouldn't change the interaction: Let's talk about this on Friday. |
Oh actually I see that actual phenotype is used. |
Clicking on edit will give a message "changes to this annotation will change xx genetic interactions that it refers to" |
This annotation should be editable: |
I've deployed that change. Let me know if there are any problems. |
Seems to be working for me. |
Thanks for testing. I'll close this and we can open new issue if there are any bugs. |
in this session to add new terms?
pombe/curs/c56a652b8b068e66
The text was updated successfully, but these errors were encountered: