Page History

Discussion Points:

• LexEVS
  • Rob deployed 6.5 Dev DB refresh,
  • a 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.
• Systems
  • AHP → 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 (August 31, 2017 – September 13, 2017)

• Tier Deployment
  • Data deployment

Discussion Points:

Decision Points:

Discussion Points: 

Decision Points:

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.

• 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  VS definitions 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.

Discussion Points: 

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

Decision Points:

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:

Mayo Team

• Cory -
• Scott -
• Craig - 9/13

NCI

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