Annotation Conf. Call August 27, 2013: Difference between revisions

From GO Wiki
Jump to navigation Jump to search
Line 18: Line 18:
!DB (Col 2)
!DB (Col 2)
!GO ID (Col 5)
!GO ID (Col 5)
|ev.code
!ev.code
!Reference (Col 6)
!Reference (Col 6)
!Extension (Col 16)
!Extension (Col 16)

Revision as of 16:47, 23 August 2013

Agenda

Mailing lists, SF tracker etc

Val asked me (Rama) to give a refresher on where one should post what messages/questions. The following is what I have so far.

  • SourceForge- for ontology term requests, annotation issues (mappings mostly)
  • GO Help desk- when you dont know how to get some data, report something is not working (like AmiGO or the website)
  • Mailing lists- make announcements, ask annotation related questions (which evidence code etc)
  • Seth et al are using github to collect AmiGO2 bugs (https://github.com/kltm/amigo/issues), but if you can't find this URL, feel free to send email to go-help or post a message on go-consortium mailing list

Annotation Extension exercise

  • Paper 1: PMID 8384702 (Title: MAP kinase-related FUS3 from S. cerevisiae is activated by STE7 in vitro).

Annotation Extension to be discussed for the MAP kinase activity annotation for FUS3. GO annotations for FUS3- http://www.yeastgenome.org/cgi-bin/GO/goAnnotation.pl?dbid=S000000112

DB (Col 2) GO ID (Col 5) ev.code Reference (Col 6) Extension (Col 16)
GO: IDA PMID: has_


  • Paper 2: PMID 10882066 (Title: Cohesin's binding to chromosomes depends on a separate complex consisting of Scc2 and Scc4 proteins.)

Annotation extension to be discussed for the term establishment of protein localization to chromatin (BP) for SCC2 gene. http://www.yeastgenome.org/cgi-bin/GO/goAnnotation.pl?locus=scc2