Page History

...

• Overall Impessions and themes
  • Mappings
    • Extract mapping from Meta efficiently
      • This would save effort of creating custom maps.
    • Extend the model of mappings (is it supported in CTS2) to support different types of maps.
      • ie ICD-O3, Meta and the logic (OR, AND..)
  • Diversity of paths through the architecture
    • Addition of triple store
    • Multiple APIs to address user communities.
    • flow described - input of data through the tooling and delivery
    • 2 views for documentation were identified:
      • Focus on what users needed
      • Focus on overall architecture (technical)
  • Remote API Roadmap
    • Determine the replacement for what of the API is needed. (based on gap analysis)
    • Determine current users and identify what is required for those users.  
  • REST API 
    
    • Federation using SPARQL or other tooling
    • Big Data will require that performance be addressed (caching, etc.)
      • Will support the annotation pipelines
    • LexEVS will need to provide REST services for content not available in TripleStore
    • Provide documentation to better help users
  • Report Writer
    • Support for other terminologies. LexEVS REST services/EVS REST Services
  • SWAGGER documentation
    • Differentiate from the general API and CTRP specific API
  • Microservices
    • integration of triple store to support/enhance LexEVS functionality
    • Hierarchy/Transitive Table support.
  • User needs to create a unified service
    • Discuss with stakeholders to gather requirements
    • Determine how to move forward based on the requirements (best practice)
      • Separate APIs
      • Combined APIs
    • Ensure the service simpilfies what the user needs to know about the technical implementation.
    • This could be several months of effort (across teams)
  • User Education - Enable users to use the services
    
    • Provide better documentation for end users.
    • Provide mapping of source into LexEVS or REST models so users can understand how to query the service in LexEVS
    • Review and update Wiki Organization
    • Provide documentation to aid in building applications that will utilize the services (REST, Java API, TripleStore/SPARQL/ftp)
    • Architecture diagrams to describe the 1) flow of data and 2) technical specifics.
    • Provide timeline for enhancement (REST Services), dates for deprecation, system deployments
    • LexEVS REST Code Migration Guide
  • Build and Deploy (Docker)
    • Continued development of Docker containers with the systems team.
    • Use of Node.js to be discussed with systems team.
    • Investigate use of Docker for data deployments. 

Decision Points:

• Action Items:

...