NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

NameRolePresent
Remennik, LyubovNIH/NCIx

De Coronado, Sherri    

NIH/NCI   

Safran, Tracy

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

Kuntipuram, Kumar

Wynne, Robert    

NIH/NCI [C]
KuntipuramSolie, KumarChuckNIH/NCI [C]x
SolieTrikha, ChuckAkhileshNIH/NCI [C]
Trong, TracyNIH/NCI [C]
Kondareddy, SwathiNIH/NCI [C]x

Whiteman, Lori 

(NIH/NCI) [C]
Kisler, BronNIH/NCI [C]

...

EVS Weekly Tech Meeting (Systems focus)

Discussion Points:

  • Systems related topics:
    • LexEVS
    • Browser/Tools
    • Data
    • Systems
    • Triple Store/EVS API EVSRESTAPI firewall exceptions status
    • No updates. Chuck will follow up with Jason.

Decision Points:

Roll Call

Sprint Status


Current Sprint -  Sprint 98 (December 20, 2018 – January 2, 2018)

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

Planned Activities

  • Loader Fixes
  • Security Updates
Anticipated Releases

  • Release 6.5.2 RC 2
LexEVS Loader
  • Release 6.5.1.
2

Discussion Points:

Decision Points:

Rob will deploy on Dev, if it hasn't been already
  • 3 (loader updates)
  • Loader Fixes

Anticipated Releases

  • Release 6.5.2
LexEVS Release 6.5.2 RC 12

Discussion Points:

The QA team will be ready to test this version when it is deployed to the QA tier.

Decision Points:

Mapping fixes for the LexEVS remote API

Discussion Points:

Kim was working on a project for alternative to creating the mappings in CSV format outside the browsers.

  • Jira
    serverNCI Tracker
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId7954a81f-12da-3366-a0ef-97c806660e7c
    keyLEXEVS-4240
  • Kim would like source to target term/code mapping data to be populatedThe LexEVS team did some preliminary review of this issue and added comments to the JIRA issue.
  • Kim suggested that this should be in the next release (6.5.2)

Decision Points:

  • We will need to discuss with Lyuba the priority of this issue. 
    • Should this go into the next release (6.5.2)?
  • Scott will investigate how much work this issue requires.
    • call could be made locally instead of over RMI. 
      • This will make the implementation more simple and faster.

    Decision Points:

    GitHub security alerts

    Discussion Points:

    • The LexEVS has a list of its LexEVS security alerts and will need to have a contact to send this list to and discuss.

    Decision Points:

    • Determine the security contact to discuss LexEVS security alerts with.
    Rob’s tasks and knowledge transfer
    • Lyuba requested that we need to determine the effort to eliminate these git security issues.
    • Other teams are not sure how to proceed either.
    • These issues were reported from Git, not from the security team. 
    • The LexEVS team has a document that has all of the issues and possible mitigation

    Discussion Points:

    • Rob is transitioning with Tracy and Akelesh.
    • He has a spreadsheet for tracking this.

    Decision Points:

    • Cory and Jason should add Akelesh to this meeting.
    • Scott will re-send the security issue document to Lyuba and team.
    EVS Service and Architecture Group (Tracy)Tracy’s work load

    Discussion Points:

    • Rob was doing CDISC publications.  Tracy will be taking over this task.
    • This CDISC publication is on 12/21.

    Decision Points:

    Mapping tool(s)

    LexEVS External Users

    Discussion Points:

    • Agenda for the kick-off meeting on the requirements for the mapping tool(s): What we have from previous years (Kim, Mayo team, Rob’s scripts…), Demo (Kim?)
    • Rob suggested that there may be two parts to this mapping:
      • Matching (LexEVS?) and Curation
    • Lori suggested there will be requests for mapping to NCIt and other terminologies (will need Meta for other terminologies).
    • Lori also suggested the mapping tool should be able to handle different spellings of the same word (such as British spelling) and synonyms (ex. stomach cancer and the synonyms of this)
    • This mapping tool will hopefully decrease the manual load for the editor's work.
    • We will need semantic mapping.
    • Kim gave a demo of his mapping tool.

    Decision Points:

    • Lori will follow up with Lyuba about the kickoff meeting.
    Value Set Definitions - REST services not working

    Discussion Points:

    • Update from Scott on DB on DEV
      • The load has the updates from our fix.  DB looks OK.  We will need to determine if there is an API fix necessary or if it's an additional loader fix.
      • The namespaces and coding scheme relationship isn't connected how we expected.
      • This should be just a lexevs REST API issue.

    Decision Points:

    • Scott to create a JIRA item to investigate/fix this issue.
    EVS Service and Architecture Group (Tracy)

    Discussion Points:

    Decision Points:

    LexEVS External Users

    Discussion Points:

    Decision Points:

    Decision Points:

    Cloud team meeting

    Discussion Points:

    • Lyuba and the team had a meeting with the cloud team to look at preliminary use of the cloud.

    Decision Points:

    Team Meetings

    Discussion Points:

    Decision Points:

    • 12/26 No EVS meeting
    • 1/2 We will have the EVS meeting
    Team Absences

    Mayo Team

    • Cory - 12/24, 12,25, 12/31, 1/1
    • Scott - 12/24, 12,25, 12/26, 1/1
    • Craig - 12/24, 12,25, , 12/31, 1/1

    NCI

    • Tracy - 12/19 - 12/30
      Rob - Last day 12/14
    • Kim -

    JIRA Issues

    Recent LexEVS Related Bugs and Features (within last week)

    ...