Page History

De Coronado, Sherri    

Safran, Tracy

Kuntipuram, Kumar

Discussion Points:

• LexEVS
  • Updates for Systems team has DEV system to be configured to run Docker containers.
    • LexES team to start working with this setup.
  • CTS2 on-line documentation is running on NCI Dev system and Heroku.
    • Jenkins is set up to build/deploy on dev.
  • Lexevs-system-tests - have been updated and are running successfully.
  • MySQL timeout during value set load.
• Browser/Tools
• Data
• Systems
• Triple Store/EVS API

Decision Points:

• Cory to submit a ticket to install npm/node.js and deploy CTS2 API documentation artifacts to QA/PROD.

Sprint Status

Discussion Points:

Decision Points:

• Scott will send a link to the slides to Margaret and Lyubov.
  

Empty value sets - Update (Rob)

Discussion Points:

•  VS have loaded last night on Dev.
• Should we load empty VS?  Rob suggested that it may be OK.The browser should be able to handle an empty VS Meeting will be on Thursday this week.

Decision Points:

Discussion Points:

• Resolved VS were persisted in the past.  They are now dynamically resolved (without being persisted).
• VS definitions are still be persisted to the system.
• We depend upon the resolved VS for the existing CTS2 REST API.The lexevs resolved value set API will need to be updated to still return the resolved value sets.should continue to return what it was prior to this rework.
• The search extension won't have value set coding schemes to search against.
• The team will need to determine what impacts that these changes will have on existing applications that use this The VS search API will change (source asserted API).  The browser will need to use the new API.

Decision Points: 

• Scott to send out email to document/describe the value set rework and what impacts this will have on resolved value sets and other services.

Discussion Points:

• Scott mentioned that how we represent/structure value sets in NCIt is a new/interesting concept. 
• He mentioned that this could be a good idea for a paper.

Decision Points: 

• Scott and Rob to create an abstract and bring it back to the group to review.Rob suggested that this scenario should work:
  • Browser - If multiple value sets are selected, and one is empty, the browser should still get results back.
  • If a user clicks on the empty value set in the hierarchy, they should be able to see the value set information and an empty value set.
    
    • The user currently see a "null" response.
   

LexEVS External Users

Discussion Points:

• caDSR - LexEVS REST vs Java API discussion on Friday.
• Mayo team gave some query/display examples using the LexEVS API and CTS2 REST API.
• We did not have an EVS API example. 
  

Decision Points:

Mayo Team

• Cory -
• Scott -
  
• Craig -

NCI

• Tracy -
  
• Rob - 2/13-3/6
• Bron -
  
• Sana -
  
• Kim -