NIH | National Cancer Institute | NCI Wiki  

 Attendees

NameRolePresent
Wright, Larry NIH/NCI   
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
Tran, Tin    NIH/NCI [C]  
Carlsen, Brian NIH/NCI [C] 
Wong, Joanne NIH/NCI [C] 

Kuntipuram, Kumar

NIH/NCI [C]x

Action Items

AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
      

Agenda

Sprint Status

 

Current Sprint  Sprint 41 (October 13, 2016 – October 26, 2016)

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

  • Completed Lexevs 6.4.1.1 artifacts
  • Completed some Java 1.8 tasks
  • Assisted with issues found during the sprint.

6.4.1 Deployment/Testing status

 

Discussion Points:

  • This is in Production now.  CaDSR is using this version

Decision Points:

6.4.1.1 Build and Deployment

  • Testing on QA

Discussion Points:

  • There are some issues found in this release
  • LEXEVS-2413 - Kim mentioned that the browser is passing in a hash set in its code, but is not seeing this error.
  • We will investigate LEXEVS-2412  (OBI) to determine if this is a loader or code issues.
    • If this is a code issue, we will need to determine what release they would go in.

Decision Points:

  • LEXEVS-2413 - Scott will verify if this is a java 1.7/18 issue or if it is just an API level issue.
Valueset resolution issue on STAGE

Discussion Points:

  • This issue was resolve by fixing the data load.
  • Tracy suggested that we add a loader preference to set the value set version.

Decision Points:

  • Scott will investigate this issue and see if anything breaks and then propose a solution, if needed.
    • This test plan and execution will be added to the JIRA item
LEXEVS-2412 - Getting issue details... STATUS

Discussion Points:

 

Decision Points:

NCI Nexus Server Migration Update

Discussion Points:

  • Mayo team had a meeting on Monday with Sarah and team. 
  • They will look at automating the maven script for publishing artifacts first, then look at the ANT

Decision Points:

CTS2 URLs for 6.3 and 6.4

Discussion Points:

  • CTRP verification of HTTPS URL.

Decision Points:

  • The contact person is Emont. 
  • Tracy will contact this person to see if they have tested the HTTPS URL.

MySQL database upgrade for LEXEVS

Discussion Points:

  • An NCI email states- "All MySQL Development databases except LEXEVS databases, related applications, and related servers could be restarted during this patching window."  
  • Jacob is working with the DBA team to determine when 5.6 is required. 

Decision Points:

DEV deployment process

Discussion Points:

  • The Mayo team would like to have a dev server that we would push out the latest snapshot code to at the end of the sprint.
  • The Mayo team would maintain the lexevs software on this system.
  • Tracy mentioned that the only one that would use the lexevs release would be the browser.
  • The dev server could be a VM.
  • We could also use the existing DEV server for this work.

Decision Points:

  • We will work with Jacob to determine if we need a new dev instance or if we can use the existing DEV server

F2F Planning

Discussion Points:

Decision Points:

LexEVS External Users

https://github.com/cts2/lexevs-service/issues/15

  • Multiple targets in mappings source not working?

Team Absences

Mayo Team

  • Cory -
  • Scott -
  • Craig -

NCI

  • Larry
    • October 20 - November 7
  • Tracy
    • Nov 8
    • Dec 14-16
    • Jan 9-17
    • Feb 21-24
  • Rob
    • 10/21 – AM only

    • 11/2

    • 11/14 – PM only

    • 11/24-11/28

    • 12/9

    • 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
Loading...
Refresh

Recent CTS2 Service Related Issues (within last week)

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

6.4 LexEVS Related Issues

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

6.4 CTS2 Service Related Issues

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Loading...
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
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 CTRP2014.07.30  on hold
212LarryInclude LexGrid XML Export as part of the 5.1 retirement notice. 2014.07.30  

on hold

224ScottURI 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

 

 

 


  • No labels