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

Kuntipuram, Kumar

Haber, MargaretNIH/NCI

Action Items

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



Sprint Status


Current Sprint  Sprint 51 (March 2, 2017 – March 15, 2017)

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

Triple store discussion

  • Gilberto

Discussion Points:

  • Gilberto gave an overview of the current status of the triple stores.
  • Gilberto is waiting for quotes to come back.
  • Stardog has another version coming out that may improve performance.

Decision Points:

  • The team decided to go with Stardog if we can get several developer licenses for a discount.  (They charge $8600/developer license).  Otherwise we will go with Virtuoso.

DEV Server Configurations

  • DEV Blade
    • Separate DB

Discussion Points:

  • Jacob anticipates the DEV blade VM will be installed with the FINAL by early next week.
  • Cory created a ticket for Jacob to create separate MySQL 5.6 DBs for the DEV blade and VM instances.

Decision Points:

Value Set Loading Enhancements

  • Load Update

Discussion Points:

  • LexEVS Meeting Minutes - Value Set Architecture Planning Session - 2017.03.02
  • We discussed how we could automate testing of loaded value set definitions and resolved value sets (in the meeting link above).
  • Tracy suggested starting from scratch to fix this error-prone approach.
  • Rob asked if we could we use the content of Thesaurus for populating the value set?
  • We could look into using an OWL based approach
    • Concept in subset.
  • Tracy suggested that this could be a prototype for outside groups to use too.
  • We will continue this discussion at our value set meeting next Tuesday, 3/14.

Decision Points:

  • Scott to test the value set load on the NCI DEV system.
  • Mayo dev team will look into a new architecture/design for generating the value sets.
CTS2 REST API Discussion

Discussion Points:

  • The Mayo dev team looked at the 6 CTS2 issues and determined what was possible for each.

  • LEXEVSCTS2-138: This fits within the realm of the CTS2 spec and could be implemented as a part of that specification
  • LEXEVSCTS2-139, 140: These are LexEVS coding scheme metadata and don’t really have a good counterpart or fit in CTS2.  We’d likely want to provide a separate resource or service for these. 
  • LEXEVSCTS2-142: Return only the specified information on an entity
    • This would be a new call that returned a new partial resource
  • LEXEVSCTS2-143: Return a property type for an entity 
  • LEXEVSCTS2-144:  Retrieve a concept based on the presence of a restriction
    • Workflow - series of calls to get from CTS2
    • A new wrapper/extension REST call would need to be created to do this in one call.
  • Priorities (suggested by Tracy)
    • Ability to retrieve the FULL_SYN information (Larry)
    • Search on property for a given criteria
      • Give me all the concepts that have a specific property
    • Limit the result set coming back.

Decision Points:

  • Set up meeting to look at examples and discuss.
  • Start to add to sprints - convenience methods for
    • LEXEVSCTS2-142, LEXEVSCTS2-143
AnyURI Designation

Discussion Points:

  • Gilberto - from the snippet that Scott provided: an annotation property that doesn't have a range.
  • There have been JIRA issues that were created for the points that Gilberto discussed.

Decision Points:

  • Gilberto to send an OBO example code snippet for the issues he discussed
Docker - Next Steps Discussion

Discussion Points:

  • Docker Contacts: Mike Stockwell & Sue Pan

Decision Points:

Resolving all relationships for a given association

  • Discussion with Kim

Discussion Points:

  • What is the use case for resolving all relationships for a given association. 
  • Is there a requirement for Enumerations
  • There is a workaround that can retrieve these relationships, but we should discuss implementing a more efficient API call.

Decision Points:

LexEVS External Users

Discussion Points:

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