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 [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]x
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
Cory

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

2016.03.092016.08.30 Open
CoryCreate JIRA issue to remove caCore legacy code2016.04.202016.08.30 Open

Progress

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

Agenda

LexEVS External Users

Sprint Status

 

Current Sprint  Sprint 35 (July 21, 2016 – August 3, 2016)

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

QA Tier Status

  • NCI-RITM0031271: New container on QA for the LexEVS 6.4 Remote API
  • NCI-RITM0031282: CTS2 AHP on QA
  • AppScan
Jacob is assigned these tasks and is working on them.

OWL2 Discussion

  • LEXEVS-1299 - Supported properties (Kim/Gilberto)
  • LEXEVS-1976 - Complex property loader directives
  • LEXEVS-1160 - NDFRT Loader - Restrictions on a class not displayed in the browser.

LEXEVS-1299 - Scott asked if these properties belong in the system as supported properties?

  • Scott suggested there is a way to eliminate the duplicates.
  • TODO: Scott will create a JIRA item for the work above.

LEXEVS-1976 - Scott suggested the preferences could be updated for this.

  • Scott is suggesting keeping the hard coded items and they can be modified via the preference file. This specific parsing has to be "turned on" via the preferences file.
  • Gilberto mentioned in OWL2, these values do not exist. They will be pre-floating properties.
  • The decision is to leave it in the OWL2 loader. The default is off. It will only be on/available when specifically called in the preferences file.

LEXEVS-1160 - Scott suggested that the browser should add logic to determine what to display.

  • Tracy and Gilberto agreed with this.

OWL2 Loader build

  • Specific 6.4 build with loader fixes.
  • Can NCI verify the fixes in this build?
TODO: Cory/Scott will create a build with the OWL2 loader enhancements in the next sprint.

LexEVS using HTTPs - December 31st, 2016 deadline

  • Discuss possibility of updating 6.3 or 6.4 for HTTPs for existing customers

There is an NCI department level requirement that all services need to use HTTPs. If they don't, the current services will be shutdown at the end of December.

We don't want to force end users to migrate to 6.5, if that had the HTTPs fix in it by the end of the year.

Larry suggested that we need to upgrade the existing LexEVS 6.3 and/or 6.4 to use HTTPs prior to the end of the year.

If LexEVS 6.3 was updated and the end user clients have to rebuild their clients, then we should just consider upgrading the clients to the LexEVS 6.4/6.5

The Mayo team will start to investigate and discuss with the NCI systems team.

LexEVS versions - Previous/Deprecated/Retired

LexEVS 6.3 should be moved to deprecated.

Remove the "Previous" section.

TODO: Cory will make these changes.

LEXEVS-2131 - Getting issue details... STATUS

  • Review column length options

Based on the investigation from Cory, the field is a VARCHAR (250). We can increase the length to accommodate a longer description.

Larry suggested increasing the length to 1000.

Tracy agreed with this.

TODO: Cory will send out an email to confirm everyone agrees with the suggestion from Larry.

LexEVS External Users

We think this may be a source issue - loading from RRF.

Brian will look into this issue.

Team Absences

Mayo Team

  • Scott - August 1st
  • Craig - August 24th - 29th

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