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

Merge terms under 'GO:0000991 transcription factor activity, core RNA polymerase II binding' and children #15798

Closed
10 tasks
pgaudet opened this issue May 25, 2018 · 24 comments

Comments

@pgaudet
Copy link
Contributor

pgaudet commented May 25, 2018

This ticket is replaced by #16053

  • GO:0000989 transcription factor activity, transcription factor binding -> merge into GO:0008134 transcription factor binding (28 manual annotations, excluding ISS)
    BHF-UCL
    MGI
    SGD
    UniProt

  • GO:0000990 transcription factor activity, core RNA polymerase binding -> merge into GO:0000993 RNA polymerase II core binding (21 manual annotations, excluding ISS)
    CACAO, CAFA, FlyBase, SGD

  • GO:0000991 transcription factor activity, core RNA polymerase II binding -> merge into GO:0000993 RNA polymerase II core binding (26 manual annotations, excluding ISS) pombase SGD

  • GO:0000995 transcription factor activity, core RNA polymerase III binding -> merge into GO:0000994 RNA polymerase III core binding (5 manual annotations, excluding ISS) pombase

  • GO:0001076 transcription factor activity, RNA polymerase II transcription factor binding -> merge into GO:0001085 RNA polymerase II transcription factor binding (19 manual annotations, excluding ISS)
    BHF-UCL
    ComplexPortal
    MGI
    ParkinsonsUK-UCL
    SGD
    TAIR
    UniProt
    WB

  • GO:0001132 RNA polymerase II transcription factor activity, TBP-class protein binding -> merge into GO:0017025 TBP-class protein binding (6 manual annotations, excluding ISS) SGD

  • GO:0001181 transcription factor activity, core RNA polymerase I binding -> merge into GO:0001042 core RNA polymerase I binding (9 manual annotations, excluding ISS) SGD

  • GO:0001190 transcriptional activator activity, RNA polymerase II transcription factor binding -> merge into GO:0001085 RNA polymerase II transcription factor binding
    BHF-UCL
    CAFA
    MGI
    PomBase
    SGD
    TAIR
    WB

  • GO:0001191 transcriptional repressor activity, RNA polymerase II transcription factor binding (44 manual annotations, excluding ISS)
    -> merge into GO:0001085 RNA polymerase II transcription factor binding
    BHF-UCL
    CAFA
    ComplexPortal
    FlyBase
    MGI
    SGD
    UniProt

  • GO:0038049 | transcription factor activity, ligand-activated RNA polymerase II transcription factor binding -> merge into GO:0035257 nuclear hormone receptor binding (1 manual annotations, excluding ISS) UniProt

Manual (non-ISS) annotations are here:
https://docs.google.com/spreadsheets/d/1Apv6MiftFCXKHKHVY_ebkZG8PH49PL1HlPsAFW-8LK4/edit#gid=0

There is no action needed if we merge, this is just to check that the merge is OK.

@pgaudet pgaudet self-assigned this May 25, 2018
@pgaudet
Copy link
Contributor Author

pgaudet commented May 25, 2018

@krchristie @ValWood @RLovering @srengel
@vanaukenk @sylvainpoux @ggeorghiou @hattrill @bmeldal @hdrabkin

Can you please have a look before I implement ?

Thanks, Pascale

@bmeldal
Copy link

bmeldal commented May 25, 2018

GO:0000990 transcription factor activity, core RNA polymerase binding -> merge into GO:0000993 RNA polymerase II core binding

Isn't that merging a more general term into a specific child? Are we sure all GO:0000990 annotations were meant to be for RNAPII?

@hattrill
Copy link

A quick glance at the FlyBase ones, I can see that they were probably made in a slightly different spirit - more aimed at capturing that they are regulating transcription but not DNA-binding TFs, I think. Will need a bit of time to review and re-house.

@ValWood
Copy link
Contributor

ValWood commented May 25, 2018

