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 47 (January 5, 2017 – January 18, 2017)

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

LexEVS Java 1.8 & MySQL 5.6 Environment

  • Status update: Jason

Discussion Points:

  • Jacob mentioned that they were waiting for the DB specialist. 
  • He is anticipating this to be completed next week.

Decision Points:

6.4.1.3 Snapshot build update

Discussion Points:

Decision Points:

NCI Nexus Server Migration Update

Discussion Points:

Decision Points:

Value Set Architecture Update

Discussion Points:

  • The Mayo dev team will be meeting with Kim tomorrow to continue gathering requirements.

Decision Points:

Transitive OWL Discussion

  • Blank Nodes
  • Implementation Considerations

Discussion Points:

  • Jira
    serverNCI Tracker
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId7954a81f-12da-3366-a0ef-97c806660e7c
    keyLEXEVS-2585
  • Jira
    serverNCI Tracker
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId7954a81f-12da-3366-a0ef-97c806660e7c
    keyLEXEVS-2651
  • Scott has been researching how blank nodes are handled with respect to transitive closure in OWL.
  • Larry mentioned that role group is being lost in the LexEVS model.
  • We can remove the anonymous nodes in transitive closure.  They will still be available in the API to the browser.

Decision Points:

  • Scott will create JIRA issues to remove anonymous nodes from transitive closure.
  • Better understand role group and any use cases associated with it.
echache issue

Discussion Points:

  • This was an outside user that accessed the NCIT through a search and the page didn't load.
  • Others tested this and it worked fine. 
  • However, Larry saw it happen again today searching on the term browser.
  • This failed initially on Chrome (was also seen in IE, FF, and Chrome).
  • Scott mentioned that there may have been some invalid text in the history API.
  • Kim suggested that this didn't have anything to do with the history API.
  • This was seen on the PROD server.
  • This issue was seen on the NCIT.

Decision Points:

  • Rob to request the container to be restarted.
caCORE follow up

Discussion Points:

  • We followed up with Bob Kline and mentioned that the CTS2 service returns the same data but in a different format.
  • The lexevs API URL can be modified so it doesn't change.

Decision Points:

CTRP Thread Issue

  • Cory to update

Discussion Points:

  • This issue has been resolved.
  • The fix has been put into the 6.4.2 branch.

Decision Points:

LexEVS External Users

Discussion Points:

Decision Points:

Proposed Backlog Review Items
Team Absences

Mayo Team

  • Cory - Jan 27
  • Scott -
  • Craig -

NCI

  • Tracy
    • Feb 21-24
  • Rob

...