NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Old Version 1

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.

 Attendees

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

De Coronado, Sherri    

NIH/NCI    x

Safran, Tracy

NIH/NCI [C] 
Ong, Kim L
IS x
Lucas, Jason R
IS x
Bauer, Scott  Mayo x
Stancl, Craig
Mayo x
Endle,  CoryMayo x
Sharma, DeepakMayo 
Wynne, Robert    NIH/NCI [C] x
Tran, Tin    NIH/NCI [C]  
Barry 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
CraigCreate JIRA issue to remove caCore legacy code2016.04.202016.04.30 Open
CoryUpdate wiki to describe what DBs are supported/tested going forward2016.04.272016.04.30 OpenCoryInvestigate invisible indexes being created.2016.05.102016.05.17 Done

Progress

  
Scott
  • Sprint 30
  • Sprint 31 PlaningPlanning
  • On going Support
Cory
  • Sprint 30
  • Sprint 31 PlaningPlanning
  • On going Support
Deepak
  • Sprint 30
  • Sprint 31 PlaningPlanning
Craig
  • Sprint 30
  • Sprint 31 PlaningPlanning
  • Agile Admin

Agenda

Sprint Status

 

Current Sprint -  Sprint 30 (May 12, 2016 – May 25, 2016)

LexEVS 6.4 S13-500 Agile Development - Sprint Status

NCI has deployed LexEVS core API and LexEVS Remote API.

Tracy mentioned that she will test from her client.

Kim has been testing with the remote API. He is running into the issue related to LEXEVS-957. The Mayo team will discuss possible solutions to this issue.

Discuss Issues

  • LEXEVS-1729
  • LEXEVS-1730
  • LEXEVS-1731
  • LEXEVS-1732

Status#SprintStatus-Sprint30

Mayo team deployed sprint 29 artifacts and determined stories for sprint 31.

We are looking at moving to the next phase for documentation and tier deployment. We have planned 60 days for tier deployment.

We need to discuss the following next steps:

  • Loader and tree extension
We discussed the priority of these
  • JIRA items and if they need to be
in the LexEVS
  • implemented for 6.4
release
  • .

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

  • Investigate if this is a bug that we can reproduce. If this is a bug, then we need to fix for 6.4

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

  • There is a workaround. This issue can be completed after LexEVS release 6.4.

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

Feature request for 6.4.
  • Determine when to working on 6.5 work.
  • Many issues have been de-prioritized to 6.5

Larry agreed that there are some loader issues that need to be worked on for the 6.4 release.

  • We will need to go through the existing loader issues to determine which ones need to be completed in 6.4.

We all agreed to move the backlog issues (not including the loader issues) in 6.4 into 6.5.

6.4 wrap upThis has been discussed above.
6.5/loader issues/tree extension issues 
Discuss
Jira
serverNCI Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId7954a81f-12da-3366-a0ef-97c806660e7c
keyLEXEVS-
1732
957

LEXEVS-957 - Mapping iterators do not work on distributed.

This issue was closed and two new issues were created to better describe the issues (LEXEVS-960, LEXEVS-961)

Larry agreed that LEXEVS-960 and LEXEVS-961 should be looked at in 6.5

There is a workaround. This issue can be completed after LexEVS release 6.4.

NCI DEV deployment updatesLexEVS core API 6

  • CTS2 1.4
and LexEVS Remote API 6.4 war files are deployed. Tracy and Kim have been testing.
  • .1 (6.3) snapshot deployment progress
  • CTS2 1.5.0 (6.4) snapshot deployment

CTS2 6.3 - NCI will deploy to existing is installed on DEV. This hasn't been tested on DEV yet.

  • Cory will create a FINAL tag on CTS2 6.3
container. NCI will let us know when this is done and Mayo and NCI will test the API on DEV.
  • Cory to send a link to Tin for our online API.
  • Cory to send JIRA item that was fixed to Tin.
    • Jira
      serverNCI Tracker
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId7954a81f-12da-3366-a0ef-97c806660e7c
      keyLEXEVS-1768
  • Larry would like to move CTS2 6.3 up the tiers to PROD as soon as possible.

CTS2 6.4 - will deploy to a new container that is currently empty.

PIV card updates

No updates.

Kumar asked if Deepak filled out the form: VPN remote access user agreement. Cory will follow up with Deepak.

LexEVS External Users

  • Updates

Gilberto mentioned that there was an app support question from a user at Georgetown University.

