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]||x|
|Wong, Joanne||NIH/NCI [C]|
|Assigned||Description||Date Identified||Due Date||Date Completed||Status|
LEXEVS-1516 - Getting issue details... STATUS
|Brian||For the RRF issue, come up with some examples to send out to the group to explore.||2016.03.02||2016.03.09||open|
|Scott||For the RRF issue, send out his list of ten offenders that show this issue.||2016.03.02||2016.03.09||open|
Current Sprint - Sprint 24 ( February 18, 2016 – April 02, 2016 )
We have finished up phase 4 - lucene development (100% junits passing)
Sprint 25 (March 03, 2016 – March 16, 2016)
Focus on performance.
Verify Remote API, CTS2, Browser, GUI.
Loader related issues:
After reviewing the existing OWL2 issues, Scott suggested that NCI reload the OWL2 files using the preference file and then re-test.
Lucene 6.4 performance
Scott gave an overview of 6.4 Lucene performance and how it compares to 6.3. After implementing the Lucene hit collector and providing a cache, the performance appears acceptable.
There is still some tuning that needs to done to increase the performance.
Comparing performance from 6.4 to 6.3, some areas are better and some are a bit slower.
Larry was suggesting that we used the hit collector (that retrieved all of the results up front) to ensure we got the best results. Larry was wondering if we still need to retrieve all of the results up front.
Scott mentioned that collecting all of the results up front takes a large amount of time.
Larry suggested that we investigate the possibility of only returning an initial amount of results (for example 1000).
Scott reviewed the results spreadsheet.
Scott noted that the tree extension calls take longer.
Larry mentioned that that NCI would like to test it out and see how it performs.
OBI/OWL2 Load Issues
This was discussed during the prior meeting.
NCI acknowledged that they need to reload OWL2 with the preference file.
Gilberto will recheck his list of issues against this new load.
OBO Hierarchy Load Issues
|No updates this weeks.|
VPN and GFE
Girlberto stated the request when up the ladder for approval.
Our RSA software token is tied to the user, not the machine.
Scott was wondering or the SMQs, can these be summarized in LexEVS?
Brian suggested that what the loader is doing is fine.
He also suggested that in the browser, qualifiers - don't show on the browser.
Brian will come up with some examples to send out to the group to explore.
Scott will also send out his list of ten offenders that show this issue.
|LexEVS External Users|
lexgrid.org xsd references
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|