NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Old Version 2

changes.mady.by.user Unknown User (endlecm)

Saved on

compared with

New Version Current

changes.mady.by.user Unknown User (endlecm)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

2017 December Face-to-Face Meeting Prioritization List

 

Future Priority

(1-high, 3-low

, 5 out of scope

)

Meeting

CategoryTopic
NotesMapping to be discussed further with the editors.Tuesday 9-11Mapping  LexEVS to look at utilizing the triplestore to speed up load (remove the need to load transitive table)
MeetingCommentsEpic
2DockerInvestigate the use of Docker to deploy data (Database container).Tuesday 9-11
Triple Store  LexEVS REST (CTS2) services should be revisited and reviewed for missing functionality and complexityTuesday 9-11API 
 

Jira
serverNCI Tracker
serverId7954a81f-12da-3366-a0ef-97c806660e7c
keyLEXEVS-3461

3

Docker
 

Investigate the use of Docker

to deploy data (Database container)

containers to support end users.

Tuesday 9-11
Docker
 

Jira

 

server

 

Investigate the use of Docker containers to end users

Tuesday 9-11Docker  

NCI Tracker
serverId7954a81f-12da-3366-a0ef-97c806660e7c
keyLEXEVS-3461

3508Consider 508 compliance going forward.Tuesday 9-11
508
  
Investigate the possibility of mapping for independent term to a source in meta; or another loaded terminology; or 2 sources in meta.Tuesday 11-12Mapping  
1Value setsFurther evaluate LexEVS
VS
Value Set resolution by implementing the text search.Wednesday 10-12
Value sets 
 

Jira
serverNCI Tracker
serverId7954a81f-12da-3366-a0ef-97c806660e7c
keyLEXEVS-3469

working groupMicro service
 
Investigate Node Graph (microservice or other, based on triple store).Wednesday 10-12
Micro service  

Further investigation of VS Hierarchy Display needed.

Wednesday 1-2Value sets  Cory to complete testing of containers using CentOS.Wednesday 2-3Docker 
 

Jira
serverNCI Tracker
serverId7954a81f-12da-3366-a0ef-97c806660e7c
keyLEXEVS-3458
Jira
serverNCI Tracker
serverId7954a81f-12da-3366-a0ef-97c806660e7c
keyLEXEVS-3459
Jira
serverNCI Tracker
serverId7954a81f-12da-3366-a0ef-97c806660e7c
keyLEXEVS-3460

2DockerLexEVS deployments using DockerWednesday 2-3 

Jira
serverNCI Tracker
serverId7954a81f-12da-3366-a0ef-97c806660e7c
keyLEXEVS-3461

working group

Graph
 

Investigate usage of MariaDB for JSON and graphing capabilities.

Wednesday 2-3
Graph
 

 

LexEVS team to send Migration link to caDSR team.Wednesday 3-4API  Determine gaps between LexEVS REST services and caDSR LexEVS API usage.

 

1
Wednesday 3-4
API
  
Provide assistance to caDSR team to parse results coming from CTS2.Wednesday 3-4
API  
 

Jira
serverNCI Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId7954a81f-12da-3366-a0ef-97c806660e7c
keyLEXEVS-3459

3APIMigrate CTS2 API from Heroku to NCI.Thursday 1-3
API
  
 
1
   
APIParticipate in unified API services working group.Thursday 9-11  
 
working group
   
EducationProvide EVS/LexEVS User Education - Focus on support and easy end useThursday 1-3 
 

Jira

 

server

 

NCI Tracker

                               

serverId7954a81f-12da-3366-a0ef-97c806660e7c
keyLEXEVS-3462

1MappingUpdate LexEVS mapping model and API to accommodate extended use casesTuesday 9-11 

Jira
serverNCI Tracker
serverId7954a81f-12da-3366-a0ef-97c806660e7c
keyLEXEVS-3457