NIH | National Cancer Institute | NCI Wiki  

 Attendees

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

De Coronado, Sherri    

NIH/NCI   x

Safran, Tracy

NIH/NCI   x
Ong, Kim L
ISx
Lucas, Jason R
ISx
Bauer, Scott  Mayox
Stancl, Craig
Mayox
Endle,  CoryMayox
Wynne, Robert    NIH/NCIx
Tran, Tin    NIH/NCI [C] x
Carlsen, Brian (NIH/NCI) [C] 
Wong, Joanne   

Kuntipuram, Kumar

 x

Action Items

 #AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
293JasonCheck into Mayo being designated a trusted site2015.06.03  open

Progress

  
Scott
  • Sprint 8
  • On going Support

Cory
  • Sprint 8
  • On going Support
Craig
  • Sprint 8
  • Agile Admin

Agenda

Sprint Status

Current Sprint - Sprint 8 (July 9, 2015 - July 22, 2015)

LexEVS 6.4 Agile Development - Sprint Status - Sprint 8

 

Sprint Planning

Issue Prioritization

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

LEXEVS-1017 and LEXEVS-1029 should be worked on as part of 6.4.


Issue Grooming

Prioritize JIRA issues (fix version 6.4)

Key Summary T Created Reporter P Status Labels
Loading...
Refresh

Multi-Index Prototype Status

  • Results (Scott)

Prototype is complete and have results to review.

Times shown are better for many areas. 

For multi-index searching, results were slightly higher, but still < 100 ms.

Two questions from NCI came up:

  • Will the performance hold up when we use real data.
  • When we go to a multi user environment and multi queries, will the performance hold up?

Local XSD Resolution

  • Resolution and Priority (Scott)

LEXEVS-1029 was worked on to put in a temporary fix.

NCI has suggested to just point at a local copy of the XSDs being that they don't change often.

We should complete this issue in 6.4.

6.3 Deployment Status

  • NCI Maven Mirror Update (Cory)

CTS2 framework 1.2.0.FINAL on Informatics maven and build works against this.

NCI's Nexus server is no longer blocking the Mayo Nexus Proxy after a restart.

The goal is for NCI to be able to build lexevs CTS2 service. Mayo will put the correct CTS2 framework 1.2.0.RC1 artifacts on maven to allow NCI to mirror and build.

lexevs-service has be successfully deployed / tested on QA.

OBI Load

  • Update and next steps (Scott)

The OWL1 source was successfully loaded with OWL2 loader.

Scott to send the output from the load to NCI to review the hierarchy.

Possibly note that the content that is too long has a truncated marker on it.

May need to fix the inverse properties.  Inner classes (inverse properties) are not being parsed.

CTS2 Doc Service - NodeJS/NPM versions

  • NCI Tech Stack (Gilberto)

The NCI infrastructure group will not support Redis.  If we add Redis, NCI will need to support the entire server upgrade/maintenance.

MongoDB will be supported.  Redis will not be supported.

Our CTS2 service API docs can run without Redis when we upgrade to the latest Node.js and NPM.

Gilberto will follow up if Node.js and NPM will be supported.

VPN and network evaluation

  • Update from Gilberto and Jason
 No updates from Mark.  Jason will follow up with him.

External Request

  • ?

 

 

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