NIH | National Cancer Institute | NCI Wiki  

Attendees

NameRolePresent
Wright, Larry NIH/NCI  x
Fragoso, Gilberto NIH/NCI    x

De Coronado, Sherri    

NIH/NCI    

Safran, Tracy

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

Kuntipuram, Kumar

NIH/NCI [C] 
Haber, MargaretNIH/NCI

 

Mensah, JacobNIH/NCI [C]x
Din, SanaNIH/NCI [C]

 

Kessler, Ron  

Action Items

AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
      

Agenda

EVS Weekly Tech Meeting

Discussion Points:

  • LexEVS
    • 6.5.0 Firewall exceptions on Stage and Prod are finished.
    • The main LexEVS URLs don't point to 6.5.0 yet.
  • Browser/Tools
  • Data
    • Request to promote data to Stage
    • Resolved value set definitions with no members is causing problems.
  • Systems
  • Triple Store/EVS API

Decision Points:

Sprint Status

 

Current Sprint -  Sprint 62 (August 3, 2017 – August 16, 2017)


16X237 Agile Development - Sprint Status#16X237AgileDevelopment-SprintStatus-Sprint62
Tier Deployment - Update
  • Tier Deployment
    • Data deployment

Discussion Points:

  • LexEVS Deployment Status  

  • LexEVS is on Prod.  The browser is still in the process of being scanned and going through all tests.

  • The team may be able to finish release documentation in the next sprint.

Decision Points:

  • Mayo team to put together a summary of 6.5 features and any transitions.
Prioritized Value Set Issues

Discussion Points:  

 

Decision Points:

Development Snapshots availability

Discussion Points: 

  • LexEVS 6.5.0+ Snapshots will be created starting next sprint.
  • We suggested using the Mayo Dev VM.
  • Tracy suggested using the main DEV system.

Decision Points:

  • We agreed that we could put 6.5.0+ snapshots on the main Dev box on NCI.
Snapshot Deployment Location

Discussion Points: 

Decision Points:

LexEVS External Users

Discussion Points: 

Decision Points:

Duplicate Value Sets

Discussion Points: 

  • LEXEVS-3221 - Getting issue details... STATUS

  • This could be loaded with an MD5 version, or the name of the value set could be changed.

  • Scott suggested renaming the value set index would be a quick solution.

Decision Points:

  • We will work on this issue in the next load.
September Planning

Discussion Points: 

  • From this discussion, we shouldn't have to worry about wrapping everything up in a release for the end of September.  We should continue normal development.

Decision Points:

Team Absences

Mayo Team

  • Cory -  8/14, 8/15, 8/18
  • Scott - 
  • Craig -  8/10 - 8/22

NCI

  • Tracy -
  • Rob -
  • Kim -
  • Larry -

JIRA Issues

Recent LexEVS Related Bugs and Features (within last week)

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

Recent CTS2 Service Related Issues (within last week)

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

6.5 LexEVS Related Issues

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

6.5 CTS2 Service Related Issues

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
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