Page History
...
- Overall Impessions and themes
- Mapping
- Extract mapping from Meta efficiently
- This would save effort of creating cusom maps.
- Extract mapping from Meta efficiently
- 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.
- 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
- Discuss with stakeholders to gather requirements
- Determine how to move forward based on the requirements (best practice)
- Separate APIs
- Combined APIs
- 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
- Mapping
Decision Points:
- Action Items:
...