Menu
▾
▴
1 Attachments
#869 editing an allele in exisiting session
This might be OK, but I wanted to note it.
I changed an allele of cdc2 in an existing session to standardize it.
See screenshot cdc2-1w gene page
cdc2.1w is the same as cdc2-1w so I changed to -1w which is used on the rest of the page
The edit seemed to go OK, except in the title
New phenotype annotations fro this session...
it is still called SPBC1B10.09-cdc2.1w
(see screenshot cdc2-1w)
screenshot
and its still .1e in the table
http://curation.pombase.org/pombe/curs/1cf6a37d7872772f/ro/
Sorry, I don't understand this. Let's talk about it next time we chat.
I get it. Val has changed the name for an allele, but that didn't change the name of the corresponding single-allele genotype.
It might be a bit clearer if you look at the genotype details:
http://curation.pombase.org/pombe/curs/1cf6a37d7872772f/feature/genotype/view/5/ro
Ah, thanks. Currently the allele has name and the genotype has a name and they are stored separately. Changing the name of an allele of a genotype won't change the genotype name.
Definitely not essential for unleashing to the community, but this behavior would be nice:
Don't change a user-specified genotype name unless that field is explicitly edited (accept "my cool genotype" --> "the coolest genotype ever", but don't change the name upon "yfg1.17" --> "yfg1-17").
For a genotype that's just been added in a session, but not named by the user, do update an automagically-generated genotype name when any of the allele names from which it's built are changed.
Warn if an allele used in an existing genotype gets renamed. (We might have to think this one through a little more fully than I have just now.)