De Coronado, Sherri
|Ong, Kim L ||IS||x|
|Lucas, Jason R ||IS||x|
|Wynne, Robert||NIH/NCI [C]||x|
|Tran, Tin||NIH/NCI [C]||x|
|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|
Current Sprint - Sprint 28 (April 14, 2016 – April 27, 2016)
caCore legacy code was mentioned and it was suggested that we should remove any caCore code.
Mayo will need to prioritize this work to determine where it will fit into our schedule.
TODO: Craig to create a JIRA item to track the removal of the caCore code.
PTE for CI and DEV environment discussion
CI server - it was discussed that we may use an in-memory DB (HSQL) instead of MySQL DB. This is being investigated by Mayo to see if we can get this working locally.
Scott noted that our Mayo Jenkins server is running on a system that has 8 cores with 32 GB of memory.
DEV server - Rob has installed LexEVS 6.4 runtime on DEV and generated the indexes.
There is a new 6.4 DEV container that Jacob is working on getting deployed.
NCI testing - NCI will build the 2.8 browser with the new LexEVS 6.4 jars and see if that runs without any code changes.
NCI will also test the runtime API and Tin will look at performance to compare 6.3 and 6.4.
Jason asked when the remote API will be available. We suggested that it should be delivered by the end of sprint 29. We will need to verify performance is still acceptable prior to releasing it to NCI.
|CTS2 and jQuery Example Follow up||Kim was running into a cross site scripting issue. Scott suggested using a JSONP call to resolve this issue.|
|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|