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] 
Tran, Tin    NIH/NCI [C] x

Kuntipuram, Kumar


Action Items

AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
CoryAdd link to Maven Opts for end users2016.12.21  



Sprint Status


Current Sprint  Sprint 50 (February 16, 2017 – March 1, 2017)

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

DEV Server Configurations

  • DEV Blade
  • Mayo DEV VM
    • 6.5.0 SNAPSHOT

Discussion Points:

  • LexEVS is loaded on Mayo DEV VM
  • LexEVS 6.5.0 SNAPSHOT will be loaded on DEV Blade with CentOS 7.
    • Jacob has a ticket for this work.
  • We will want a separate DB (MySQL 5.6) for the Blade and the VM Dev instances.

Decision Points:

  • Mayo team will request separate DBs for the Blade and the VM Dev instances.
    • Send note to Jacob.

Value Set Loading Enhancements

  • Load Update

Discussion Points:

  • Scott and team have identified the current issues with the value set failures.
  • Tracy has not had an opportunity to test the mass load script yet.
  • Mayo team will meet with Jason and Kim to discuss value sets architecture tomorrow.

Decision Points:

CTS2 REST API Discussion

Discussion Points:

  • The Mayo team will look at the new CTS2 JIRA issues created by Tracy.
  • We will determine if our current implementation can accommodate the request.
  • If it can't, can we implement it in CTS2.
  • If that can't be done, we can look at implementing it in a different service.
  • Larry suggested that there should be a simpler REST interface than CTS2.
    • Larry mentioned that they (customers) are coming up with some criteria and examples of what they would like. 
    • They will have some examples/criteria in the next couple of weeks.
    • This may be something like convenience methods or CTS2 extensions.

Decision Points:

  • The dev team will hold off looking at the existing JIRA issues and see if CTS2 can accommodate this in the next sprint.
  • The dev team will work on the tree extensions instead in this sprint.

LexEVS Logical Role Relationship

  • Discussion with Kim

Discussion Points:

  •   LEXEVS-2764 - Getting issue details... STATUS
  • We will leave this issue open until Kim can verify.

Decision Points:

AnyURI Designation

Discussion Points:

  • There is an example in the OBI OWL2 source.
  • The AnyURI is declared as data type in the annotation property.
  • This doesn't fit into LexEVS model (an association on an association).  The LexEVS API wouldn't handle this well either.

Decision Points:

  • Scott mentioned that our load will ignore this case
  • Scott will sent a snippet source example to Gilberto.
Thesaurus OWL2 Source

Discussion Points:

  • Our loads are now making a lot of calls into the ontology class.
  • This is increasing our Thesaurus OWL2 loads from 1hr to 3-6hrs.

Decision Points:

  • Scott will create a JIRA issue to investigate the new load performance issue.

Remote API timeout issue

  • Discussion with Kim

Discussion Points:

  •  Intermittent socket timeouts from the Remote API.
  • Scott is able to reproduce this issue locally.

Decision Points:

  • Scott will investigate why our system tests are not hitting the same issue.
LexEVS External Users

Discussion Points:

  • Nothing noted.

Decision Points:

Proposed Backlog Review Items

Discussion Points:

Decision Points:

Team Absences

Mayo Team

  • Cory -
  • Scott -
  • Craig - March 6-13


  • Tracy
    • March 9-17
  • Rob
    • March 20-24

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