April 2013 GMOD Meeting
Friday 5 April, 9:00-17:00
Saturday 6 April, 9:00-16:00 (or until all topics have been covered)
Meeting location: the Hauser Forum, Cambridge, UK
Archived tweets from the meeting
Contents
Agenda
Friday 5th April
State of the GMOD Project, including GBrowse and Chado updates (Scott)
GMODsurveyome redux (Amelia Ireland)
Community Building and Maintenance (Dave Clements)
Open Ash Dieback Project (Dr. Kentaro Yoshida of The Sainsbury Lab)
The Open Ash Dieback project, an exciting (and vital) effort to gain insight into ash dieback, a chronic fungal disease of ash trees. Ash dieback is caused by a fungus, Hymenoscyphus pseudoalbidus, and is characterised by leaf loss and crown dieback in infected trees. Ash dieback has already caused significant damage to tree populations in northern Europe and was recently discovered in the UK. The Open Ash Dieback project embraces the new paradigms of open science and crowdsourcing by making all its data public and asking scientists to analyse genetic data from ash and the fungus.
More information and media coverage of OADB:
- Paper: Crowdsourcing genomic analyses of ash and ash dieback – power to the people
- Scientists crowdsource to decode genetic code of ash dieback fungus - from The Guardian
- Open Science versus Ash Dieback
iAnn collaborative announcement dissemination (Manuel Corpas)
Drupal at EBI (Joseph Rossetto/Bren Vaughan)
Galaxy Project Update (Dave Clements)
Saturday April 6th
FlyBase update (Josh Goodman)
WormBase - some notes on running a MOD in the cloud (Todd Harris)
What the Gene Ontology can do for you (Jane Lomax)
Tripal (Stephen Ficklin)
TAIR PLAIN (Bob Muller)
Using CAS-Utils (Community Annotation System Utilities) in real life (Emmet O'Brien)
Demeter: A data-harvester for biological sources (Alex Kalderimis)
Banana Genome Hub (Delphine Larivière)
Galaxy CloudMan Workshop (Dave Clements)
Remote Attendance
Saturday 6th April: https://meetings.webex.com/collabs/#/meetings/detail?uuid=IAGLKVBIA8I661U6ZAQFISZNV2-9RCJ
Meeting Assessment
Please fill out the meeting assessment so that we know what worked well and what needs improvement for next time.
