NIH | National Cancer Institute | NCI Wiki  

  • Created by Unknown User (endlecm), last modified on Dec 14, 2016

 Attendees

NameRolePresent
Wright, Larry NIH/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  Mayo 
Stancl, Craig
Mayox
Endle,  CoryMayox
Wynne, Robert    NIH/NCI [C]x
Tran, Tin    NIH/NCI [C]  
Carlsen, Brian NIH/NCI [C] 
Wong, Joanne NIH/NCI [C] 

Kuntipuram, Kumar

NIH/NCI [C] 

Action Items

AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
ScottRequest DEV VM at NCI.2016.12.072016.12.21 Open
JasonRequest Java 8 VM environment build.2016.12.072016.12.212016.12.14Closed
ScottCreate new issue for API for LEXEVS-25102016.12.072016.12.21 Open
Craig

Schedule backlog grooming meeting (Dec 21 at 1:00?)

2016.12.072016.12.21 Open
CraigClose all "on hold" JIRA issues as "resolved - not fixed"2016.12.072016.12.21 Open

Agenda

Sprint Status

 

Current Sprint -  Sprint 45 (December 8, 2016 – December 21, 2016)

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

  • Mayo team worked 3 days on CTRP issue.  This may push some stories to the next sprint.
CTRP Status

Discussion Points:

  • CTRP is able to go production after updates from the EVS team.
    • Jacob increased the max thread pool on tomcat for the CTS2 service.  This seems to have fixed the out of memory issue that CTRP was running into.
  • Mayo team will create stress tests and profile the server to see if there are areas for improvement. 
    • This will need to be prioritized.
  • Craig noted that we and  the external teams should be aware of what services are used.
    • For example, CTRP is using the data services.  These will be removed in LexEVS 6.5.0.

Decision Points:

  • Larry and team will need to prioritize the work to do stress tests and profiling.
    • This work should be done in the next couple of sprints as time permits.
    • If there are areas to fix, Larry/Craig suggested putting fixes into the 6.4.2 release.

LexEVS Java 1.8 environment

Discussion Points:

  • Jason created a ticket to request a Java 8 environment.

Decision Points:

6.4.1.3 build update

Discussion Points:

  • We will build a 6.4.1.3 snapshot when lexevs-2510 is completed.
  • We will also put in a fix for lexevs-2461 and lexevs-2529.

Decision Points:

  • Cory will send out column widths to Rob/Tracy (lexevs-2529)
  • Cory to verify that lexevs-2463 is resolved -  value set issue pertaining to loading with PRODUCTION tag.

NCI Nexus Server Migration Update

Discussion Points:

  • No updates.

Decision Points:

  • Cory will follow up with Sarah for an update.
BioMarker Discussion

Discussion Points:

  • Nothing for the LexEVS team yet.
  • Other discussions and requirements from other teams need to happen first.

Decision Points:

OBI Load

Discussion Points:

  • lexevs-2503
  • Scott was able to reproduce the error based on a preference file from Tracy.

Decision Points:

Value set resolution algorithm

Discussion Points:

  • Kim had a couple of questions
    • Leaf node and transitive closure - how does this work?
    • Value set with no entities - how do you create an XML file for this?

Decision Points:

  • The value set documentation should be updated with the above answers by the Mayo team.
LexEVS External Users 
Team Absences

Mayo Team

  • Cory - Dec 26, Jan 2
  • Scott - Dec 26, Jan 2
  • Craig - Dec 26 -30, Jan 2

NCI

  • Tracy
    • Jan 9-17
    • Feb 21-24
  • Rob

    • 12/19

    • 12/23-12/27

    • 1/2/2017

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.4 LexEVS Related Issues

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

6.4 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