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]||x|
|Wong, Joanne||NIH/NCI [C]|
|Sarah Elkins||NIH/NCI [C]||x|
|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)
Current Sprint - Sprint 27 (March 31, 2016 – April 13, 2016)
We discussed Sprint 28 work that is planned.
Larry was asking when we can deliver the first release candidate for NCI DEV.
They would only need the LexEVS core API initially (no remote service).
Priority for sprint 28 will be to get LexEVS API deployed to NCI DEV. CTS2 changes have a lower priority.
|Cory will add notes to the wiki that describes the changes.|
Feature request to get qualifiers on properties (Metathesaurus)
LEXEVSCTS2-35 - Getting issue details... STATUS
CTS2 needed to be upgraded (Lucene dependencies) for 6.4. We will need CTS2 services for both LexEVS 6.4 and LexEVS 6.3.
CTS2 service for LexEVS 6.4 can be used by end users instead of the CTS2 service for LexEVS 6.3. There are no API changes. However, there are dependency changes for the CTS2 services. This results in the CTS2 service being dependent on 6.4 and will not be able to talk to LexEVS 6.3.
Larry suggested getting the CTS2 service for LexEVS 6.3 up the tiers prior to CTS2 service for 6.4.
It was decided that the CTS2 service for 6.3 will be deployed up to PROD independent of the CTS2 service for 6.4.
The CTS2 service for 6.4 will be deployed with LexEVS 6.4.
PTE for CI and DEV environment discussion
PTE for CI server request questions
Jacob will need to make a VM request for our Jenkins instance.
PTE for LexEVS
|LexEVS External Users||Nothing to note.|
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|