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


  • Sprint 37
  • LexEVS 6.5 planning
  • On going Support
  • Sprint 37
  • LexEVS 6.5 planning
  • On going Support
  • Sprint 37
  • LexEVS 6.5 planning
  • Sprint 37
  • 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

The Mayo team is working on testing features and mavenizing the remote client.

QA Tier Status

  • AppScan

Discussion Points:

  • The remote API appscan had an issue that was fixed by the systems configuration team.
  • The CTS2 appscan didn't really test the REST services. The scan tried to find the WSDL, but that didn't do anything.
    • The appscan would need to know how to construct our REST calls.
    • Larry suggested that the tests didn't find any issues and that should be suffice.

Decision Points:

  • We decided the appscan is fine and we can move on.

Release Plan for 6.4.1

    • PTEs updated

Discussion Points:

Decision Points:

  • The NCI team will deploy to DEV and test.

OWL2 Loader Verification

Discussion Points:

  • There is concern about the OWL2 loader issue of the Thesaurus.
  • Scott asked if we need to fix this now.
  • Tracy mentioned that we are not loading OWL2 into production.
  • In the future we should be test loading the thesaurus with OWL2

Decision Points:

  • We will hold off on the OWL2 fix until next sprint before considering it.

HTTPS document review

Discussion Points:

  • Remote Client HTTPS Requirements
  • We went over the changes for the remote client as well as for the CTS2 REST client.
  • In order to help clients understand if clients need to make changes, Larry suggested that we add some text to have the end user contact us with their sample code.

Decision Points:

  • Scott will add a message to the https document that the end users can send the Mayo team a snippet of their code and we can assist in analyzing what changes (if any) they would need to make.

LexEVS External Users

  • Alexander

We have responded to the user that the fix has been checked in for the issue he found.

Team Absences

Mayo Team

  • Deepak - Sept 1-6?, Sept 5
  • Cory - Sept 5
  • Scott - Sept 5
  • Craig - August 24 -29, 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