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, DeepakMayox
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

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


  • Sprint 28
  • On going Support
  • Sprint 28
  • On going Support
  • Sprint 28
  • Sprint 28
  • Agile Admin


Sprint Status

Current Sprint  Sprint 28 (April 14, 2016 – April 27, 2016)

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

LexEVS Compatibility

  • Remote service and client jar migration

LexEVS 6.4 Remote Service and Client Updates

caCore legacy code was mentioned and it was suggested that we should remove any caCore code.

Mayo will need to prioritize this work to determine where it will fit into our schedule. 

TODO:  Craig to create a JIRA item to track the removal of the caCore code.

PTE for CI and DEV environment discussion

  • CI Server
  • DEV Server

CI server - it was discussed that we may use an in-memory DB (HSQL) instead of MySQL DB.  This is being investigated by Mayo to see if we can get this working locally.

Scott noted that our Mayo Jenkins server is running on a system that has 8 cores with 32 GB of memory.


DEV server - Rob has installed LexEVS 6.4 runtime on DEV and generated the indexes.

There is a new 6.4 DEV container that Jacob is working on getting deployed.


NCI testing - NCI will build the 2.8 browser with the new LexEVS 6.4 jars and see if that runs without any code changes.

NCI will also test the runtime API and Tin will look at performance to compare 6.3 and 6.4.


Jason asked when the remote API will be available.  We suggested that it should be delivered by the end of sprint 29.  We will need to verify performance is still acceptable prior to releasing it to NCI.

CTS2 and jQuery Example Follow upKim was running into a cross site scripting issue.  Scott suggested using a JSONP call to resolve this issue.
LexEVS External UsersNothing to note.

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