Changes between Initial Version and Version 1 of PombasePlanningMeetingAgenda20120126

Jan 26, 2012, 7:17:54 PM (9 years ago)



  • PombasePlanningMeetingAgenda20120126

    v1 v1  
     2 == Action items from technical meeting ==
     4Incomplete actions from technical meetings are included with new issues below
     7== Action items carried forward from 3rd October planning meeting ==
     9 * Need to coordinate dataset for regular public release with Ensembl genomes release cycle after the preview (Kim/Mark/Dan)
     11 * FYPO will be submitted to OBO foundry shortly which should trickle through to OLS in due course (Midori)
     15 * Ensembl group tell us which format specification for various HTP datasets. Val will draft an announcement to be approved by Paul/Mark/Dan
     19 * Load external GO data into Chado as a priority (Kim)
     20  * GO data is now loaded, but filters are not implemented (complicated by annotation extensions. Kim will prioritise this when he starts back in October)
     22DONE and filters implemented, waiting for data to filter through to check but sounds promising based on numbers
     24 * Follow up desktop sharing software (circulate possibilities, do free trial?) (Midori)
     26Carried Forward
     28 * Ask Henning Hermjakob about possibility of OLS as webservice to attach annotations to, we will have the next planning meeting at Hinxton and see if Henning can join us for a while.
     30Carried Forward
     32== General ==
     34 * Usage stats
     36 * pombelist posting from Bioneer (val)
     38 * OriDB (val)
     39  From Conrad Nieduszynski: The database is SQL based. There is a low tech browser as part of OriDB and all of the data is available for users to either download or to visualise in genome browsers as custom tracks. Let's look at how to share the data. (Conrad has evaluated the origin datasets and classified origins)
     41 * RT: Curators have agreed on a procedure for handling helpdesk queries (brief report) (Val)
     42   * Outline procedure/ immediate response
     44 * FAQ: Drupal module now deployed. Common helpdesk queries will generate FAQ entries as needed. (Midori)
     46 * Versioning, need somewhere where we can see which Ensembl and which Chado data version is currently displayed on dev and www (and what is the current Chado version)...Midori suggest how this should happen (automated...)
     47  * See also (Midori)
     49 * curation tool sub domain (Kim) (AI from 1st October, notes Mark hasn't heard anything yet. Needs input from Paul, and probably will involve EBI External Services)
     51 * Intermittent speed issues (as reported by Robin Allshire (Midori)
     53 * Any progress on setting up focused user testing? (AI from 1st Oct)
     56== Review "post-preview" criteria & progress ==
     58=== Search issues ===
     61 * Document what Simple Search searches; also Advanced Search keyword filter (should be quick)
     62 * Curators test fixes Mark has done to address serious Advanced Search problems
     63  *
     64  *
     65  *
     66 * Mark make changes discussed in curator meeting 24th Jan.; then curators test
     67  *
     69=== Blast related ===
     71  * Blast giving no hits for some searches (val)
     72  * Difficult to link output back to genomic regions based on descriptions provided
     73   * (val)
     75=== Misc Data problems (wrong/missing data) ===
     77  Unlikely to discuss any of these in detail, just wanted to flag them
     78  *  GO slim related (Val)
     79  *  Status totals discrepany (Val)
     80  *  Curated ortholog display, wrong data (Val)
     81  *   Incorrect numbers for "others" links (Val)
     83== Tasks before GeneDB decommissioned ==
     85=== Ensembl related ===
     88=== Blast related ===
     90   * Blast is incredibly slow by comparable MOD standards. Could we have a !PomBase-specific Blast queue?
     91 (val)
     93   * Blast option, Databases (val)
     95   * Blast results presentation (Midori) Needs jira items linking
     96    * find 'run' button
     97    * results on one page (exists, but not on main results page, and link is barely detectable)
     98    * better links to results
     99    * improve descriptions
     100    * karyotype map
     103=== Misc Data problems (wrong/missing data) ===
     105  Unlikely to discuss any of these in detail, just wanted to flag them, there may be a few other items but these seem fairly straightforward.
     106  *  Missing data sno/snRNA (val)
     107  *  Missing data for protein sequence features (Val)
     110== Things which are not crucial for preview removal, or GeneDB decommissioning but we would like to discuss , if time permits ==
     112=== Usability issues/ issues reported by users ===
     114   * problems switching on tracks (like ESTs) is very cryptic (val)
     115    * when tracks are enabled they will be visible on gene page context map (val I would definitely like to touch on this one briefly even if none of the others)
     116    * Discussed with Mark on 24th; Val raising tickets to go to Ensembl group; !PomBase to try linking to "location" tab from gene pages
     118  * Ability to browse left and right in browser is only available in "location" tab
     122=== Integration (Better integration between the Ensembl part of the site and the Gene pages) especially: ===
     124    * Linking between the browser and the gene pages (discuss button option  position/size/text etc)
     126    *  curator contact
     128    * tools
     129      *
     130      Q are all of these tools relelvant?  remove which are not, add relevent ones to Pombase tools menu
     132    * helpdesk/help
     133      * The "Ensembl help" link leads to a general help page for Ensembl genomes, this won't mean much to our users
     134      * We need an intermediate Pombe specific help page under  PomSase needs to be Pombase specific (it can include items here which are relevant to Pombase but should exclude items which are not related to Pombase (e.g. eHIVE production system for honeybee,  Annotation of Ig/Tcr Segment Genes, and other links in jira item)
     136    *  download
     138       * Need an intermediate page for site wide download options linked from main page menus
     140General note for all of the above, it is important that we remove things which are net relevant. There are so many new  and hidden features that users should only be presented with the relevant items or they will stop exploring.
     143    * search
     145    * Entry level text
     147== AOB ==
     149 * next technical meeting?
     151== Lower priority so bump to next meeting ? ==
     153 * Re-visit Online Meeting software
     155 * AmiGO2 demo
     156  * Need to contact Chris and Seth to make sure stable URL for meeting
     158Notes: AmiGO2 is generic and can support other ontologies. To get the cool axial, drill down search/filtering working it involved the use of Solr indexes? which need to be built but Chris says it should be relatively straightforward to implement. This should fulfill our requirements which are not met by other available tools (i.e the ability to provide links to gene product at different levels of the heirarchy). It also handles x-products.....
     160I'll put this for discussion, demo at a future planning meeting. (Quickgo issues include: different gene product names and IDs; only protein; not representing all annotation; how are term names displayed and accessed; update frequency )