NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Key

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

...

Sprint Status

 

Current Sprint  Sprint 48 (January 19, 2017 – February 1, 2017)

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

LexEVS Java 1.8 & MySQL 5.6 Environment

  • Status update: Jason

Discussion Points:

  • During our morning meeting, Jacob asked if we wanted to use CentOS 7 or RedHat 7. 
  • We suggested CentOS 7 as that is part of the tech stack that will be used in production. 

Decision Points:

  • We requested to go with CentOS 7 as this is what will be used in PRODproduction.

6.4.1.3 Snapshot build update

Discussion Points:

Decision Points:

  • Mayo will build another 6.4.1.3.SNAPSHOT by this Friday for Rob to use for another load on Monday.
  • Mayo team will notify NCI dev team when this is complete.

NCI Nexus Server Migration Update

Discussion Points:

Decision Points:

Value Set Architecture Update

Discussion Points:

  • LexEVS 6.5.1 Value Set Architecture Requirements 
  • Jira
    serverNCI Tracker
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId7954a81f-12da-3366-a0ef-97c806660e7c
    keyLEXEVS-1157
  • Jira
    serverNCI Tracker
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId7954a81f-12da-3366-a0ef-97c806660e7c
    keyLEXEVS-2670
     
  • After three different meetings, we came up with some value set requirements.
  • The two main requirements are:
    • Better logging to help determine if there were any failures for resolving the 760+ value sets.
    • Resolving all 760+ value sets should be quicker.
  • Scott has come up with a potential solution through the work in the above two JIRA items.  He created scripts to do the following:
    • Load value set definitions
    • Load resolved value set coding scheme
    • Removal tools for the above
  • Rob and Tracy requested to allow to provide tags for coding schemes and to log the names of the value sets.  This has added some database calls and slows it down some.

Decision Points:

  • Scott will run against all of the value sets to test performance locally.  He will get the list from Rob or Tracy.
  • We will create a snapshot build for Rob to test a load early next week.
eCache issue update

Discussion Points:

  • This happens when a user clicks on links in the search results from the browser.
  • We will continue to monitor this and investigate when this happens again.

Decision Points:

  • Scott will request access to the browser logs from Jacob for further investigation.

caCORE follow up

  • lexevs API URL
  • Follow up with Bob regarding data services

Discussion Points:

Decision Points:

CTRP Thread Issue

  • Data Services discussion

Discussion Points:

Decision Points:

  • Tracy will contact CTRP to start a conversation about the data services going away in the next release.
LexEVS External Users

Discussion Points:

Decision Points:

CTS2 handshake error

Discussion Points:

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

Decision Points:

  • Mayo team will document this issue on the CTS2 wiki.  There is nothing else to do.
Proposed Backlog Review Items

Discussion Points:

  • We groomed some tree extension issues this week.   

Decision Points:

  • We will come up with a new list of issues to groom for next week.
Decision Points:
Team Absences

Mayo Team

  • Cory - Jan 27
  • Scott -
  • Craig -

NCI

  • Tracy
    • Feb 21-24
  • Rob

...