NIH | National Cancer Institute | NCI Wiki  

Error rendering macro 'rw-search'

null

Versions Compared

Old Version 1

changes.mady.by.user Unknown User (endlecm)

Saved on

compared with

New Version 2

changes.mady.by.user Unknown User (endlecm)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Sprint Status

 

Current Sprint -  Sprint 50 (February 16, 2017 – March 1, 2017)

16X237 Agile Development - Sprint Status#16X237AgileDevelopment-SprintStatus-Sprint50

DEV Server Configurations

  • Planning and usage discussion

Discussion Points:

  • Dev blade for CentOS 7 being created - will be used for java 8, MySQL 5.6 (6.4/5 release)
  • VM (snapshot) blade server for Mayo (CentOS 6) pointing to MySQL 5.6
    • Mayo team requested remote API, URI resolver, CTS2 service containers on there as well.
  • The Browser team will want to test our Java 8 LexEVS release once we install on Mayo Dev.

Decision Points:

Validate that Tomcat 8 works with our Java 8 release.

LexEVS Java 1.8 & MySQL 5.6 Environment

  • MySQL update

Discussion Points:

Scott's tests on MySQL 5

.

6 show that performance is as good (and better in some cases).

Decision Points:

6.4.1.3 Snapshot build update

  • Creating 6.4.1.3.FINAL

Discussion Points:

  • Additional loader enhancements/fixes don't need to go into 6.4.1.x. 
  • They can wait until the Java 8 release.
    • The NCI dev team can use the Java 8 release of LexEVS to

    Decision Points:

    Value Set Loading Enhancements

    • Status from RobUpdate

    Discussion Points:

    • The additional fix from Scott will need to go into the 6.4.1.x release.
    • Rob/Tracy mentioned that testing with the Value Set load script from Scott, was done with OWL2 and never completed successfully.

    Decision Points:

    CTS2 RESTful documentation

    Discussion Points:

    • The Mayo dev team will look into the different query requests and see what options there are
    • Calls to return the results - are there limitations?
    • Filter down - use a programming language to parse JSON and make subsequent calls.

    Decision Points:

    • Cory will respond to the team with what is possible with CTS2 REST calls for the given examples.

    Lexevs Version/Naming Discussion

     

    		CTS2 RESTful API questions

    Discussion Points:

    Decision Points:

    • The Mayo team will investigate tools to auto-generate CTS2 RESTful API
    LexEVS External Users

    Discussion Points:

    None

    Decision Points:

    Proposed Backlog Review Items

    Discussion Points:

    Decision Points:

    Team Absences

    Mayo Team

    • Cory -
    • Scott -
    • Craig - March 6-13

    NCI

    • Tracy
      • March 9-17
    • Rob

      • March 20-24

    ...