Sprint Status
Current Sprint - Sprint 56 (May 10, 2017 – May 25, 2017)
16X237 Agile Development - Sprint Status#16X237AgileDevelopment-SprintStatus-Sprint56
- CTS2 Build/Testing
- Broken terminologies
- Moving up the tiers
Discussion Points:
- 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.
- Rob mentioned that he restarted the container that should have fixed the issue seen by Scott.
Decision Points:
Docker - Next Steps Discussion
Discussion Points:
- Cory was able to pull images from Docker hub and push them into NCI Nexus server.
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 week.
Decision Points:
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.
Anonymous Nodes Issue
- Kim
Discussion Points:
-
- 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:
- After QA is setup, Jacob will set up DATA QA to run Java 8 and the 6.5 loader.
- NCI team will determine the best plan for configuring DATA QA.
- Scott will start looking at this issue and make changes in 6.5.
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 containers.
Decision Points:
- Larry and Margaret are in agreement that we should collaborate with Preston and his team to develop LexEVS deployable Docker containers.
Mayo Team
- Cory - June, 5,6
- Scott - May 19
- Craig
NCI
- Tracy
- Rob
- Kim
