Date
Attendees
Kim Ong
- Jason Lucas
- Corey Endle
- Scott Bauer
Goals
Discussion items
Time | Item | Who | Notes |
---|---|---|---|
Mapping Meeting |
| ||
Java 11 |
| ||
CTS | Lyuba has pulled back on idea of writing their data layer. They are still using 6.4. | ||
Cloud as RMI solution | Kim uses the RMI to help development. Is a cloud server an option to allow us to retire RMI? Can cloud server be mounted as a local drive? Is CentOS capable of being mounted as local drive as an alternative? | ||
Cloud in general | NCI cloud group not being very responsive - which creates risk. Still need answers on control and cost. | ||
Triplestore | Last discussion we chatted structure and said it might need a database to store hierarchies of indexes. Any more thoughts? Could this be stored itself in TS or does it need relational? For very specific use case of resolving large hierarchies - graph databases are best. Some other types of queries are very fast - Kevin has been working with Arango and OSQL. Calls itself a "multi-model" database. | ||
Use cases - needed to develop concrete architecture | Text search Hierarchy resolution Hierarchy navigation Mapping Value Sets Reporting and exporting Coding scheme metadata Filtering return values - entity resolution Metathesaurus and how to host | ||
Future of LexEVS | The structure likely will be left behind. Still valid portions can be broken out as microservices, or inform new services Data model is sound and useful as a terminology service Metathesaurus to RDF or still supported in LexEVS? Consult with UMLS developers. Us UMLS backend and their API? |
Action items
- Tracy to look for Steve's mapping requirements
- Tracy - continue to pursue tech stack
- All - focus on Mapping requirements for next week