NIH | National Cancer Institute | NCI Wiki  


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

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]  
Barry x
Carlsen, Brian NIH/NCI [C] 
Wong, Joanne NIH/NCI [C] 

Kuntipuram, Kumar


Action Items

AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus

Close issue 

  LEXEVS-1516 - Getting issue details... STATUS

2016.02.092016.04.10 Open

Create JIRA issue to update CTS2 service to use Apache Commons Collections Version 3.2.1 (security issue)

2016.03.092016.03.30 Open
CraigCreate JIRA issue to remove caCore legacy code2016.04.202016.04.30 Open
CoryUpdate wiki to describe what DBs are supported/tested going forward2016.04.272016.04.30 Open


  • Sprint 30
  • Sprint 31 Planning
  • On going Support
  • Sprint 30
  • Sprint 31 Planning
  • On going Support
  • Sprint 30
  • Sprint 31 Planning
  • Sprint 30
  • Sprint 31 Planning
  • Agile Admin


Sprint Status


Current Sprint  Sprint 30 (May 12, 2016 – May 25, 2016)

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

Mayo team deployed sprint 29 artifacts and determined stories for sprint 31.

We are looking at moving to the next phase for documentation and tier deployment. We have planned 60 days for tier deployment.

We need to discuss the following next steps:

  • Loader and tree extension JIRA items and if they need to be implemented for 6.4.
  • Determine when to working on 6.5 work.
  • Many issues have been de-prioritized to 6.5

Larry agreed that there are some loader issues that need to be worked on for the 6.4 release.

  • We will need to go through the existing loader issues to determine which ones need to be completed in 6.4.

We all agreed to move the backlog issues (not including the loader issues) in 6.4 into 6.5.

6.4 wrap upThis has been discussed above.
6.5/loader issues/tree extension issues 
Discuss LEXEVS-957 - Getting issue details... STATUS

LEXEVS-957 - Mapping iterators do not work on distributed.

This issue was closed and two new issues were created to better describe the issues (LEXEVS-960, LEXEVS-961)

Larry agreed that LEXEVS-960 and LEXEVS-961 should be looked at in 6.5

NCI DEV deployment updates

  • CTS2 1.4.1 (6.3) snapshot deployment progress
  • CTS2 1.5.0 (6.4) snapshot deployment

CTS2 6.3 is installed on DEV. This hasn't been tested on DEV yet.

  • Cory will create a FINAL tag on CTS2 6.3 (1.4.1) and place the artifact on the NCI SFTP site.
  • Cory will also need to update the PTE to use the correct artifact naming.

CTS2 6.4 is deployed on DEV, but has not be configured yet. Mayo will work with Tracy next week to configure sprint 30 artifacts and test.

6.4 DEV Testing updates

  • Lexevs API
  • Lexevs Remote API

Mayo has some lexevs remote API fixes that will be in the artifacts we create from sprint 30.

Kim will be able to test these fixes next week.

6.4 Deployment strategy

Mayo team will finalize our naming strategy for git branches and artifact naming and review with NCI team next week
URI Resolver - No External instance

Mayo's server doesn't have a public URI resolver anymore.

The lexevs CTS2 service requires to connect to a URI resolver in order perform the unit/integration tests. This forces the developers to have a local URI resolver to connect to in order to build.

We were asking if NCI has any interest in hosting a public URI resolver instance.

Larry was asking if there has been an appscan on their URI resolver. We don't recall specifically if there was one and agreed it would be good to have one done on their current instance.


LexEVS External Users

  • Updates
No updates.

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