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]  
Carlsen, Brian (NIH/NCI) [C]x
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 11
  • On going Support
Cory
  • Sprint 11
  • On going Support
Craig
  • Sprint 11
  • Agile Admin

Agenda

Sprint Status

Current Sprint - Sprint 11 (August 20, 2015 - September 2, 2015)

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

Sprint Planning

LexEVS 6.4 Agile Development - Sprint Status

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

 


Issue Grooming

Prioritize JIRA issues (fix version 6.4)

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

 

 

Single special character search

  • LEXEVS-1131
  • Discussion with Kim

Attempting to search on single characters: <, >, and ! 

Will we need to support these kind of queries?  It would be additional work for the DEV team.  Lucene doesn't advise this.

This should be working with the new Lucene work. We will need to test.

These special properties could have their own analyzers for searching.

Chemical name searches

  • Updated from Scott

There may be a small set of users that would want to be able to search on chemical names / single characters.

We can provide analyzers for these and store them.

This could be part of an advanced search.  We would match up the query with specific analyzers.

We should consider the potential of SQL injections for this implementation.

HTTPS - Applications Migrating to HTTPS

  • LexEVS CTS2 REST Services - via Apache
  • LexEVS API Services

The REST service should be fine.  We will just need to redirect in the Apache configuration.

LexEVS service would need to be updated for HTTPS.

TODO:  Create JIRA items and put them in the backlog for after 6.4.

OBI load evaluation

  • Update from Gilberto
NCI will look at this through the browser.
Maven hosting of LexEVS jars

Tracy suggested just the LexEVS client and it's dependencies be hosted out on Maven.

Other projects at NCI are purely maven projects and would like this as an artifact.

TODO: Mayo to look at making the LexEVS client a Maven artifact.

Sorting of JSON objects in tree implementation

Do we have the ability to sort the JSON Nodes that are returned.

TODO: Mayo to investigate if we can sort the results.  This should be part of 6.4.

VPN and network evaluation

  • Update from Gilberto and Jason
Craig is looking who the Mayo networking POC is for the VPN discussion.

External Requests

  • Lekha Venugopal (CTEP)
This  was an apache re-write issue that has been resolved.

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