Closed ValWood closed 9 months ago
Also polysome GO:0005844
Seems to be used sometimes for polysomal fractions, which doesn't seem to be the way to make a GO annotation!
@hdrabkin what do you think about the terms polysome and polysomal ribosome? The seem to be out of scope.
@ValWood , these are fine I think, but just remember my old bugaboo about free ribosomes not being a good term. There are subunits, and they assemble into a functional ribosome on the mRNA during initiation and then stay as a mRNA-bound ribosome during elongation, etc. No free ribsomes; many old experiments were considered to be artifactual (what Mg levels were in the buffer, etc.; I can dig out the literature. ). This is my recollection from years ago when I was at the bench. I see now that there are a couple of terms floating around Free vs bound ribosomes; this is imprecise. There are membrane bound polysomes which put the new protein into the ER during synthesis and then 'free', meaning in the cytosol not associated with a membrane, that are making cytosolic proteins.
@RLovering looks like the 'functional complex is the polysome, but maybe the distinction is not useful? These terms could perhaps be merged.
144 annotations , 97 assigned by CAFA should we obsolete?
polysome is multiple ribosomes on an mRNA
so this is multiple translation events (i.e. a plural?)
this seems really out of scope for GO?
It seems just weird. Wouldn't this be the case for all highly translated genes? It seems to be a different level of component to what we are trying to capture (i.e. this organization is mRNA specific, so it would need to be part_of a messenger RNA, the complexity os including these terms as components is mind-boggling!)
see also https://github.com/geneontology/go-ontology/issues/21143
I agree that this is not functionally a disctint CC than the ribosome, it's just multiple + the mRNA. I agree to obsolete
To be clear, Is the decision to?
Hi @raymond91125 it should probably be an obsoletion in case it has also been sued for elongation factors (I would make it a 'related' synonym, as it's slightly out of scope for GO.) @pgaudet do you agree?
Yes, I agree.
Anyway we dont merge anymore.
If annotations are incorrect, you need to do an obsolete + consider, rather than replace_by.
Thanks, Pascale
I have the following 2 errors in my GO error log:
144 annotations , 97 assigned by CAFA should we obsolete?