Page History

De Coronado, Sherri    

Safran, Tracy

Kuntipuram, Kumar

Sprint Status

Current Sprint -  Sprint 56 (May 10, 2017 – May 25, 2017)

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

• CTS2  Build/TestingBroken terminologies
• Moving up the tiers

Discussion Points:

• The latest CTS2 is configured correctly now.
• Jacob is ready to install FINAL on the QA system.
• Scott noticed some broken terminologies.
  
  • Rob mentioned that he restarted the container that should have fixed the issue seen by Scott.
    

• Service is on Dev as a release candidate version.
  
• 6.5.0.FINAL LexEVS Remote API is on Dev, ready to test.
  

Decision Points:

• Kim to test the remote API on DEV when the data is loaded.
  
• Tracy will test the CTS2 service on DEV
• Cory will request Jacob to install the FINAL version of the LexEVS admin and CTS2 on DEV
  

Docker - Next Steps Discussion

Discussion Points:

• Cory was able to pull images from Docker hub and push them into Next sprint, Cory will update the lexevs test scripts to pull the stored versions of software from NCI Nexus server.
• The next step would be to look at making deployable containers in Docker.
  

Decision Points:

Discussion Points:

• There are some logistic issues that we are still working through for this move.  We will investigate further and most likely coordinate this for next weekScott is investigating and testing what the exact changes need to be for updating the DNS.

Decision Points:

Value Set Architecture

• Update

CTS2 REST Calls

• Max to return default

Discussion Points:

• Cory sent out some performance information for how maxtoreturn changes affect the service return times.
• Tested values of 50, 250, 500, 1000
• Larry suggested that many users make these CTS2 calls and expect to get all of the data back at once.
• One example of queries is for "Disease_Is_Stage" (from Bryan in CTRP)
  

Decision Points:

•  We agreed on 1000 as the new value for maxtoreturn.
• Larry will need to add an announcement to our LexEVS 6.5.0 release that the maxtoreturn value has been updated from 50 to 1000.
• This change will go into the 6.5.0 release.

• Scott is currently working on this.  There is a plan to have a meeting next week to review the current work.

Decision Points:

CTRP discussion

• Possible nightly data builds

Discussion Points:

• We discussed that CTRP may need nightly data builds.
  

Decision Points:

• Scott will provide links to CTS2 documentation on how to make changes to the data

Anonymous Nodes Issue

• Kim

Discussion Points:

•  

  Jira
  server NCI Tracker columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 7954a81f-12da-3366-a0ef-97c806660e7c key LEXEVS-2994

• Rob needs an OWL2 loader with the fix by May 30th at the latest.
• This fix would NOT go into lexevs 6.4.1.4. 
  
  • Rob was wanting this in 6.4.1.4 because DATA QA is on Java 7, not 8.
• 6.4.1.4 is being used for PROD loading at the moment.

Decision Points:

• .

LexEVS External Users

Discussion Points:

• ASU
• Preston and team would like to work us and contribute to our Lexevs project, specifically make Lexevs Docker containers to deploy by anyone.
We would set up a new Github project as well as a Docker Hub user to push containersThe LexEVS team is planning on working with the ASU team to set up repositories in the next sprint.

Decision Points:

Mayo Team

• Cory - May 29, June, 5,6
• Scott - May 1929
• Craig - May 26, 29,

NCI

• Tracy
• Rob
• Kim