NIH | National Cancer Institute | NCI Wiki  


Wright, Larry NIH/NCI  x
Fragoso, Gilberto NIH/NCI    x

De Coronado, Sherri    


Safran, Tracy

Ong, Kim L
Lucas, Jason R
Bauer, Scott  Mayox
Stancl, Craig
Endle,  CoryMayox
Sharma, DeepakMayo 
Wynne, Robert    NIH/NCI [C]x
Tran, Tin    NIH/NCI [C] x
Carlsen, Brian NIH/NCI [C] 
Wong, Joanne NIH/NCI [C] 

Kuntipuram, Kumar


Action Items

AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus


  • Sprint 37
  • Sprint 38 Planning
  • LexEVS 6.5 planning
  • On going Support
  • Sprint 37 
  • Sprint 38 Planning
  • LexEVS 6.5 planning
  • On going Support
  • Sprint 37
  • Sprint 38 Planning
  • LexEVS 6.5 planning
  • Sprint 37
  • Sprint 38 Planning
  • LexEVS 6.5 planning
  • Agile Admin


LexEVS External Users

Sprint Status


Current Sprint  Sprint 37 (August 18, 2016 – August 31, 2016)

LexEVS S13-500 Agile Development - Sprint Status#SprintStatus-Sprint37

6.4.1 Testing on Dev and QA

  • QA Verification Process

Discussion Points:

  • 6.4.1 is deployed on QA.
  • 6.4.1 was not deployed/tested on DEV.
  • QA tier is configured for HTTPS
  • HTTP requests against the remote API are working.

Decision Points:

6.4.1 Lexevs remote API HTTPS discussion

  • Discuss NCI QA setup on Apache

Discussion Points:

  • HTTP requests against the remote API are working
  • HTTPS requests against the remote API are throwing exceptions.
  • The remote API service accepts a valid, signed certificate, not a self signed one.
  • At the morning meeting, NCI suggested that we could remove our HTTPS security in the remote API.
  • Mayo team suggested we dig into this a bit more to see what the problem is.
  • Larry/Jacob suggested that Apache should handle the security rather than the remote API.
  • Scott is wondering if the certificate on QA is a valid, signed certificate. If it is, then the remote API should work fine.

Decision Points:

  • Mayo team will work with Jacob to understand the root problem and determine if our HTTPS fix is the cause of the issue.
  • Scott/Cory will deploy 6.4.1 lexevs-remote API to DEV to see if DEV behaves similar to what the problems are on QA.
    • Tin is deploying 6.4.1 to DEV now. (No need for Mayo to install now).
  • Mayo team will discuss the 6.4.1 QA deployment with Jacob to better understand the HTTPS issue.

OWL2 Loader Discussion

Discussion Points:

  • Mayo team asked what NCI's priority is on implementing a fix for this issue.
  • This issue is seen in our 6.4.1 codebase.
  • A fix would be created and released as and could be pushed up the tiers similar to all of the other loader fixes we have done.

Decision Points:

  • We will work on this issue after the 6.4.1 HTTPS issue is resolved.

HTTPS document review

  • End user communication update

Discussion Points:

Decision Points:

NCI Jenkins Plan/Configuration

Discussion Points:

  • Toky had configured Jenkins at NCI for LexEVS.
  • No one has continued this work.

Decision Points:

  • Mayo team will contact Sarah Elkins to work with Jenkins set up at NCI


CTS2 over RMI

  • Future Need

Discussion Points:

  • It was mentioned that some clients at NCI may be using CTS2 over RMI.
  • The Mayo team has updated the code to make this work.
  • Gilberto/Tracy suggested we disable this feature and see if anyone is using it.

Decision Points:

  • Mayo will create a JIRA item to remove/hide this feature.

NCI Nexus Server

  • Mayo to migrate to NCI's server

Discussion Points:

  • Cory/Deepak met with Sarah Elkins and she discussed options on how to move the lexevs jars to NCI's maven repository.
  • Craig mentioned that the Mayo team has until the end of September to move from our Nexus server to NCI's.

Decision Points:

  • Cory will work with Sarah in the next Sprint to start moving jars to NCI's Maven repository

LexEVS External Users

  • Alexander

  • Our fix worked for Alexander.
  • Scott is working with him on his coding scheme mapping issues.

Multiple Loads at the same time

  • LEXEVS-2253 - Getting issue details... STATUS
  • This is a feature request.


Discussion Points:

  • Rob/Tracy are requesting the GUI to do multiple loads of different coding schemes at the same time.
  • Scott mentioned there are some restrictions with multiple JVMs and locks on the file system.
REST CTS2 DiscussionCraig will look to set up a meeting to continue this discussion.
Team Absences

Mayo Team

Deepak - Sept 2-5

  • Cory - Sept 5, Sept 8-9
  • Scott -Sept 5
  • Craig - Sept 5


  • Rob Wynne - Sept. 1-5

JIRA Issues

Recent LexEVS Related Bugs and Features (within last week)

Key Summary T Created Reporter P Status Affected Version/s Fix Version/s

Recent CTS2 Service Related Issues (within last week)

Key Summary T Created Updated Due Assignee Reporter P Status Resolution

6.4 LexEVS Related Issues

Key Summary T Created Updated Due Assignee Reporter P Status Resolution

6.4 CTS2 Service Related Issues

Key Summary T Created Updated Due Assignee Reporter P Status Resolution

Project Plan Changes

#DescriptionDue DateResourcesNotesRisksMitigation

 Planned Activities

Area of InterestDetails

Risks, Issues, Dependencies


Opened DateDue DateDescriptionLikelihood (H, M, L)ImpactAssignedStatusMitigation Strategy


 #Opened DateDescriptionImpactAssignedStatus


Opened DateDescriptionAssigned


Action Item Backlog

 #AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
64ScottTo follow up on URI's on OWL2 with Harold.   on hold
164CoryCory to add implementation to CTS2 implementations page.2014.04.30  on hold
197ScottDo a gap analysis on what the URI_Resolver logs and what NCI would like to know from these logs2014.6.18  on hold
200Larry/SherryQuery current LexEVS users about use of SOAP, REST or QBE services in the legacy caCORE api's2014.6.18  on hold
207CoryWrite issue against CTS2 OMG regarding the ability to return INACTIVE concepts only.2014.07.30  on hold
210Larry/GilbertoDetermine if there is a need to meet with the CTRP2014.07.30  on hold
212LarryInclude LexGrid XML Export as part of the 5.1 retirement notice. 2014.07.30  

on hold

224ScottURI Resolver - Provide overview of how to access the URI Resolver2014.09.03  

on hold

225ScottURI Resolver - Look at TLAMP and VSAC service to determine usage of URI Resolver2014.09.03  on hold
244CraigPlan meeting with Tracy to discuss collaborative LexEVS development process2014.12.03  on hold
281ScottTry to replicate what CTRP did to break our service (retrieve a tree through CTS2).2015.03.25  on hold
282Mayo TeamLook into implementing graph node in CTS2 for the path to root method (and path to leaf).2015.03.25  on hold




  • No labels