Page History

Discussion Points: 

EVS API Services

• Determine a level of governance and architecture for EVS related services.
• Work with the caDSR team to transition from remote API to REST Services. (TBD?)
• Propose ability to capture usage statistics for analytics of what types of queries are being run, content searched, etc.
• Determine a REST service for Metathesaurus and determine best how to support the end users.
• Continued transition of stand alone coding systems to EVS REST API.
• Transition of LexEVS search knowledge to the EVS API development team
  • utilize the services spreadsheet
• Provide LexEVS resources to help with EVS API.
• Investigate infrastructure considerations (cloud environments?).
• Single Service coverage (provide single search mechanism)
  • REST Service for Meta
  • EVS REST API
  • LexEVS API

Model Changes (OWL)

• Complex Classes need to be addressed somehow - LexEVS or not.
• Micro services should be considered for providing services to provide OWL content (micro service using the triple store)

Admin UI

• Continue to use the GUI as it is
• Consider to look at the dashboard viewer (query)

Decision Points: