Page History

De Coronado, Sherri    

Safran, Tracy

Kuntipuram, Kumar

Sprint Status

Current Sprint -  Sprint 52 53 (March 1630, 2017 – March 29April 12, 2017)

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

Working on We are looking at getting 6.5.0 release out.  Our intent is to limit any additional changes besides the fixes in sprint 52.We will have a build for both and 6.4.1.4 and 6.5.0 branches for the fixes put into sprint 52.

LEXEVSREM-60 - This issue works locally.  It was suggested that we build 6.5.0 without this issue instead of waiting for the next build in the next sprint. 

After 6.5.0 release issues are complete, we will working on the following:

• Value Set Architecture
• REST Architecture
• DevOps/Docker work will continue in the background

Data Services

• Bob K. has transitioned from data services to CTS2. 
  
• CTRP was using this service at one point.
• This service is removed in 6.5.0.
• LexEVS 6.4 will remain up for a while in case there are still users that rely on the data services.
  

artifacts as well.  Incorporating a value set resolution issue.

OWL2 Release Update

• Final OWL2 source

Discussion Points:  Loading a candidate now.  Expected release is in May

Discussion Points:

.

Decision Points:

• Testing update
• Install LexEVS admin
• Load value sets with new script

Discussion Points:  Cory validated this as working

Decision Points:

• Cory will update the ticket he created to install the Lexevs Admin on the server, nciws-d790.

Value Set Loading

• Update from Rob - using latest mass VS loader.
• Removal scripts

Discussion Points:

  Indexes weren't being removed when using lbGui to remove value sets.  Rob will create a JIRA item. 

Regarding needs for improved workflow. Can we know what direction value sets are resolved from the NCIt source?  

Decision Points:

Will meet on this later. 

Tree Extensions in 6.5

• UpdateTesting/Validation

Discussion Points:

Decision Points:

Discussion Points: 

• REST Service Architecture

Decision Points:

• Mayo team planning on setting up some meetings to discuss requirements.

• We are preparing to push out recent Tree Extension fixes.
• NCI is trying to get a container on the 6.5 blade for the browser

Decision Points: 

Docker - Next Steps Discussion

Discussion Points:

• Meeting set up for Friday, 2017.03.31
• LexEVS 16X237 Docker Setup
• This discussion will include Jenkins setup.
  

Decision Points:

JSON format for OBO

• Gilberto

Discussion Points:

• The OBO group is working on a JSON representation for OBO.
• This supports JSON and YAML formats.
• Gilberto suggested that Lexevs could potentially create a new loader using this JSON format.
  

Decision Points:

• Gilberto will send out documentation on this to the group.

• Update from recent meeting

Discussion Points: DevOps/QA teams sound like they are prepared to support a CI server for full system test docker script as we are able to work with them on it.

Decision Points:

Discussion Points:

Decision Points:

Mayo Team

• Cory - April 3-5
• Scott - PossibleApril 7
• Craig -

NCI

• Tracy
• Rob