Attendees

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

De Coronado, Sherri    

NIH/NCI   x

Safran, Tracy

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

Kuntipuram, Kumar

NIH/NCI [C]x
Mensah, JacobNIH/NCI [C] 
Trong, TracyNIH/NCI [C]x
Vinayagampudur, Kiruthika
NIH/NCI [C] 
Kisler, BronNIH/NCI [C]x
Remennik, LyubovNIH/CC/BTRIS 

Action Items

AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
      

Agenda

EVS Weekly Tech Meeting

Discussion Points:

  • LexEVS
    • CTS2 on-line documentation is running on NCI Prod system. 
      • A ticket has been submitted for the URL to be accessed outside the firewall.
      • Update on the appscan.
    • Lexevs 6.5 AnthillPro migration to Jenkins update
    • Performance - Browser and LexEVS
      • Indexing and Coding Schemes out of sync?
      • Broken Pipes?
      • Null values for coding scheme queries?
      • QA responsibilities?
  • Browser/Tools
  • Data
  • Systems
  • Triple Store/EVS API

Decision Points:

Roll Call 

Sprint Status

 

Current Sprint  Sprint 77 (March 1, 2018 – March 14, 2018)

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

6.5.1.SNAPSHOT.6 deployed to dev

Discussion Points:

  • We discussed deploying responsibilities going forward.
  • Tracy would be Ok with the Mayo team to deploy the war and admin files in the future.
    • We will need to coordinate with Rob on loads that he does out there.

Decision Points:

  • We decided to discuss this issue again next week when Rob is back.
EVS Technical Strategy Meeting/Discussion Update

Discussion Points:

  •  Met on Monday and focused on browser performance issues.
  • A meeting is planned for Thursday when Rob and Gilberto are back.

Decision Points:

Browser Performance Issues

Discussion Points:

  • Accepting a MeDRA license takes a long time as well.
  • The broken pipe issue should be looked at.
  • Scott suggested that as part of QA, the browser logs should be scanned on QA and/or Stage to check for errors.
  • There may be code paths that the browser is going through LexEVS with that we have not tested.
  • The new QA tester is starting to take over and picking up the browser tests.

Decision Points:

  •  We decided to track the issues better and have a more formal way of categorizing the problems.
  • The Thursday metting with Bron will discuss this further.

LexEVS QA/Testing Overview

Discussion Points:

Decision Points: 

LexEVS External Users

Discussion Points:

Decision Points:

Team Absences

Mayo Team

  • Cory -
  • Scott - March 9, June 19th - July 1st
  • Craig -

NCI

  • Tracy -
  • Rob - 
  • Bron -
  • Sana -
  • Kim -

JIRA Issues

Recent LexEVS Related Bugs and Features (within last week)

Recent CTS2 Service Related Issues (within last week)

6.5 LexEVS Related Issues

6.5 CTS2 Service Related Issues

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