Page History

De Coronado, Sherri    

Safran, Tracy

Kuntipuram, Kumar

Discussion Points:

• Systems related topics:

• • LexEVS
    • Data Dev - upgrade DB to Barracuda
      • Jacob will follow up with Yahia for a status.
  • Browser/Tools
  • Data
  • Systems
  • Triple Store/EVS API

Decision Points:

Sprint Status

Discussion Points:

• Tracy has done some LexEVS wiki reorganization at the top level.
• We suggested that the "community code contribution" could probable be archived.
• Tracy will continue working on updating the wiki pages.
• A quick start page was originally suggested for the NCIt access
• No significant changes to mention.
• The Mayo team is available to assist Tracy, if she needs it.
• Tracy mentioned that she will have a preliminary outline of changes by this Friday.
  
• Sherri mentioned that QDC (user) is waiting for this updated documentation.

Decision Points:

• Lyuba suggested that we provide a timeline to complete the wiki updatescan provide additional feedback at the next meeting.

Discussion Points:

• 2018-11-06 Meeting notes
• Team will meet next week.Lyuba would like a timeline for us to come up with a valuation of the EVS services
  

Decision Points:

Discussion Points:

Decision Points:

Discussion Points:

• Reviewed issues
• Prototyped fixes in branches for CTS2, URI Resolver, LexEVS Service
• Created partial updates to LexEVS to gauge the scope of spring updates in LEXEVS-4192
• Alternately removed project with pom file LEXEVS-4199
• Waiting for Kumar to set up a meeting with security, systems, and development teams
• Kumar mentioned that there has been turn over in the security division and it will take time to get everyone together.
• Jacob suggested that we could update/fix our security issues and then they can perform an appscan and nexus scan to see what ports are open and any other security users.
• Tracy mentioned that the remote client users (caDSR) would need to update their client jars if/when we do security upgrades.
• Jacob mentioned in the past, the security team considered issues fixed only when the spring version was upgraded to a version that fixes the vulnerability.
  

Decision Points:

• Jacob will look into what was last done by Phil before he left.
• The LexEVS team will work on security issues and request an appscan and nexus scan on the services.
• Has CTS migrated off from 6.4?  Kumar will ask Tony.  If they have, the 6.4 service will be retired.

Discussion Points:

• We need to meet with NCI development team to discuss how to move more quickly on diagnoses and fixes.

Decision Points:

• Scott will come up with a workflow plan on how to diagnose these issues in the future. 
  
  • Provide a task list of things to look at before considering this is a coding issue

• LexEVS Security issues
  • The team reviewed the security issues and discussed how to proceed.
  • We discussed the usage of AppScans for LexEVS and assumed they should be revealing any real security issues.
• LexEVS users
  • caDSR Tools use LexEVS Remote client

Decision Points:

• We agreed that we need to discuss possible actions with the Systems team.
  • Kumar will set up a meeting to discuss with the Systems team (Phil).We should include the LexEVS team and caDSR (Natalia) in this meeting.

Discussion Points:

• December 8 power outage.
• We will need to test our services when the power is back on (December 9/10).
• This testing will be done by NCI.
  

Decision Points:

LexEVS External Users

Discussion Points:

Decision Points:

Mayo Team

• Cory - 11/9
• Scott - 11/5, 11/6 (PM), 11/7 (AM)
• Craig - 11/2 - 11/8

NCI

• Tracy -
  
• Rob - 
• Kim -