Changes between Version 2 and Version 3 of PombasePlanningMeetingAgenda20130318


Ignore:
Timestamp:
Mar 16, 2013, 11:32:07 AM (9 years ago)
Author:
val_wood
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PombasePlanningMeetingAgenda20130318

    v2 v3  
    1313 == New Agenda Items ==
    1414
     15From Mark,
     16This will probably cover many of the items below:
     17
     18     * Present the stats for the difference between the stage site now
     19      and the live site as it was when we were having trouble.
     20          o Talk about the use of Monitor.us (Starter pack is $7.50 per
     21month and can select 3 locations by country (US has 5 of those
     22locations) (25 listed), actual location not listed.)
     23          o See if it is possible to set something up in Cambridge.
     24          o Looking at converting the python Selenium tests into Java
     25and then working on expanding the tests that are run.
     26
     27    * Got the data on Thursday (7th March).   I had started working on
     28the ontology db and loading that so they could get the release to us.
     29I have been able to perform the updates and reload the core and ontology
     30a couple of times to fix a few bugs.   v33 is now on the test
     31genomebrowser.  I have initiated the stage.pombase.org Drupal server to
     32rebuild the JSON cache.   I have also rebuilt the ontology database.
     33If everything is working and the stats look fine we should be able to
     34start to push through to dev on Tuesday and then hopefully on to live on
     35Wednesday.
     36      Given the manual run through that I have just done; Val and Kim
     37are you happy going forward with the timeline that I'll take the latest
     38release on the 1st Monday of the Month and then go for release on the
     39third Monday?   This gives two weeks for the updates and then do the
     40release on a Monday rather than a Friday?
     41
     42    * After going through a full release manually I have noted down the
     43proceedure I followed, along with subsequent updates.   This now needs
     44to be formalised and packed in an automated fashion along with
     45regression testing. My target is to focus on this after the release and
     46hopefully have a pipeline ready for the next meeting.
     47
     48    * With automation I need to work on the dumping scripts for the
     49stats.   These should come in soon after having the main pipeline
     50generated and then I can just plumb them in accordingly.
     51
     52
    1553  * update on speed and page loading
    1654  * Update on regularity of updates
    1755 
    18   * We are now showing version 31 from *** (324 fully curated publications)
     56  * We are now showing version 31 from 19 December (324 fully curated publications)
    1957    * V32 was skipped because version 31 hasn't gone live (330 fully curated publications)
    20     * V33 (535 fully curated publications) is on stage
     58    * V33 (7th March) (535 fully curated publications) is on stage
    2159   
    2260
    23   * Progress implementing the RNA/protein expression data from Sam's paper (now tabled for V 34, need to load into Chado and get display on gene page sorted)
     61  * Progress implementing the RNA/protein expression data from Sam's paper
     62    * (now tabled for V 34, need to load into Chado and get display on gene page sorted)
    2463
    25  
    2664
    2765  * Update on gene  name synching (e.g.  why is mre11 still called rad32…was changed in early November?)