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


What is the status of Paco's data?

  • AI Val contact Paco

What is the status of track-hub? This will not happen in the near future, will be done at some point in the future by Ensembl

  • AI Create jira ticket to ensure this is working correctly when it happens

What is the status of on the fly multiple alignments from Compara (for gap squashing etc)

  • AI Create jira ticket for PomBase? curators to ensure this is working correctly when it comes through to PomBase?

What is the status of storing ontology synonym scope in Ensembl

  • AI Mark will find out the details of the Bio-perl module that is used
  • AI Val will contact author to see if synonym scope can be included
  • AI Ticket will be raised with Ensembl to include synonym scope when option is avaiable

What is the status of Sam's data

  • AI Ask Sam for feedback, Jurg will follow up with Sam

What is the status of ensuring that Ensembl ensuring that annotations are transitive over the "regulates" relationship for biological process?

  • AI Somebody (who?) will create a ticket (where?). We will also need a PomBase? jira tracker ticket for this to list the changes which will need to happen PomBase? side when this is in place (mainly test on query builder and documentation)

Discussion- if Ensembl do this in a generic/modular way it will also provide a solution for but this might not be possible....

PomBase? browser suggestions

  • AI Paul will ensure that PomBase? browser suggestions are forwarded to the new point person before browser overhaul begins

Exporting FYPO and GO IDs in GenBank? and EMBL export files

  • AI Dan will remove the PomBase? IDs from this file

Can centromere features be visible in the "detail view" AI Mark will create jira ticket

Q How long is a PomBase? build taking from start to finish A Approximately 2-3 days. It takes about 0.5 days of Mark's time

Q Should we be combining experimental tracks for repeats in the browser track displays

  1. General consensus was yes. Users will be able to refer to publications for details of how the tracks were combined. Only change to track labelling will be to add "combined" or "consensus"

AI Midori Update any of the submission documentation, and the wiki page which details track descriptions (note: I don't know if this is the right page, its the only one I could find)

EsyN, Val described that various link outs will be needed from the "GO slim" and the physical and genetic interaction sections of the gene pages. AI Val will open a jira ticket once the teething problems are overcome and the URLs are available ( I will circulate for feedback first).

New high-throughput data, upcoming dataset from Runge lab

  • AI Mark will contact authors with ftp upload details and check file formats

Discussion about display of variation and phenotypes for 50+ wild strians in Ensembl.

  • AI EG are keen to host this. Dan Jeffares will submit data.

We spent some time going through Marks mockups of the compact view for phenotypes and GO.

  • AI. Mark to make additional mockups based on discussion outcome