You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In their 2019-Nov release UniProt has made changes that allow several statements to be made specifically on isoforms/fragments/cleavage products associated with a full UniProt "protein" entry sequence, see https://www.uniprot.org/news/2019/12/18/release.
Clearly, many UniProt entries must now be considered as containers of subentries with associated statements, creating the need for separate WD items, which can be recognized by being instances of isoform (Q609809), protein variant (Q77030030), or protein fragment (Q78782478). I expect Gene Ontology moving to annotation of subentries in the future, as well.
This is why I would ask you to improve the bot, so that it recognizes or creates items that are of the above type AND that are part-of the parent protein entry, changing its behaviour accordingly, e.g. updating the sub-item not the main item.
The text was updated successfully, but these errors were encountered:
In their 2019-Nov release UniProt has made changes that allow several statements to be made specifically on isoforms/fragments/cleavage products associated with a full UniProt "protein" entry sequence, see https://www.uniprot.org/news/2019/12/18/release.
Clearly, many UniProt entries must now be considered as containers of subentries with associated statements, creating the need for separate WD items, which can be recognized by being instances of isoform (Q609809), protein variant (Q77030030), or protein fragment (Q78782478). I expect Gene Ontology moving to annotation of subentries in the future, as well.
This is why I would ask you to improve the bot, so that it recognizes or creates items that are of the above type AND that are part-of the parent protein entry, changing its behaviour accordingly, e.g. updating the sub-item not the main item.
The text was updated successfully, but these errors were encountered: