NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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
IS x
Lucas, Jason R
IS x
Bauer, Scott  Mayo 
Stancl, Craig
Mayo x
Endle,  CoryMayo x
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] 

...

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

F2F Debrief

Discussion Points:

  • We felt this was a productive face to face. 
  • The ideas here will guide us for the next year.
  • We will have to do additional planning and prioritization.
  • Some of the major focus points will be on REST, DevOps, the use of micro services, and triple stores.

Decision Points:

  • Scott to submit a ticket to request a DEV VM at NCI.

LexEVS 6.4.2 (Java 1.8)

  • Timeline discussion

Discussion Points:

  • There have been several LexEVS updates recently. 
  • We want to be considerate of the churn for the clients that will need to update.
  • We need to be at Java 8 to move to Cent OS 7.
  • The browser is not running at Java 8 yet.

Decision Points:

  • LexEVS 6.4.2 branch is running on Java 8. 
  • LexEVS-2510 fix (for the API)  will be included in the 6.4.2 branch.
  • Jason will create a ticket to start Java 8 build.

Backlog grooming discussion

  • Recent grooming performed
  • Set up meeting request
    • Mandatory attendance
    • Optional attendance

Discussion Points:

  • NCI team is willing to work with us as we groom the backlog.
  • Tracy suggested sending a list of JIRA issues ahead of time to review.
  • Start with a small group of technical developers.

Decision Points:

  • Initial backlog grooming group should contain the following: Rob, Tracy, Gilberto, Kim, Cory, Scott, Craig.
    • Gilberto and Larry can be option depending on the issues we are reviewing for the current meeting.
  • Mayo team to create a wiki that contains the list of JIRA issues we want to discuss.
  • Craig to send meeting notice out.

Sprint 45 Planning

  • Prioritize F2F issues

Discussion Points:

  • We reviewed the current items queued up for sprint 45.
  • We discussed MySQL 5.6 upgrade.  Once we verify it for performance, we can upgrade when NCI Systems team is ready.
  • Larry asked to add the value set fix (loader part of the fix) to this sprint for LexEVS 6.4.1.3.

Prioritize F2F issues

Decision Points:

Craig asked how we should start prioritizing the priority 1's.  This is what prioritization the team decided (in order):

  • Tech stack and deployment stories.
  • Value set workflow management stories to support Rob/Tracy
  • REST features to support our clients.
  • DevOps, CI server and Docker
    • These are dependent upon NCI systems.
  • Tracy and Rob mentioned that the command line script functionality is suffice for now.
    • The current admin stories are "nice to have", but not necessary.
  • 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

6.4.1.3 issues

Discussion Points:

  • OWL1 loader change
    • Jira
      serverNCI Tracker
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId7954a81f-12da-3366-a0ef-97c806660e7c
      keyLEXEVS-2448
  • GUI updates
    • Jira
      serverNCI Tracker
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId7954a81f-12da-3366-a0ef-97c806660e7c
      keyLEXEVS-2288
    • Jira
      serverNCI Tracker
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId7954a81f-12da-3366-a0ef-97c806660e7c
      keyLEXEVS-2459
  • Value Set load
    • Jira
      serverNCI Tracker
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId7954a81f-12da-3366-a0ef-97c806660e7c
      keyLEXEVS-2241
    • Jira
      serverNCI Tracker
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId7954a81f-12da-3366-a0ef-97c806660e7c
      keyLEXEVS-2463

Decision Points:

  • We would like to add the LexEVS-2510 to 6.4.1.3.  But only the loader change for this issue.
  • Jira
    serverNCI Tracker
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId7954a81f-12da-3366-a0ef-97c806660e7c
    keyLEXEVS-2510
    There is a loader fix and and API fix for this issue.

NCI Nexus Server Migration Update

Discussion Points:

  • No updates.

Decision Points:

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

Discussion Points:

  • No updates

Decision Points:

CTS2 URLs for 6.3 and 6.4

Discussion Points:

  • No updates

Decision 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

Initial grooming

  • On Hold Issues
  • Initial Items to review

Discussion Points:

  • Initial Items to review
    • Jira
      serverNCI Tracker
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId7954a81f-12da-3366-a0ef-97c806660e7c
      keyLEXEVS-1483
    • Jira
      serverNCI Tracker
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId7954a81f-12da-3366-a0ef-97c806660e7c
      keyLEXEVS-285
    • Jira
      serverNCI Tracker
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId7954a81f-12da-3366-a0ef-97c806660e7c
      keyLEXEVS-1110
    • Jira
      serverNCI Tracker
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId7954a81f-12da-3366-a0ef-97c806660e7c
      keyLEXEVS-809
    • Jira
      serverNCI Tracker
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId7954a81f-12da-3366-a0ef-97c806660e7c
      keyLEXEVS-961
    • Jira
      serverNCI Tracker
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId7954a81f-12da-3366-a0ef-97c806660e7c
      keyLEXEVS-911
    • Jira
      serverNCI Tracker
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId7954a81f-12da-3366-a0ef-97c806660e7c
      keyLEXEVS-1131

Decision Points:

On Hold Issues - We agreed to close them all (Resolved - Not Fixed).The Mayo team will close these issues
  • .
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
    • Dec 14-16
    • Jan 9-17
    • Feb 21-24
  • Rob
    • 12/19

    • 12/23-12/27

    • 1/2/2017

...

Risks

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

Issues

 #Opened DateDescriptionImpactAssignedStatus
      
      
      

Dependencies

Opened DateDescriptionAssigned
   
   

 

Action Item Backlog

2014.07.30
 #AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
64ScottTo follow up on URI's on OWL2 with Harold.   on hold
164CoryCory to add implementation to CTS2 implementations page.2014.04.30  on hold
197ScottDo a gap analysis on what the URI_Resolver logs and what NCI would like to know from these logs2014.6.18  on hold
200Larry/SherryQuery current LexEVS users about use of SOAP, REST or QBE services in the legacy caCORE api's2014.6.18  on hold
207CoryWrite issue against CTS2 OMG regarding the ability to return INACTIVE concepts only.2014.07.30  on hold
210Larry/GilbertoDetermine if there is a need to meet with the CTRP
  on hold212LarryInclude LexGrid XML Export as part of the 5.1 retirement notice. 2014.07.30  on hold224ScottURI Resolver - Provide overview of how to access the URI Resolver2014.09.03  

on hold

225ScottURI Resolver - Look at TLAMP and VSAC service to determine usage of URI Resolver2014.09.03  on hold
244CraigPlan meeting with Tracy to discuss collaborative LexEVS development process2014.12.03  on hold
281ScottTry to replicate what CTRP did to break our service (retrieve a tree through CTS2).2015.03.25  on hold
282Mayo TeamLook into implementing graph node in CTS2 for the path to root method (and path to leaf).2015.03.25  on hold