NIH | National Cancer Institute | NCI Wiki  

Error rendering macro 'rw-search'

null

Versions Compared

Old Version 3

changes.mady.by.user Unknown User (endlecm)

Saved on

compared with

New Version 4

changes.mady.by.user Unknown User (endlecm)

Saved on

Key

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

...

The purpose of this document is to capture proposed agenda topics for the 2017 technical face to face meeting between NCI and Mayo.

 

Agenda ItemPurpose/GoalsProposed DurationParticipantsTime/Date RestrictionsRequested / Proposed ByAdded to Schedule
New REST APIs

Discuss a new REST API to supplement CTS2 REST Services

  • Examine current CTS2 REST API
    • Discuss what doesn't work for the end users.
  • Discuss user requirements for a new REST API
    • Document the gaps from CTS2 REST API and user requirements.
   Mayo Team/Larry 

Surfacing terminology history in a REST service

  • NCIt and ULMS

Discuss what history information is required by the user to be returned.

  • Discuss if this fits in to LexEVS or is part of a new REST API
     
Surfacing history of value sets in a REST service      
LexEVS integration with EVS Triple Store

Discuss using triple store calls in parallel with LexEVS DB

  • Explore if the EVS triple store offers performance improvements over LexEVS DB
  • Discuss what calls could be made to the triple store.
     
Stardog and its built in graph database      
Direct calls to NCIt for value sets      

NCI Systems Discussions

  • CI and Docker Status/Roadmap
  • Tech Stack Upgrades
  • CI and Docker Status/Roadmap
    • Discuss the current status of the Docker scripts used to build/test LexEVS components.
      • Discuss the current NCI Docker images used in LexEVS tests.
    • Discuss NCI's current status and future plans to use Docker.
  • Tech Stack Upgrades
    • Discuss DB upgrade: MySQL 5.6 vs. MariaDB
 Jacob and Systems team Mayo Team 
Micro services

Discuss Potential of using Micro Issues

  • Synchronization of data on the back-end
    • LexEVS DB and Triple Store need to be in sync when NCIt information (such as value sets) changes. 
  • Loader that relies on SPARQL queries
      • After SPARQL query to load, kick off LexEVS loader
   Mayo Team/Larry 
Services/updates for our customers

Discuss how to update customers with jar files when updating LexEVS versions

  • Releases need to be backwards compatible

Discuss evolving to all REST services and possibility of retiring the Java API

  • Customers would need all of the similar services.
  • What needs to be enhanced in the REST API need to support our Java API customers.
     
Systems Issues

Discuss systems deployment issues to Stage/Prod.

  • Issues migrating from 6.4 to 6.5 database.
  • Performance relating to SSDs, Lucene and shared volumes.

Discuss migrating from Anthill Pro to Jenkins