1
I would obsolete
GO:0000989 transcription factor activity, transcription factor binding
and
GO:0008134 transcription factor binding (28 manual annotations, excluding ISS)

and suggest using protein binding terms instead if appropriate, but also checking that they have the correct "general transcription initiation factor activity" or "cofactor activity" (since this is what most seem to be?

If we move them now we will probably need to move them again later. Better to just get them to their final home?

2 GO:0000993 RNA polymerase II core binding

Again, do we need this term. Why not just "protein binding" if demonstrated with the
the correct "general transcription initiation factor activity" or "cofactor activity"

  1. Birgit is correct
    GO:0000990 transcription factor activity, core RNA polymerase binding
    is a polymerase independent term. It should not merge into
    GO:0000993 RNA polymerase II core binding

but again, I think it is confusing to have both the "general/cofactor" term AND a RNA polymerase or TF binding term to describe the same activities. This is why we all got confused in the first place.....

Personally I would obsolete or merge the binding branch into the cognate term in the non binding branch....

@ValWood
Copy link
Contributor

ValWood commented May 25, 2018

  1. so here:
    Annotation review: polIII terms  go-annotation#1734
    I propose to merge these 4 terms into 'GO:0000995' (to be renamed "general RNA polymerase III transcription factor activity", see MF refactor - transcription factor activity #14790

so I just moved all of these this week to GO:0000995 as the new “general RNA polymerase III transcription factor activity” pending the name change.

but here you are saying
GO:0000995 transcription factor activity, core RNA polymerase III binding -> merge into GO:0000994 RNA polymerase III core binding (5 manual annotations, excluding ISS) pombase

I think we need the “GO:0000995 general RNA polymerase III transcription factor activity”

@ValWood
Copy link
Contributor

ValWood commented May 25, 2018

So, I thought we would be getting rid of "transcription factor binding" terms and try to just use the simplified terms relating to your schema ?
If this is the case we don't want to migrate step-wise up the "transcription factor binding" branch.

But if you can unambigously map to the other branch, that would be useful?

@ValWood
Copy link
Contributor

ValWood commented May 25, 2018

Arghh I'm so confused ;!!! ;)

@pgaudet
Copy link
Contributor Author

pgaudet commented May 25, 2018

@bmeldal

GO:0000990 transcription factor activity, core RNA polymerase binding -> merge into GO:0000993 RNA polymerase II core binding

Isn't that merging a more general term into a specific child? Are we sure all GO:0000990 annotations were meant to be for RNAPII?

yes, I checked.

@pgaudet
Copy link
Contributor Author

pgaudet commented May 25, 2018

@ValWood I corrected geneontology/go-annotation#1734
In the end I just renamed GO:0000995 from transcription factor activity, core RNA polymerase III binding -> to RNA polymerase III general initiation factor activity (and doidn't merge the other terms in).

@pgaudet
Copy link
Contributor Author

pgaudet commented May 25, 2018

@ValWood

I think we need the “GO:0000995 general RNA polymerase III transcription factor activity”

This is done, it should trickle through shortly.

@pgaudet
Copy link
Contributor Author

pgaudet commented May 25, 2018

You are right about the final home. For sure that protein binding branch is not really a solution.

First: we don't have a term 'transcription factor activity', so it's really odd to have a precision on that.
What we have is:

  • DNA binding tx factor activity
  • coregulator activity
  • general transcription factor activity.

So if we want to describe what types of protein a protein binds to, it should be to one of the 3. So anyways these will need to be reviewed (this is why I wanted to 'park' them there for now).

I don't know if all the proteins in that list (see Google doc above) can have a home now. I think we're missing the elongation factor. (I can rescue that from the obsoletes). Can you spot anything else missing ?

Thanks, Pascale

@ValWood
Copy link
Contributor

ValWood commented May 25, 2018

I'm still confused

GO:0000995 transcription factor activity, core RNA polymerase III binding -> merge into GO:0000994 RNA polymerase III core binding (5 manual annotations, excluding ISS) pombase

but yesterday:
pombase/curation#2011

Which term do I need (ID) for
"RNA polymerase III general transcription initiation factor activity" ?

@pgaudet
Copy link
Contributor Author

pgaudet commented May 25, 2018

Hi @ValWood
My bad !!! GO:0000995 = will become RNA polymerase III general transcription initiation factor activity

so the merge I propose above is irrelevant.

Thanks for picking that up !

Pascale

@vanaukenk
Copy link
Contributor

@pgaudet
I'm looking through the WB annotations. We have a range of gene products annotated to the terms cited above, e.g. general TFII subunits, obligate heterodimer specific TFs, and bona fide transcriptional co-activators. I'll need to sort through these to see exactly how we should re-annotate.

Wr the general pol II transcription initiation factors, though:
GO:0016251 general RNA polymerase II transcription factor activity
has been restored, right?
To help guide curators, what kind(s) of experiment(s) are sufficient evidence to select this MF term for annotation?

@pgaudet
Copy link
Contributor Author

pgaudet commented May 28, 2018

@ValWood
For GO:0008134 transcription factor binding (28 manual annotations, excluding ISS)
I see 797 direct EXP annotations - are you sure about the 28 ? Also, there are many children to this term, we need to also look at those before obsoleting the parent.

@ValWood
Copy link
Contributor

ValWood commented May 28, 2018

Did I say 28?

@ValWood
Copy link
Contributor

ValWood commented May 28, 2018

I see 251 in QuickGO...

@pgaudet
Copy link
Contributor Author

pgaudet commented May 28, 2018

For GO:0008134 transcription factor binding ?

I see 943 EXP in QuickGO - and still 797 in AmiGO

@RLovering
Copy link

Hi Pascale

I think merging would be great as this will reduce the our annotation workload. However, I also think that as suggested getting the transcription regulator terms available so that people can try to create additional GO terms based on the transcriptional activities would be great, so that people can go through the spreadsheet.

Ruth

@ValWood
Copy link
Contributor

ValWood commented Jun 3, 2018

should
GO:0001190 transcriptional activator activity, RNA polymerase II transcription factor binding instead of -> merge into GO:0001085 RNA polymerase II transcription factor binding (47 manual annotations, including ISS)

(and repressor term)
merge into

https://www.ebi.ac.uk/QuickGO/term/GO:0003713
transcription coactivator activity
Molecular Function
Definition (GO:0003713 GONUTS page)
A protein or a member of a complex that interacts specifically and non-covalently with a DNA-binding transcription factor to activate the transcription of specific genes. Coregulators often act by altering chromatin structure and modifications. The Mediator complex, which bridges transcription factors and RNA polymerase, is also a transcription coactivator. PMID:10213677 PMID:16858867

It seems to fit the definition?

(Rather than the binding term?, or is this for something else?

@ValWood
Copy link
Contributor

ValWood commented Jun 3, 2018

For example Rep2, is a co-activator for MBF transcription factor complex
https://www.ncbi.nlm.nih.gov/pubmed/7588609

with the current proposal there is a loss of repressor/activator specificty

@pgaudet
Copy link
Contributor Author

pgaudet commented Jun 4, 2018

@ValWood how are you trying to annotate Rep2?

@ValWood
Copy link
Contributor

ValWood commented Jun 4, 2018

Actually it isn't a coactivator, it's part of a DNA binding TF complex

but it also binds to another RNA pol II TF as part of the complex. I'm not so bothered about the binding term (we'll capture that with protein binding)

GO ahead with the merge , but when I finish I don't plan to have anything annotated to
"GO:0001085 RNA polymerase II transcription factor binding".....

@pgaudet
Copy link
Contributor Author

pgaudet commented Jul 10, 2018

Annotation guidelines presented at today's annotation call are here:
https://drive.google.com/drive/folders/11KY9lO9gFHa72B3OzWAfHRhVEH6Tbdon

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

No branches or pull requests

6 participants