De Coronado, Sherri
|Ong, Kim L ||IS||x|
|Lucas, Jason R ||IS||x|
|Wynne, Robert||NIH/NCI [C]||x|
|Tran, Tin||NIH/NCI [C]|
|Carlsen, Brian||NIH/NCI [C]|
|Wong, Joanne||NIH/NCI [C]|
|Assigned||Description||Date Identified||Due Date||Date Completed||Status|
LEXEVS-1516 - Getting issue details... STATUS
Create JIRA issue to update CTS2 service to use Apache Commons Collections Version 3.2.1 (security issue)
|Craig||Create JIRA issue to remove caCore legacy code||2016.04.20||2016.04.30||Open|
|Cory||Update wiki to describe what DBs are supported/tested going forward||2016.04.27||2016.04.30||Open|
Current Sprint - Sprint 30 (May 12, 2016 – May 25, 2016)
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:
Larry agreed that there are some loader issues that need to be worked on for the 6.4 release.
We all agreed to move the backlog issues (not including the loader issues) in 6.4 into 6.5.
|6.4 wrap up||This has been discussed above.|
|6.5/loader issues/tree extension issues|
|Discuss LEXEVS-957 - Getting issue details... STATUS|
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
NCI DEV deployment updates
CTS2 6.3 is installed on DEV. This hasn't been tested on DEV yet.
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
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
Recent LexEVS Related Bugs and Features (within last week)
|Key||Summary||T||Created||Reporter||P||Status||Affected Version/s||Fix Version/s|
Recent CTS2 Service Related Issues (within last week)
6.4 LexEVS Related Issues
6.4 CTS2 Service Related Issues
Project Plan Changes
|Area of Interest||Details|
Risks, Issues, Dependencies
|#||Opened Date||Due Date||Description||Likelihood (H, M, L)||Impact||Assigned||Status||Mitigation Strategy|
Action Item Backlog
|#||Assigned||Description||Date Identified||Due Date||Date Completed||Status|
|64||Scott||To follow up on URI's on OWL2 with Harold.||on hold|
|164||Cory||Cory to add implementation to CTS2 implementations page.||2014.04.30||on hold|
|197||Scott||Do a gap analysis on what the URI_Resolver logs and what NCI would like to know from these logs||2014.6.18||on hold|
|200||Larry/Sherry||Query current LexEVS users about use of SOAP, REST or QBE services in the legacy caCORE api's||2014.6.18||on hold|
|207||Cory||Write issue against CTS2 OMG regarding the ability to return INACTIVE concepts only.||2014.07.30||on hold|
|210||Larry/Gilberto||Determine if there is a need to meet with the CTRP||2014.07.30||on hold|
|212||Larry||Include LexGrid XML Export as part of the 5.1 retirement notice.||2014.07.30|
|224||Scott||URI Resolver - Provide overview of how to access the URI Resolver||2014.09.03|
|225||Scott||URI Resolver - Look at TLAMP and VSAC service to determine usage of URI Resolver||2014.09.03||on hold|
|244||Craig||Plan meeting with Tracy to discuss collaborative LexEVS development process||2014.12.03||on hold|
|281||Scott||Try to replicate what CTRP did to break our service (retrieve a tree through CTS2).||2015.03.25||on hold|
|282||Mayo Team||Look into implementing graph node in CTS2 for the path to root method (and path to leaf).||2015.03.25||on hold|