Page History

...

• 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.  
• Overview of LexEVS Stack
  • Scott noted that the Distributed LexEVS should be considered to be deprecated.
    • Serialization is the primary concern.
  • Tracy noted that the REST service is used more than the Java API.
  • Most NCI customers/users need simplified API.  
  • Users of Distributed API
    • Matching Program for Editors
    • caDSR
  • Lucene recommendations
    • Move all Lucene code into the DAO layer (this is not complete today)

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.  

...