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]  

Kuntipuram, Kumar

Haber, MargaretNIH/NCI


Sana x

Action Items

AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus


Sprint Status


Current Sprint  Sprint 58 (June 8, 2017 – June 21, 2017)

16X237 Agile Development - Sprint Status#16X237AgileDevelopment-SprintStatus-Sprint58
LexEVS REST Services

Discussion Points:

Goals of REST API from CTRP and others

  • Much simpler format with just thesaurus content
    • Harmonized with the REST (JSON) output with the CTS2 service.   This will make it compatible with users of both CTS2 output (JSON) and this REST service.
    • Is there an easier REST API to put on the top of CTS2?
  • There are current users of CTS2 REST service, so we need to make sure any API changes will have a similar format.
  • EntityDescription vs RDF label - how do we harmonize the data.
  • CTS2 is generic.  The NCI team is suggesting going to a more specific (RDF OWL) model for a thesaurus API.
    • Current SPRARQL REST calls to StarDog returns JSON (OWL2 model).

Decision Points:

  • Tracy requested from the LexEVS team: mapping to/from lexgrid↔OWL.
  • Kim will share with the Mayo team the output/format he has from SPRARQL REST calls to StarDog. 
  • Mayo team will see if anyone in our group has triple store expertise that may be able to answer questions from NCI.
 Tier Deployment - Update
  • Tier Deployment
    • Data deployment
  • LexEVS Admin testing

Discussion Points:

Decision Points:

Docker - Next Steps Discussion

Discussion Points:

  • lexevs-system-test Docker script is pulling Docker images from the internal NCI Nexus server. 
    • Working with systems team on configuring this withing Jenkins the server.
  • On Monday we discussed with the systems team what it would take create a lexevs deployable container as a prototype on a Dev server.
    • The systems team is a few months out on this work.
    • The Mayo team will start to design and develop Docker images with non-NCI specific software.

Decision Points:

Value Set Architecture

  • Update

Discussion Points:

  • Working on miscellaneous issues on the value set workflow.
  • Moving toward replacing the hierarchy implementation.
    • We will need to understand the current hierarchy structure and how it is handled in the browser.

Decision Points:

LexEVS External Users

Discussion Points:

Decision Points:

  • Craig to set up meeting with ASU and our NCI/LexEVS team.
Team Absences

Mayo Team

  • Cory - 6/19 - 6/23
  • Scott - 7/27 - 7/28, 7/31- 8/1
  • Craig -


  • Tracy
  • Rob June 16,19
  • Kim
  • Larry - 6/23 - 6/29

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.5 LexEVS Related Issues

Key Summary T Created Updated Due Assignee Reporter P Status Resolution

6.5 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