NIH | National Cancer Institute | NCI Wiki  

Error rendering macro 'rw-search'

null

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
  • 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
    • 6.5.1 (dev snapshot)  LexEVS Remote API is on NCI dev
  • The SIW code is working for them.
  • 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
  • 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.

Sprint Status

 

Current Sprint -  Sprint 64 65 (August 31September 14, 2017 – September 1327, 2017)


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

Discussion Points:

Decision Points:

New Rest Service Plugin for LexEVS

Discussion Points: 

Decision Points:

NCI Metathesaurus namespace - ns1363824265

Discussion Points: 

https://lexevscts2.nci.nih.gov/lexevscts2/entities

  • The current namespace for NCI Metathesaurus in CTS2 is: ns1363824265.

    • 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 updatedHierarchy prioritization

    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.
    • Jira
      serverNCI Tracker
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId7954a81f-12da-3366-a0ef-97c806660e7c
      keyLEXEVS-2969

    Decision Points:

    Value Set Namespace discussion

    Discussion Points: 

    • Value sets that have codes from multiple coding schemes vs. union of value sets from multiple coding schemes
    		Curation tool - Hierarchy Discussion

    Discussion Points: 

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

    Decision Points:

    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 the backlog.

    Decision Points:

    Development team will set up meeting with the extended team for backlog grooming.

    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

    ...