LexEVS Meeting Minutes - 2018.01.31

De Coronado, Sherri    

Safran, Tracy

Kuntipuram, Kumar

Discussion Points:

• LexEVS
  • Updates for DEV system to be configured to run Docker containers.
    • Jacob is testing Docker implementation.
  • CTS2 on-line documentation is running on NCI Dev system and Heroku.
    • redis server is not needed. This ticket was cancelled.
    • Ticket submitted for setting Jenkins to build/deploy on all of the tiers.
      • Jacob is working on this issue as well.
  • Lexevs-system-tests - updates in progress due to centos7_tomcat image different than standard unbunto image.
    • Jenkins and Docker - users and permissions.
    • Margaret suggested resurfacing this issue at the next Monday meeting.
• Browser/Tools
• Data
• Systems
• Triple Store/EVS API

Decision Points:

Sprint Status

Discussion Points:

• Bron and Tracy are out today.
• Scott gave a quick overview of the last meeting.  Much of the time was discussing and documenting the existing architecture.
• Margaret suggested this meeting should include requirements gathering and gap determination as well as day to day needs.
  

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.

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.
• The VS search API will change (source asserted API).  The browser will need to use the new API.
  

Decision Points:

• 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.
  

Decision Points:

Mayo Team

• Cory -
• Scott -
  
• Craig -

NCI

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