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]x

Kuntipuram, Kumar

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

Action Items

AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
      

Agenda

EVS Weekly Tech Meeting

Discussion Points:

  • LexEVS
    • Lexevs 6.5 AnthillPro migration to Jenkins update on upper tiers.
      • Migrations completed:
        • Lexevs API (Dev, QA, Stage, Prod)
        • Lexevs-service (CTS2) (Dev, QA, Stage, Prod)
        • URI Resolver (Dev)
      • Migrations not yet completed:
        • Lexevs-service (CTS2) (Stage, Prod)
          • Completed through Prod, but not yet deployed there.
        • URI Resolver (Dev, QA, Stage, Prod)
          • Completed on dev
      • Goal is to be off from AHP by end of this year.
    • Lexevs-system tests (Jenkins/Docker) system failures causing builds to fail.
      • Phil will increase the log history to about 10 and monitor builds.
      • Mayo team will email any errors that we notice to Phil.
    • Lexevs URLs for 6.5.1
      • The URLs will stay the same as the 6.5 URLs
      • We will cut over from 6.5 to 6.5.1.  (We won't have both services running at the same time).
      • Users (CTRP, caDSR, Browser) will be requested to test the LexEVS remote API on Stage (to validate the API didn't change for them).
  • Browser/Tools
  • Data
  • Systems
  • Triple Store/EVS API

Decision Points:

  • Come up plan on how to promote 6.5.1 and data up the tiers.
    • Jacob mentioned that Prod and Stage point to each other when they are being updated.
Roll Call 

Sprint Status

 

Current Sprint  Sprint 83 (May 24, 2018 – June 6, 2018)

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

Release Roadmap
  • Discussion Points:
    • Planned Release Roadmap
      • Estimated effort:
        • Sprint 83 - May 24, 2018 June 6, 2018
          • LexEVS will be code complete during this sprint. 
          • Last planned snapshot (SNAPSHOT.15) will be delivered during this sprint.
          • Anticipated delivery of SNAPSHOT.15 by about May 30th.
          • Deploy SNAPSHOT.15 to Dev.
        • Sprint 84 - June 7, 2018 - June 20th
          • If no issues were found in SNAPSHOT.15 on Dev, we can re-brand SNAPSHOT.15 as a release candidate (RC1) and deploy to QA for testing (on or after June 7). 
          • We will request an Appscan of RC1 on QA

Decision Points:

  • A high level release roadmap of LexEVS was requested by Margaret for the rest of the team.
  • Kumar volunteered will work with all the teams to get their individual plans and come up with a master project plan.
Mapping Namespace Issue

Discussion Points:

  • Scott reviewed the issue and the fix with namespace mapping (as described in the JIRA issue).
  • Tracy mentioned the scenario for mapping NCIt to SwissProt (that coding scheme is not loaded in LexEVS) to consider.

Decision Points:

  • Tracy agrees with the fix for the current issue.
  • We will need to define further requirements for future enhancements for namespaces and mapping.
EVS F2F Planning

Discussion Points:

  • Sherry suggested getting together July 19th, Thursday afternoon via a conference call to discuss LexEVS topics.

Decision Points:

LexEVS External Users

Discussion Points:

Decision Points:

Team Absences

Mayo Team

  • Cory - June 5, June 18th - 21st
  • Scott - June 18th - July 1st, July 25 -27
  • Craig -

NCI

  • Tracy - June 7, July 30 - August 5
  • Rob - June 28,29, July 12,13
  • 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