Version 1 (modified by vw253, 6 years ago) (diff)


PomBase Planning Meeting 17 Oct 2014

Cambridge - Meeting Room * * Building

Action item review

Outstanding action items carried forward from previous meeting

  • Speak to Eugene to group tracks (aka track hub) (Mark) (Q is there an Ensembl jira ticket for this?)
  • Multiple alignments from Compara Check that i) gap squashing and or ii) dynamic alignment generation for subsets of protein in progress (EG, Q check is there a jira ticket for this)

  • AI: (speed issues) Check progress of trackhub for PomBase?? (EG) (jira ticket?)
  • AI: report onto perl bug synonym type not included (who?) - Reported to Ensembl for fixing.

Action items from

  • AI Val or Mark contact Paco
  • AI check Wilhelm track descriptions are OK Circulate Wilhelm and Marguerat data to Jurg, Sam and Brian for feedback, are all tracks useful? Sam’s data: this is only bigwigs, would bam be useful? Still need track descriptions(Mark/curators)
  • EBI set up dummy confluence (not required, have trac)
  • Mark to draft and circulate an outline of NAR paper contents before the next planning meeting (done & dusted)
  • Ensembl will make annotations propagate over regulates for biological process (follow up: we will need to remove associated text for doing both queries from the Query builder, and update the FAQs)
  • Paul will ensure that that the Ensembl browser developers get the PomBase?? suggestions before the browser overhaul

New (and continuing) Agenda items

  • AI: Document update procedure and time taken (Mark) Done on Confluence (Q how long is this?)

Hosting high throughput datasets

  • None pending at high priority

Priority Jira tickets

  • I have cleared out some of the smaller tickets to V 48, but if they are quick they can be done and closed. As the gene pages are getting longer and longer due to the volume of curated data we feel that it is becoming a priority to address the display of GO and phenotype data and address some of the redundancy in order for the users to be able to consume the data effectively. This should be the next larger project to tackle development wise. Also we should start to add a large volume of multi gene phenotypes in the next couple of months, so the other 2 tickets under the parent PB-1836 (PB-1839 and PB-1840), so we are happy to punt anything else bar critical bugs until these are done.
  • Follow up on the items for Ensembl, are they all raised and in progress?


Usage stats



Phenotype ontology


  • Kim is finalising multi gene phenotypes (and their storage in Canto), many annotation transfer speed ups.
    • We have a large volume of multi gene phenotype data ready to input so this will be the issues to tackle immediately after the compact display. There are related tickets already for how this should look on the gene pages.

Other general issues



Update on community curation

Literature (triage) status

All annotation types

Next priorities



News and Outreach

Next planning meeting