NIH | National Cancer Institute | NCI Wiki  

Attendees

NameRolePresent
Remennik, LyubovNIH/NCIx

De Coronado, Sherri    

NIH/NCI   x

Safran, Tracy

NIH/NCI [C]x
Ong, Kim L
IS
Lucas, Jason R
ISx
Bauer, Scott  Mayox
Stancl, Craig
Mayox
Endle,  CoryMayox
Wynne, Robert    NIH/NCI [C]x

Kuntipuram, Kumar

NIH/NCI [C]x
Mensah, JacobNIH/NCI [C]
Trong, TracyNIH/NCI [C]
Kondareddy, SwathiNIH/NCI [C]
Kisler, BronNIH/NCI [C]

Action Items

AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus






Agenda

EVS Weekly Tech Meeting (Systems focus)

Discussion Points:

  • Systems related topics:
    • LexEVS
      • Data Dev
      • System Tests - Jenkins build failing
    • Browser/Tools
    • Data
    • Systems
    • Triple Store/EVS API

Decision Points:

Roll Call

Sprint Status


Current Sprint -  Sprint 94 (October 25, 2018 – November 7, 2018)

16X237 Agile Development - Sprint Status#16X237AgileDevelopment-SprintStatus-Sprint94

Planned Activities

  • Review Security issues
  • Data Dev performance testing
  • EVS Service and Architecture Group

Anticipated Releases

  • Release 6.5.2
  • Release 6.5.1.2
LexEVS Wiki Updates

Discussion Points:

  • 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 updates.
EVS Service and Architecture Group

Discussion Points:

  • Team will meet next week.

Decision Points:

Med-RT

Discussion Points:

  • The long term priority is to create a LexEVS loader for MED-RT.
  • Short term priority is the single source extraction - This is on Dev.
  • There is also a MED-RT browser issue that the LexEVS team needs to look at.

Decision Points:

LexEVS Security Issue

Discussion Points:

  • 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.
Power outage

Discussion Points:

  • December 8 power outage.
  • We will need to test our services when the power is back on (December 9/10).

Decision Points:

LexEVS External Users

Discussion Points:

Decision Points:

Team Absences

Mayo Team

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

NCI

  • Tracy -
  • Rob - 
  • Kim -

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.5 LexEVS Related Issues

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Loading...
Refresh

6.5 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











  • No labels