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

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 31
  • Sprint 32 planning
  • On going Support
  • Sprint 31
  • Sprint 32 planning
  • On going Support
  • Out of office
  • Sprint 31
  • Sprint 32 planning
  • Agile Admin


Sprint Status


Current Sprint  Sprint 31 (May 26, 2016 – June 08, 2016)

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

We have completed sprint 31. The following tasks were completed:

  • We completed the code clean up task
  • We pushed out the 6.4 artifacts from the previous sprint.  
  • We also worked on remote API tests to make more generic. This will need to be expanded to provide more test coverage in the next sprint.
  • LEXEVS-1729 was fixed as well.

For sprint 32, we will start work on the following issues:

  • We will be delivering the 6.4 artifacts from sprint 31.
  • We will work on the OWL 2 loader issues.
  • We will provide additional test coverage for the remote API.
  • Based on today's suggestion, Gilberto suggested the HL7 loader issue should be put at the bottom of the list, after the OWL2 loader issues - LEXEVS-1037.

Gilberto suggested that LEXEVS-1153 should be fixed by fixing the other OWL2 loader issues.  

    • We will drop the priority to the last OWL2 loader issue to look at.

We are also managing the final deliverables for the 6.4 projects.

6.3 CTS2 service deployment

  • Update from Tin

This has been deployed to PROD. The Mayo development team verified that the property qualifiers are showing up.

Tracy has contacted CTRP about this update.

NCI DEV deployment updates

  • All Services

6.4 CTS2 hasn't been deployed to DEV yet.

Tracy will wait for the artifacts from sprint 31 and then deploy 6.4 CTS2.

Deployment Approach

  • RC1 Delivery

LexEVS 6.4 Git Tags and Artifact Naming Conventions

After discussing with NCI, we decided that we will create an RC build on DEV.

When tested/ready, we will create a FINAL tag for QA.

  • This build/tag will not change any further up the tiers. This will satisfy NCI's requirements.

Cory will update the document to reflect these changes.

OWL2 Approach (Prioritized)

We discussed this above.

Hyphenated Word - Contains Search

  • Verification (Kim)
Kim mentioned this is now working.

Complex Properties Hardcoded

LEXEVS-1948 - Getting issue details... STATUS

Tracy indicated that in OWL2, there should be no hard coding.

We should derive from the context. If it can't be then it should be taken from the preferences.

For priority, Gilberto suggested that this should be fixed as part of the OWL2 loader issues.

Rob suggested that other teams would like to use the "Map to" feature.

  • Tracy will create a separate issue for the "Map to" part of this issue. 
  • This is a high priority issue that should be done for 6.4.
6.4 Release Approach

Larry suggested the following approach for what will be on PROD:

  • LexEVS 6.4 will go to PROD and be available.
  • There will a single database with 2 indexes (one for 6.3 and one for 6.4)
  • 6.3 will still be the default LexEVS API
  • CTS2 REST will default to 6.4
  • The browser will use 6.4 LexEVS API
  • The community will be made aware of 6.4 and they can test

We should document 6.4 on the wiki. Make sure to include the following points:

  • CTS2 REST services will be available
  • Clients will need to rebuild jars if they move to 6.4.
    • We will need to provide a migration path

Looking forward to 6.5, we will need to look into replacing MySQL with MariaDB for better graph performance.

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