Gilberto pointed him to the LexEVS wiki about the LexEVS API and CTS2 API.

  • (1.4.1) and place the artifact on the NCI SFTP site.
  • Cory will also need to update the PTE to use the correct artifact naming.

CTS2 6.4 is deployed on DEV, but has not be configured yet. Mayo will work with Tracy next week to configure sprint 30 artifacts and test.

6.4 DEV Testing updates

  • Lexevs API
  • Lexevs Remote API

Mayo has some lexevs remote API fixes that will be in the artifacts we create from sprint 30.

Kim will be able to test these fixes next week.

6.4 Deployment strategy

Mayo team will finalize our naming strategy for git branches and artifact naming and review with NCI team next week
URI Resolver - No External instance

Mayo's server doesn't have a public URI resolver anymore.

The lexevs CTS2 service requires to connect to a URI resolver in order perform the unit/integration tests. This forces the developers to have a local URI resolver to connect to in order to build.

We were asking if NCI has any interest in hosting a public URI resolver instance.

Larry was asking if there has been an appscan on their URI resolver. We don't recall specifically if there was one and agreed it would be good to have one done on their current instance.

 

LexEVS External Users

  • Updates
No updatesInvisible Indexes

These seem to happen when indexes are deleted and the container is still running and holds a reference to them.

One possible workaround is to shutdown the container are restart it. NCI team will continue to look into this.

JIRA Issues

Recent LexEVS Related Bugs and Features (within last week)

Jira
serverNCI Tracker
columnskey,summary,type,created,reporter,priority,status,versions,fixversions
maximumIssues20
jqlQueryproject = LEXEVS AND (TYPE = bug or TYPE = "new feature" or TYPE ="Improvement" or TYPE ="Inquiry") AND created >=2016-05-18 AND created <= 2016-05-25
serverId7954a81f-12da-3366-a0ef-97c806660e7c

Recent CTS2 Service Related Issues (within last week)

Jira
serverNCI Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = LEXEVSCTS2 AND created >=2016-05-18 AND created <= 2016-05-25
serverId7954a81f-12da-3366-a0ef-97c806660e7c

6.4 LexEVS Related Issues

Jira
serverNCI Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject in (LEXEVS) AND fixVersion = 6.4 ORDER BY priority DESC
serverId7954a81f-12da-3366-a0ef-97c806660e7c

6.4 CTS2 Service Related Issues

Jira
serverNCI Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = LEXEVSCTS2 AND fixVersion = "CTS2 Service 2.1" OR fixVersion = "VS Client 1.1"
serverId7954a81f-12da-3366-a0ef-97c806660e7c

Project Plan Changes

#DescriptionDue DateResourcesNotesRisksMitigation
 None     
       
       

 Planned Activities

Area of InterestDetails
  
  
  

Risks, Issues, Dependencies

Risks

# Opened DateDue DateDescriptionLikelihood (H, M, L)ImpactAssignedStatusMitigation Strategy
         
         

Issues

 #Opened DateDescriptionImpactAssignedStatus
      
      
      

Dependencies

Opened DateDescriptionAssigned
   
   

 

Action Item Backlog

 #AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
64ScottTo follow up on URI's on OWL2 with Harold.   on hold
164CoryCory to add implementation to CTS2 implementations page.2014.04.30  on hold
197ScottDo a gap analysis on what the URI_Resolver logs and what NCI would like to know from these logs2014.6.18  on hold
200Larry/SherryQuery current LexEVS users about use of SOAP, REST or QBE services in the legacy caCORE api's2014.6.18  on hold
207CoryWrite issue against CTS2 OMG regarding the ability to return INACTIVE concepts only.2014.07.30  on hold
210Larry/GilbertoDetermine if there is a need to meet with the CTRP2014.07.30  on hold
212LarryInclude LexGrid XML Export as part of the 5.1 retirement notice. 2014.07.30  

on hold

224ScottURI Resolver - Provide overview of how to access the URI Resolver2014.09.03  

on hold

225ScottURI Resolver - Look at TLAMP and VSAC service to determine usage of URI Resolver2014.09.03  on hold
244CraigPlan meeting with Tracy to discuss collaborative LexEVS development process2014.12.03  on hold
281ScottTry to replicate what CTRP did to break our service (retrieve a tree through CTS2).2015.03.25  on hold
282Mayo TeamLook into implementing graph node in CTS2 for the path to root method (and path to leaf).2015.03.25  on hold

 

...