NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Old Version 1

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

Saved on

compared with

New Version Current

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

Saved on

Key

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

...

NameRolePresent
Wright, Larry NIH/NCI   x
Fragoso, Gilberto NIH/NCI     

De Coronado, Sherri    

NIH/NCI    x

Safran, Tracy

NIH/NCI [C] x
Ong, Kim L
IS x
Lucas, Jason R
IS x
Bauer, Scott  Mayo x
Stancl, Craig
Mayo x
Endle,  CoryMayo x
Wynne, Robert    NIH/NCI [C] x
Tran, Tin    NIH/NCI [C]  

Kuntipuram, Kumar

NIH/NCI [C] x
Haber, MargaretNIH/NCI

 

Mensah, JacobNIH/NCI [C] 
Trong, TracyNIH/NCI [C]x
Din, SanaNIH/NCI [C] x
Kessler, Ron  x

Action Items

AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
      

Agenda

EVS Weekly Tech Meeting

Discussion Points:

  • LexEVS
  • Rob deployed 6.5 Dev DB refresh
  • A mass VS load was done on Data QA
    • We asked if the 6.5.1 (dev snapshot) is on NCI dev
      • Testing is ongoing on 6.5.1 (
    dev snapshot)  LexEVS Remote API is on NCI dev
  • The SIW code is working for them.
      • Dev branch)
    • Browser/Tools
    • Rob found an issue. "Show other" link isn't behaving properly with redirecting.  This is being investigated, but not a show stopper.
    • Data
      • Monthy's went to 6.5 stage and 6.4 stage today.  Should go to prod by Friday
    • Systems
  • Data
    • 4 new versions have been uploaded.
    • SystemsAHP → Jenkins migration - this will require some effort from the LexEVS team.  The systems team will provide the server for this.
    • Triple Store/EVS API
  • Ticket has been submitted to move these up the tiers.

    • Decision Points:

    Kim would like to see the Java doc for the LexEVS Remote API.  Scott will point him to it.
    • Cory will get the latest status from the systems team on any Docker accomplishments since the last update.

    Sprint Status

     

    Current Sprint -  Sprint

    64

    65 (

    August 31

    September 14, 2017 – September

    13

    27, 2017)


    16X237 Agile Development - Sprint Status#16X237AgileDevelopment-SprintStatus-
    Sprint64
    Sprint65
    Tier Deployment - Update
    • Tier Deployment
      • Data deployment

    Discussion Points:

    Decision Points:

    New Rest Service Plugin for LexEVS

    Discussion Points: 

    • No new discussion

    Decision Points:

    NCI Metathesaurus namespace - ns1363824265
    Value Set Updates -
    • Hierarchy prioritization

    Discussion Points: 

    Decision Points:

    • We agreed to create a JIRA item to capture this.
    Value Set Updates -
    • What is the criteria to determine a value set needs to be updated

    Discussion Points: 

    • What indicates a value set has changed and needs to be reloaded? We will need to discuss what constitutes a change with the team.
    • A value set definition changes when:
      • Published value set value is yes (and didn't exist before)
      • Definition changes
      • TDS location changes
    • Resolved VS 
      • Every RVS may need to be updated each time there is a new version of NCIt, because it is resolved against the new version.
    • There may be some simple comparisons that can be made that will work well.
    • Would we be able to use the value set change history?
      • If a value set is updated based on the history, we could reload it.

    Decision Points:

    • The Mayo team will set up a meeting to discuss this and other value set issues and their priorities.
    Curation tool - Hierarchy Discussion

    Discussion Points: 

    • The initial code was not robust.  Changes were suggested by Scott/Tracy.
    Decision Points:

    • Jira
      serverNCI Tracker
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId7954a81f-12da-3366-a0ef-97c806660e7c
      keyLEXEVS-2969
    • Scott asked if this value set hierarchy work should be put into the next sprint.
      • Some value sets have structure (like neoplasm).  Should this be implemented in LexEVS so the structure can be viewed in the browser?

    Decision Points:

    • No decision was made to put it in the next sprint.
    Value Set Namespace discussion

    Discussion Points: 

    • Jira
      serverNCI Tracker
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId7954a81f-12da-3366-a0ef-97c806660e7c
      keyLEXEVS-1732

       
    • Value sets that have codes from multiple coding schemes vs. union of value sets from multiple coding schemes.
    • Scott asked if  we can use the namespace and the source version?
      • Kim suggested that this might be acceptable.

    Decision Points:

    • We will continue this discussion offline with Kim.
    LexEVS Remote Client updated needed

    Discussion Points: 

    • Jira
      serverNCI Tracker
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId7954a81f-12da-3366-a0ef-97c806660e7c
      keyLEXREMCLI-15
    • This was last updated for 6.4.2 and needs to be updated soon.

    Decision Points:

    • We will update/build the client for 6.5.0 and above. 
    • This work will be done in the next sprint.
    • We will also put a notice on the 6.4.2 link indicating users to contact us for assistance with this client.

    Backlog grooming - plan meeting

    Discussion Points: 

    The development team will meet first to groom the backlog and then we will set up a meeting with the extended team to review and prioritize
    • We will plan on spending some time with the technical team to clean up the backlog.

    Decision Points:

    Development team
    • Craig will set up a meeting
    with the extended team for backlog grooming
    • for this.

    LexEVS External Users

    Discussion Points: 

    Decision Points:

    Team Absences

    Mayo Team

    • Cory -
    • Scott - 9/28
    • Craig - 9/21

    NCI

    • Tracy - 9/22 - 9/29
    • Rob -
    • Kim -
    • Larry - 9/21-9/29

    JIRA Issues

    Recent LexEVS Related Bugs and Features (within last week)

    ...