NIH | National Cancer Institute | NCI Wiki  

Attendees

NameRolePresent
Haber, MargaretNIH/NCI
x
Fragoso, Gilberto NIH/NCI     

De Coronado, Sherri    

NIH/NCI   x

Safran, Tracy

NIH/NCI [C] 
Ong, Kim L
ISx
Lucas, Jason R
ISx
Bauer, Scott  Mayox
Stancl, Craig
Mayox
Endle,  CoryMayox
Wynne, Robert    NIH/NCI [C]x

Kuntipuram, Kumar

NIH/NCI [C] 
Mensah, JacobNIH/NCI [C]x
Trong, TracyNIH/NCI [C] 
Din, SanaNIH/NCI [C] 
Kisler, BronNIH/NCI [C] 
Remennik, LyubovNIH/CC/BTRISx

Action Items

AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
      

Agenda

EVS Weekly Tech Meeting

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:

Roll Call 

Sprint Status

 

Current Sprint  Sprint 74 (January 18, 2018 – January 31, 2018)

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

API Meeting/Discussion Update

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:

Resolved Value Set rework

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:

Team Absences

Mayo Team

  • Cory -
  • Scott -
  • Craig -

NCI

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

JIRA Issues

Recent LexEVS Related Bugs and Features (within last week)

Key Summary T Created Reporter P Status Affected Version/s Fix Version/s
Loading...
Refresh

Recent CTS2 Service Related Issues (within last week)

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Loading...
Refresh

6.5 LexEVS Related Issues

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Loading...
Refresh

6.5 CTS2 Service Related Issues

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Loading...
Refresh

Project Plan Changes

#DescriptionDue DateResourcesNotesRisksMitigation
 None     
       
       

 Planned Activities

Area of InterestDetails
  
  
  

Risks, Issues, Dependencies

Risks

Opened DateDue DateDescriptionLikelihood (H, M, L)ImpactAssignedStatusMitigation Strategy
         
         

Issues

 #Opened DateDescriptionImpactAssignedStatus
      
      
      

Dependencies

Opened DateDescriptionAssigned
   
   

 

Action Item Backlog

 #AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
       

 

 

 


  • No labels