NIH | National Cancer Institute | NCI Wiki  

  • Created by Unknown User (endlecm), last modified on May 18, 2016

 Attendees

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

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
Mayo 
Endle,  CoryMayox
Sharma, DeepakMayo 
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
Rob

Close issue 

  LEXEVS-1516 - Getting issue details... STATUS

2016.02.092016.04.10 Open
Craig

Create JIRA issue to update CTS2 service to use Apache Commons Collections Version 3.2.1 (security issue)

2016.03.092016.03.30 Open
CraigCreate JIRA issue to remove caCore legacy code2016.04.202016.04.30 Open
CoryUpdate wiki to describe what DBs are supported/tested going forward2016.04.272016.04.30 Open
CoryInvestigate invisible indexes being created.2016.05.102016.05.17 Done

Progress

  
Scott
  • Sprint 30
  • On going Support
Cory
  • Sprint 30
  • On going Support
Deepak
  • Sprint 30
Craig
  • Sprint 30
  • Agile Admin

Agenda

Sprint Status

Current Sprint -  Sprint 30 (May 12, 2016 – May 25, 2016)

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

NCI has deployed LexEVS core API and LexEVS Remote API.

Tracy mentioned that she will test from her client.

Kim has been testing with the remote API. He is running into the issue related to LEXEVS-957. The Mayo team will discuss possible solutions to this issue.

Discuss Issues

  • LEXEVS-1729
  • LEXEVS-1730
  • LEXEVS-1731
  • LEXEVS-1732

We discussed the priority of these JIRA items and if they need to be in the LexEVS 6.4 release.

LEXEVS-1729 - Getting issue details... STATUS

  • Investigate if this is a bug that we can reproduce. If this is a bug, then we need to fix for 6.4

LEXEVS-1730 - Getting issue details... STATUS

  • There is a workaround. This issue can be completed after LexEVS release 6.4.

LEXEVS-1731 - Getting issue details... STATUS

  • Feature request for 6.4.

LEXEVS-1732 - Getting issue details... STATUS

  • There is a workaround. This issue can be completed after LexEVS release 6.4.
NCI DEV deployment updates

LexEVS core API 6.4 and LexEVS Remote API 6.4 war files are deployed. Tracy and Kim have been testing.

CTS2 6.3 - NCI will deploy to existing CTS2 6.3 container. NCI will let us know when this is done and Mayo and NCI will test the API on DEV.

  • Cory to send a link to Tin for our online API.
  • Cory to send JIRA item that was fixed to Tin.
  • Larry would like to move CTS2 6.3 up the tiers to PROD as soon as possible.

CTS2 6.4 - will deploy to a new container that is currently empty.

PIV card updates

No updates.

Kumar asked if Deepak filled out the form: VPN remote access user agreement. Cory will follow up with Deepak.

LexEVS External Users

  • Updates

Gilberto mentioned that there was an app support question from a user at Georgetown University.

Gilberto pointed him to the LexEVS wiki about the LexEVS API and CTS2 API.

Invisible Indexes

These seem to happen when indexes are deleted and the container is still running and holds a reference to them.

One possible workaround is to shutdown the container are restart it. NCI team will continue to look into this.

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