NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Old Version 28

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

Saved on

compared with

New Version 29

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

Saved on

Key

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

...

TimeLocationTopicsParticipantsResources
 9:00 AM - 10:00 AM3-W-030
EVS Architecture

Discuss Potential of using a variety of architectures

Proposed topics for discussion:

  • Micro services
    • Considerations:
      • Determine how to synchronize data on the back-end. LexEVS DB and Triple Store need to be in sync when NCIt information (such as value sets) changes. 
      • Determine the potential of a loader that relies on SPARQL queries (after SPARQL query load, kick off LexEVS loader)
  • LexEVS integration with EVS Triple Store
    • Considerations:
      • Determine use of triple store calls in parallel with LexEVS DB
      • Determine performance improvements over LexEVS DB
      • Determine what calls could be made to the triple store instead of LexEVS.
      • Determine use of Stardog built in graph database.
      • Determine performance considerations for hierarchy traversal for graph resolution.
  • Future implementation considerations

Gilberto Fragoso

Kim Ong

Tracy Safran

Rob Wynne

Larry Wright

Margaret Haber

Sherri De Coronado

Bron Kisler

Systems team

John Cambell /Ruth Monterio users of the SQARL

MicroServiceProp.pptx

TripleStore.pptx

Attendees: 

Jason Lucas, Kim Ong, John Campbell, Larry Wright, Bron Kisler, Rob Wynn, Craig Stancl, Cory Endle, Scott Bauer, Kumar, Luba, Sherri De Coronado, Margaret Haber, Gilberto Fragoso, Liz, Denise

Discussion Points:Decision Points:

  • Overview of EVS Architecture
    • Need to had value sets and mappings.
    • Would like to include all the ways that reports are created. (content channels - as separate slide)
    • Need to incude additional sources being loaded into SPARQL.
    • Consider adding channels from triplestore to LexEVS.
    • Add detail for Browser and assiciated dependencies
    • Change from SPARQL to TripleStore.  

 

Decision Points:

  • Action Items:
    • Update Architecture to had value sets and mappings.
    • Update Architecture to include all the ways that reports are created. (content channels - as separate slide)
    • Update Architecture to incude additional sources being loaded into SPARQL.
    • Update Architecture by adding channels from triplestore to LexEVS.
    • Update Architecture to add detail for Browser and assiciated dependencies
    • Update Architecture to change from SPARQL to TripleStore.  

 

TimeLocationTopicsParticipantsResources
10:00 AM - 12:00 PM

10:00-10:30

3-W-030

11:00-12:30

TE-420

(Can't fill gap 10:30-11:00)

EVS Architecture - Technical Discussion with Systems team

Discuss technical aspects of potentially using a variety of architectures

Proposed topics for discussion:

  • Micro services
    • Considerations:
      • Embedded Tomcat implementations
      • Alternative web service platforms
      • Container/Port clashes
  • LexEVS integration with EVS Triple Store
    • Considerations:
      • SPARQL clients
      • Docker options
  • Future implementation considerations
    • Java
    • Python
    • Node.js/javascript
    • Others?

Systems team

 

...

Discussion Points:

Decision Points:

 

TimeLocationTopicsParticipantsResources
 1:00 PM - 2:00 PM3-W-030
EVS Project Group Discussion (During regular call-in time)

Proposed topics for discussion:

  • (High Level Overview) Discuss direct calls to NCIt for value sets
    • Performance
    • Workflow
    • API Implications
  • Discuss Mappings and cross-walking coding schemes

  •   SwissProt, ICD-0-3, and MED-RT as the successor of NDRFT
    • Associations from/to
    • Cross walking coding schemes
    • Loader considerations for Mesh, RxNorm

Kim Ong

Tracy Safran

Rob Wynne

Editor's Representative/Margaret Haber

Larry Wright

Sherri De Coronado

Gilberto Fragoso

Proposed Biomarker Terminology Sets_2017-12-05.pptx

Attendees: 

Discussion Points:

Decision Points:

 

TimeLocationTopicsParticipantsResources
2:00 PM - 3:00 PM3-W-030
NCI Systems Discussions

Proposed topics for discussion:

  • Discuss 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.
  • Discuss Tech Stack Upgrades
    • Discuss DB upgrade: MySQL 5.6 vs. MariaDB
    • Discuss migrating from Anthill Pro to Jenkins

Jacob and Systems team

Gilberto Fragoso

Rob Wynne

Tracy Safran

Kim Ong

Larry Wright

Margaret Haber

Sherri De Coronado

Q/A (Sana)

 

Attendees: 

Discussion Points:

Decision Points:

 

TimeLocationTopicsParticipantsResources

3:00 PM - 4:00 PM

(added meeting)

3-W-030
User Group Discussion - caDSR 

Continued discussion of current API

  • APIs: Java, REST (CTS2 or 3-store), SPARQL

caDSR - Philippa,

Vikram, Natalia, Rui

EVS REST API

CTS2 REST API

Attendees: 

Discussion Points:

...