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