How to increase profile [meetings, workshops, software, training, etc]

[Shane Burgess]

"dave burt \(RI\)" <dave.burt at bbsrc.ac.uk> on Wednesday, December 07, 2005
at 4:48 AM +0000 wrote:
2. How to increase profile [meetings, workshops, software, training, etc] 

This is important to increase number of GO annotators, support for further
funding, etc 

Some idea? 

- May 7/10 2006 we will hold the next Chicken genome conference at cold
spring harbor - and we will invite Shane to provide an overview of chickGO
OK

- other meetinsg would be the genome meeting itself at CSH,
Yes, you are right about that


I have just returned from the Conference for reasearch workers in animal
diseases where I spoke with on "GO and immunology" using data from my lab
to illustrate the point. Immediately after I spoke at the first USDA NRI
grant holders compulsory meeting and GO was again featured in the work for
that grant. I will be attending this meeting for at least the next 5 years
so that venue is covered. This meeting is open and I had a lot of people
who are doing functional genomics asking  me about GO (not our disease
work sigh ;-)  ).

- Plant & Animal Genome (San Diego) - we should make a concerted effort to
spread the idea 

I am speaking in the Chicken genome section of this meeting specifically
on ChickGO at AgBase and Fiona is speaking in the Ruminant Section on
CowGO and SheepGO. I am also invited to the speak at the general
proteomics  section and GO will be mentioned there as the fundamental
basis for our Modeling. Of course Jen has her very own GO session. Jen and
I are discussing how we can best integrate this whole thing. Do you all
think that we  could/should push to have a specific GO/Ontology/Annotation
session session at PAG every year? Certainly, given the fundamental nature
of GO (and other ontologies) for modeling functional genomics data (and
even structurally annotating genomes to some degrees), there is a strong
argument here. Especially as proteomics, with a much smaller interest
group, has its own session. Also I plan to speak with the USDA genome
administrators at PAG. 

- so what would be useful would be to share powerpoint slides, make a
common poster - other ideas?
Yes. Susan Fi and I do this routinely send each other our ppts and,
speaking for Fi and I at least, I am very happy to send these to be
archived somewhere "on the www" if it helps all involved.

A common poster would be great. If we hurry I can put it up at PAG.
 
- as part of our grant proposals we will have - travel, training, sharing
of software 
Yes we really need to generate a lot of support , and letters of support,
from the animal and plant communities (in addition of letters of support
from each other). I mention plants here because Dawn Luthe (corn) has been
greatly involved in the money for AgBase and, in the USA at least, plants
have MUCH more access to  money. This one of the reasons why it's "agBase"
and not "LivestockBase". Though having said at AgBase, money earmarked for
a species is spent on that species. This is why chicken is the most
advanced animal, followed by cow.
 
- In addition we should be proactive and enlist those we think will be
interested in this project (either as annotators, users?).
Yes I agree. 

The paradigm that we have here at AgBase is that we provide a service and
port of call for people who are interested in using GO in Ag species.
Also, at AgBase, we think that the communities are too small and poorly
funded to replicate what is happening at , for example, MGI in mouse. So
we are encouraging those PIs who need GO annotations for their genes of
interest, and in situations were we haven't already done the manual
annotations, to manually annotate their genes of interest as experts in
their area of interest. We also hold a database of all papers PMID numbers
that we manually annotate (you just can’t see it on AgBase yet) so that 1.
people don’t have to re-annotate the same papers over and over again
(believe me, no wants to annotate more papers than they need to) and 2. we
can identify papers that can be used in annotation QC. Christine at TAMU
will hold a database for her bovine manual GO annotations and Christine
and AgBase will swap these with each other.Of course we have come full
circle here because people will need to know how to GO annotate. 

So here at AgBase we have a 12 hour long course (we developed this after
Fiona spent two weeks at MGI with Judy Blake’s group). This course is kind
of an expanded version of what Jen is doing at PAG. 

We have run this course on campus here twice and we have it pretty well
ironed out. We have trained about 12 annotators across various species. We
have not had any issues with annotations sent by these people to GOA via
AgBase. I have recently been asked if we can do the same course for others
outside of MSU. I said, that yes we could (in theory). Fiona is speaking
about this at the 1st annual  Biocurator meeting.

At AgBase we are acting at the moment as a kind of buffer for GOA so that
we can answer a lot (all?) of the Agriculture beginners questions in GO
and save the GOA folks for answering our hard questions.


Professor David Burt 
Roslin Institute (Edinburgh) 
Midlothian EH25 9PS, UK 
tel: +44-131-527-4218 
fax: +44-131-440-0434 
[ http://www.ark-genomics.org ]http://www.ark-genomics.org 



Shane C Burgess BVSc(Dist.), MRCVS., PhD.
Department of Basic Sciences
College of Veterinary Medicine
Mississippi State University
Box 6100
MS 39762-6100
USA
Tel:  (+ 1) 662 325 1239
Fax:  (+ 1) 662 325 1031
Email:   burgess at cvm.msstate.edu


Important: Emails that you send may not get to my inbox. Worse, you will
NOT receive a failure notification. I endeavor to answer all emails within
72 hours. If you do not receive a reply, please assume that I never got
your email and re-send it.



Shane C Burgess BVSc(Dist.), MRCVS., PhD.
Department of Basic Sciences
College of Veterinary Medicine
Mississippi State University
Box 6100
MS 39762-6100
USA
Tel:  (+ 1) 662 325 1239
Fax:  (+ 1) 662 325 1031
Email:   burgess at cvm.msstate.edu


Important: Emails that you send may not get to my inbox. Worse, you will
NOT receive a failure notification. I endeavor to answer all emails within
72 hours. If you do not receive a reply, please assume that I never got
your email and re-send it.