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
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
CoryAdd link to Maven Opts for end users2016.12.21  



Sprint Status


Current Sprint  Sprint 48 (January 19, 2017 – February 1, 2017)

16X237 Agile Development - Sprint Status#16X237AgileDevelopment-SprintStatus-Sprint48

LexEVS Java 1.8 & MySQL 5.6 Environment

  • Status update: Jason

Discussion Points:

  • During our morning meeting, Jacob asked if we wanted to use CentOS 7 or RedHat 7. 
  • We suggested CentOS 7 as that is part of the tech stack that will be used in production. 

Decision Points:

  • We requested to go with CentOS 7 as this is what will be used in production. Snapshot build update

Discussion Points:

Decision Points:

  • Mayo will build another by this Friday for Rob to use for another load on Monday.
  • Mayo team will notify NCI dev team when this is complete.

NCI Nexus Server Migration Update

Discussion Points:

Decision Points:

Value Set Architecture Update

Discussion Points:

  • LexEVS 6.5.1 Value Set Architecture 
  • LEXEVS-1157 - Getting issue details... STATUS
  • LEXEVS-2670 - Getting issue details... STATUS  
  • After three different meetings, we came up with some value set requirements.
  • The two main requirements are:
    • Better logging to help determine if there were any failures for resolving the 760+ value sets.
    • Resolving all 760+ value sets should be quicker.
  • Scott has come up with a potential solution through the work in the above two JIRA items.  He created scripts to do the following:
    • Load value set definitions
    • Load resolved value set coding scheme
    • Removal tools for the above
  • Rob and Tracy requested to allow to provide tags for coding schemes and to log the names of the value sets.  This has added some database calls and slows it down some.

Decision Points:

  • Scott will run against all of the value sets to test performance locally.  He will get the list from Rob or Tracy.
  • We will create a snapshot build for Rob to test a load early next week.
eCache issue update

Discussion Points:

  • This happens when a user clicks on links in the search results from the browser.
  • We will continue to monitor this and investigate when this happens again.

Decision Points:

  • Scott will request access to the browser logs from Jacob for further investigation.

caCORE follow up

  • lexevs API URL
  • Follow up with Bob regarding data services

Discussion Points:

Decision Points:

CTRP Thread Issue

  • Data Services discussion

Discussion Points:

Decision Points:

  • Tracy will contact CTRP to start a conversation about the data services going away in the next release.
LexEVS External Users

Discussion Points:

Decision Points:

CTS2 handshake error

Discussion Points:

Decision Points:

  • Mayo team will document this issue on the CTS2 wiki.  There is nothing else to do.
Proposed Backlog Review Items

Discussion Points:

  • We groomed some tree extension issues this week.  

Decision Points:

  • We will come up with a new list of issues to groom for next week.
Team Absences

Mayo Team

  • Cory - Jan 27
  • Scott -
  • Craig -


  • Tracy
    • Feb 21-24
  • Rob

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




  • No labels