NIH | National Cancer Institute | NCI Wiki  

  • Created by Unknown User (endlecm), last modified on Aug 17, 2016

 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
ISx
Lucas, Jason R
ISx
Bauer, Scott  Mayox
Stancl, Craig
Mayox
Endle,  CoryMayox
Sharma, DeepakMayox
Wynne, Robert    NIH/NCI [C]x
Tran, Tin    NIH/NCI [C] x
Carlsen, Brian NIH/NCI [C] 
Wong, Joanne NIH/NCI [C] 

Kuntipuram, Kumar

NIH/NCI [C]x

Action Items

AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
      

Progress

  
Scott
  • Sprint 37 planning
  • LexEVS 6.5 planning
  • On going Support
Cory
  • Sprint 37 planning
  • LexEVS 6.5 planning
  • On going Support
Deepak
  • Sprint 37 planning
  • LexEVS 6.5 planning
Craig
  • Sprint 37 planning
  • LexEVS 6.5 planning
  • Agile Admin

Agenda

LexEVS External Users

Sprint Status

 

Current Sprint -  Sprint 36 (August 04, 2016 – August 17, 2016)

LexEVS S13-500 Agile Development - Sprint Status#SprintStatus-Sprint36

Main work items that have been completed in sprint 36:

  • Tech stack - Java 8/CentOS7 testing and verification is complete.
  • HTTPS updates have been completed and verified.

QA Tier Status

  • Test update - Tin
  • AppScan

Discussion Points:

  • Testing is in progress.
  • Tin requested an AppScan for CTS2.

Decision Points:

Release Plan for

    • HTTPS
    • Tech Stack
    • Loaders

Discussion Points:

  • If we give NCI one release with everything, they would have to test the browser and other clients (caDSR) with the upgrade to Java 8.
  • Larry suggested this would be too much of a change for the clients at this time.
  • Scott suggested delivering all of the code that is compiled in Java 1.7.
  • Tracy mentioned that for the browser, they were able to redirect HTTP to HTTPS so end users were not forced to have to change their links.
  • We discussed testing the current LexEVS 6.4 and whether to continue testing or wait until the HTTPS changes are added in.
    • Tin suggested halt testing until the new build is created.
  • Larry suggested to create another build in Java 8. This would enable clients to test connecting to a Java 8 service and determine if their clients are compatible.

Decision Points:

  • There will be no changes to 6.3.
    • This will run http.
    • It may be shutdown at the beginning of 2017.
  • LexEVS 6.4.0 will be the HTTPS fix.
    • This will include the loader updates.
  • LexEVS 6.5 will be the Tech Stack update.
  • Mayo team will update the wiki page to show what changes are required to move to HTTPS.
  • Mayo will rebuild LexEVS 6.4.0 to have the HTTPS and Loader changes. It will be re-tagged as the same 6.4.0.FINAL code base.
    • This will be built in Java 7.
  • The CTS2 and LexEVS Remote API PTEs need to be updated to allow for HTTPS.
  • Tickets need to be created to configure QA/STAGE/PROD for HTTPS.
  • NCI needs to discuss with Systems to determine if they can handle parallel systems: one for HTTP and one for HTTPS.

Backlog grooming

Discussion Points:

  • We asked if NCI had any comments on the backlog and priorities.
  • Tracy suggested looking at the task to convert LexEVS to Maven.

Decision Points:

OWL2 Loader Verification

Discussion Points:

  • No testing has been done.

Decision Points:

6.5 Planning

Discussion Points:

Decision Points:

LexEVS External Users

  • Alexander

https://github.com/cts2/lexevs-service/issues/2#issuecomment-240205829

We assisted the user in configuring lexevs and cts2 and getting it up and running. This user will be loading HL7 next.

Team Absences

Mayo Team

  • Deepak - Sept 1-6?, Sept 5
  • Cory - August 12, Sept 5
  • Scott - August 15, Sept 5
  • Craig - August 24 -29, Sept 5

NCI

  • Rob Wynne - Sept. 1-5

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