NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Old Version 1

changes.mady.by.user Unknown User (endlecm)

Saved on

compared with

New Version 2

changes.mady.by.user Unknown User (endlecm)

Saved on

Key

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

...

EVS Weekly Tech Meeting

Discussion Points:

  • LexEVS
    • Updates for DEV system to be configured to run Docker containers.
    • CTS2 on-line documentation is running on NCI Dev system and Heroku.
      • Jenkins is set up to build/deploy on dev.
    • Lexevs-system-tests - have been updated and are running successfully.
    • MySQL timeout during value set load.
  • Browser/Tools
  • Data
  • Systems
  • Triple Store/EVS API

Decision Points:

Roll Call 

Sprint Status

 

Current Sprint -  Sprint 75 (February 1, 2018 – February 14, 2018)


16X237 Agile Development - Sprint Status#16X237AgileDevelopment-SprintStatus-Sprint75
API Meeting/Discussion Update

Discussion Points:

  • Bron and Tracy are out today.
    • Scott gave a quick overview of the last meeting.  Much of the time was discussing and documenting the existing architecture.

  • Margaret suggested this meeting should include requirements gathering and gap determination as well as day to day needs.

    • Decision Points:

    Scott will send a link to the slides to Margaret and Lyubov.

    Empty value sets - Update (Rob)

    Discussion Points:

    •  VS have loaded last night on Dev.
    • Should we load empty VS?  Rob suggested that it may be OK.
      • The browser should be able to handle an empty VS.

    Decision Points:

    Resolved Value Set rework

    Discussion Points:

    • Resolved VS were persisted in the past.  They are now dynamically resolved (without being persisted).
    • VS definitions are still be persisted to the system.
    • We depend upon the resolved VS for the existing CTS2 REST API.
      • The lexevs resolved value set API will need to be updated to still return the resolved value sets.
    • The VS search API will change (source asserted API).  The browser will need to use the new API.

    Decision Points:

    Rob suggested that this scenario should work

    :

    • Browser - If multiple value sets are selected, and one is empty, the browser should still get results back.
    • If a user clicks on the empty value set in the hierarchy, they should be able to see the value set information and an empty value set.
      • The user currently see a "null" response.

     

    LexEVS External Users

    Discussion Points:

    • caDSR - LexEVS REST vs Java API discussion on Friday.

    Decision Points:

    Team Absences

    Mayo Team

    • Cory -
    • Scott -
    • Craig -

    NCI

    • Tracy -
    • Rob - 2/13-3/6
    • Bron -
    • Sana -
    • Kim -

    ...