Changes between Version 25 and Version 26 of MolgenisAppStories


Ignore:
Timestamp:
2011-11-25T14:49:29+01:00 (13 years ago)
Author:
jlops
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MolgenisAppStories

    v25 v26  
    11= Stories for the LifeLines release of Jan. 2012 =
    2 
    32== As LL team we want to be able to deploy VMs with a basic toolset ==
    4 
    53Scrum: ticket:1068
    64
     
    108
    119== As LL team we want to connect each WOM to the proper VM ==
    12 
    1310Scrum: ticket:1053
    1411
     
    1815
    1916== As LL team we want to provide a Molgenis Research Portal for each study ==
    20 
    2117Scrum: ticket:949
    2218
     
    2622
    2723== In the Molgenis Research Portal, we want to have a Phenotype Matrix Viewer ==
    28 
    2924Scrum: ticket:1050
    3025
     
    3429
    3530== As a user, I want to select a phenotype and a list of individuals in the Molgenis Research Portal and then run a GWAS on the LL geno data ==
    36 
    3731Scrum: ticket:1052
    3832
     
    8276
    8377== As a LL data manager, I want to have a Catalog of the LL phenotype data ==
    84 
    8578Scrum: ticket:1051
    8679
     
    9487
    9588== As a LL data manager, I want to load data from publish layer into EAV (pheno model) ==
    96 
    9789Scrum: ticket:1067
    9890
     
    113105 * Re-factor lifelines packages (it a little bit messy), remove old not used code anymore and place in descriptive packages
    114106 * Remove JPA dependencies
    115    * Many-to-many in JPA are not working properly with Labels, for example ov.setTarget_Name("x"). In JDBCMapper this is solved, but know not where and how we could best do this for JPA. This set by label should also be put into generated test.
     107   * Many-to-many in JPA are not working properly with Labels, for example ov.setTarget_Name("x"). In JDBCMapper this is solved, but know not where and how we could best do this for JPA. This set by label should also be put into generated test
     108   * Remove change org.molgenis.[wiki:JpaDatabase] interface to prevent this 
     109   *         //trick to prevent compilation problem in Hudson, should be changed! 
     110   *        this.em = ((!JpaDatabase)db).getEntityManager().getEntityManagerFactory().createEntityManager();
    116111 * Update CSV readers to be multi threaded?
    117112 * In (production) environment it's not a bad idea to put the java executable in the Oracle VM that part of the database.