Page History

De Coronado, Sherri    

Safran, Tracy

Kuntipuram, Kumar

Sprint Status

Current Sprint -  Sprint 51 (March 2, 2017 – March 15, 2017)

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

Discussion Points:

• LexEVS 6.5.0 Release
• OWL2 Transition
• Value Set Architecture
• REST Architecture
  
• DevOps: Docker setup at NCI
  

Scott mentioned the OBO loader issue should be considered as well.

Larry suggested that the priority list as follows:

• OWL 2 transition is a priority 
• Value Set loads (issues described by Rob)
  • There are still some loading issues
    
    • Searching against a coding scheme that doesn't exist
    • Rob to provide an example of what if failing.
• LexEVS 6.5.0 Release
• REST Architecture
• Value Set Architecture
• DevOps: Docker setup at NCI

Decision Points:

• Rob to provide example of issues with the value sets that are loaded incorrectly.
• 
  

Discussion Points:

• Rob, Tracy, Scott, and Kim to work together on the new OWL 2 loads and determine why Kim's code is failing.
  • Kim will provide the stack trace of the issue.
   
• Kim to create a JIRA issue for the source qualifier issue that he is seeing in the Terms browser.

Decision Points:

DEV Server Configurations

• DEV Blade
  • 6.5.0 Snapshot

Discussion Points:

• Jacob is waiting on the creation of the MySQL 5.6 DB for the blade server.
• The API set up but pointing to existing 5.6 db for the VM.

• Access to the server and the URLs should be completed before Friday.

• Once the Dev blade system is installed and configured, Kim will test his browser on it.

Decision Points:

Value Set Loading Enhancements

• Planning Update

Discussion Points:

• LexEVS Meeting Minutes - Value Set Architecture Planning Session - 2017.03.02
• Once Tracy and Rob are both back, we will set up a meeting with both of them.
• Rob suggested that he could offer suggestions on where the current workflow is broken.
  

Decision Points:

Discussion Points: 

• REST Service Architecture
• The Mayo team needs to capture the end user requirements and and then come up with some suggested approaches.
• Larry suggested that the CTS2 calls work but may not be efficient for what the user is requesting.
  

Decision Points:

Discussion Points:

Decision Points:

Discussion Points:

Decision Points:

Mayo Team

• Cory -
• Scott - March 14
• Craig -

NCI

• Tracy
  • March 9-17
• Rob
  

  • March 20-24