 |
Page History
...
Future Priority (1-high, 3-low, 5 out of scope) | Meeting | Category | Topic | Notes | ||||
|---|---|---|---|---|---|---|---|---|
| Investigate the use of Docker to deploy data (Database container). | Tuesday 9-11 | Docker | ||||||
Investigate the use of Docker containers to support end users. | Tuesday 9-11 | Docker | ||||||
| Consider 508 compliance going forward. | Tuesday 9-11 | 508 | ||||||
| Further evaluate LexEVS VS Value Set resolution by implementing the text search. | Wednesday 10-12 | Value sets | ||||||
| Investigate Node Graph (microservice or other, based on triple store). | Wednesday 10-12 | Micro service | Further investigation of VS Hierarchy Display needed. | |||||
| Wednesday 1-2 | Value sets | LexEVS Deployments LexEVS deployments using Docker | Wednesday 2-3 | Docker | ||||
Investigate usage of MariaDB for JSON and graphing capabilities. | Wednesday 2-3 | Graph | ||||||
| LexEVS team to send Migration link to caDSR team. | Wednesday 3-4 | API | ||||||
| Determine gaps between LexEVS REST services and caDSR LexEVS API usage. | Wednesday 3-4 | API | ||||||
| Provide assistance to caDSR team to parse results coming from CTS2. | Wednesday 3-4 | API | ||||||
| Migrate CTS2 API from Heroku to NCI. | Thursday 1-3 | API | ||||||
| Extend the model of mappings (is it supported in CTS2) to support different types of maps. | Mapping | |||||||
| Participate in unified API services working group. | API | |||||||
| Provide EVS/LexEVS User Education - Focus on support and easy end use | Education | |||||||
| Update LexEVS mapping model and API to accommodate extended use cases | Mapping | |||||||
...
