NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Old Version 2

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

Saved on

compared with

New Version 3

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

Saved on

Key

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

...

NameRolePresent
Wright, Larry NIH/NCI   x
Fragoso, Gilberto NIH/NCI     x

De Coronado, Sherri    

NIH/NCI    x

Safran, Tracy

NIH/NCI [C] x
Ong, Kim L
IS x
Lucas, Jason R
IS x
Bauer, Scott  Mayo x
Stancl, Craig
Mayo x
Endle,  CoryMayo 
Sharma, DeepakMayo 
Wynne, Robert    NIH/NCI [C] x
Tran, Tin    NIH/NCI [C]  x
Carlsen, Brian NIH/NCI [C] 
Wong, Joanne NIH/NCI [C] 

Kuntipuram, Kumar

NIH/NCI [C] x

Action Items

AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
Rob

Close issue 

 

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

2016.02.092016.04.10 Open
Craig

Create JIRA issue to update CTS2 service to use Apache Commons Collections Version 3.2.1 (security issue)

2016.03.092016.03.30 Open

...

Sprint Status

Current Sprint -  Sprint 27 (March 31, 2016 – April 13, 2016)

LexEVS 6.4 Agile Development - Sprint Status

LexEVS Compatibility

  • 6.4 vs. 7.0
  • 6.3 and 6.4 indexes
  • remote service and client jar migration
  • API will remain the same.  
  • However, changes to the jars (client) will be required.
  • The requirement from NCI is that 6.3 users be able to use 6.4 content.
  • Data Loaded would be loaded to 6.4
    • 6.4 indexes would be created
    • For 6.3 indexes would need to be rebuilt.
  • NCI needs to plan on having both 6.4 and 6.3 indexes.
    • Additional storage will need to be obtained by NCI.
  • Additional NCI 6.3 regression testing will need to be done to ensure 6.3 data is still correct.
  • Analysis from Cory about migration to be discussed during the next week's meeting.
    • NCI will need to understand how extensive the changes are.
    • Based on the level of changes, thought needs to be given to releasing as 7.0 instead of 6.3
  • It was suggested that 6.4 be released all the way to PROD to allow others to use/test. The URL would not be openly shared.

Value Set Issues

  • Follow up/priorities

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

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

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

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

 

  • Resolution still required:
    • Jira
      serverNCI Tracker
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId7954a81f-12da-3366-a0ef-97c806660e7c
      keyLEXEVS-1731
  • Needs Investigation:
    • Jira
      serverNCI Tracker
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId7954a81f-12da-3366-a0ef-97c806660e7c
      keyLEXEVS-1729
  • Work Arounds exist for:
    • Jira
      serverNCI Tracker
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId7954a81f-12da-3366-a0ef-97c806660e7c
      keyLEXEVS-1730
    • Jira
      serverNCI Tracker
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId7954a81f-12da-3366-a0ef-97c806660e7c
      keyLEXEVS-1732

Feature request to get qualifiers on properties (Metathesaurus)

  • Priority
 
CI environment discussion 
LexEVS External Users 

...