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|
|Craig/Larry||Follow up with Jose (CTRP) in January 2016 to see if we can assist them and understand their requirements.||2015.12.16||2016.01.31||2016.02.10||Closed|
|Tracy||Follow up with caDSR team to see if they still have lucene questions.||2016.01.13||2016.01.31||2016.02.10||Closed|
LEXEVS-1516 - Getting issue details... STATUS
Current Sprint - Sprint 23 ( February 04, 2016 – February 17, 2016 )
Craig reviewed what is needed to exit phase 4 (core Lucene development) and what will need to be worked on in phase 5.
Craig also reviewed the roadmap. We added one more sprint to phase 4 to finish up all of the issues. Also, deployment and documentation will happen concurrently.
We haven't heard back from Toky yet.
TODO: Craig to get the latest status from Toky on the scheduled testing.
6.4 Install on Dev
Kim noted that testing from his term browser to DATA_QA (remote API) doesn't work. But it does work on PROD (remote API).
NCI is considering moving from the local LexEVS to the LexEVS remote API. They need to first evaluate performance between the local and remote API
Tin mentioned that he will do some performance testing will be done by next Monday.
188.8.131.52 RC Testing with Term Browser
Kim found an issue in view in hierarchy. Kim created a JIRA issue for this.
LEXEVS-1627 - Getting issue details... STATUS
This is a different issue than the namespace issue that was fixed for 184.108.40.206 RC1.
Scott will look into how to create complex properties for Tracy.
Based on our testing, we found that the Site-to-Site VPN was a bit slower than the software VPN.
Additionally, the software VPN is more versatile in it's usage (don't need to be hardwired, can connect to multiple DEV servers at NCI).
|LexEVS External Users||No updates.|
How to make this more DevOPs like to streamline testing:
TODO: Create a deployment wiki page to keep a running list of tasks we want to do for deploying 6.4.
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|