De Coronado, Sherri
|Ong, Kim L ||IS||x|
|Lucas, Jason R ||IS||x|
|Tran, Tin||NIH/NCI [C]|
|Carlsen, Brian||(NIH/NCI) [C]|
|#||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|
Document across all 6.x versions that LEXEVS-623 doesn't work (unless you use the local API).
Note that this may be fixed in future releases.
|285||Scott||Create JIRA task to review how mapping is implemented and see if there is a short term fix to increase the performance for multiple maps.||2015.05.20||done|
|286||Rob||Attempt to load OBI with OWL2 loader and review the results||2015.05.20||done|
|288||Larry||Prioritize the MRMAP loader issues.||2015.05.27||2015.06.05||done|
|289||Scott||Look into OBI issues||2015.06.03||2015.06.05||done|
|290||Scott||Discuss with Craig extra effort to create next gen indexes against actual LexEVS loaded content||2015.06.03||2015.06.05||done|
|291||Rob||Look into getting information allowing creating a subset of MRMAP for larger subsets involving SNOMED||2015.06.03||2015.06.10||done|
|292||Scott||Re-evaluate 5.1 Lucene use depending on possible update of Luke||2015.06.03||2015.06.05||done|
|293||Jason||Check into Mayo being designated a trusted site||2015.06.03||open|
Current Sprint - Sprint 6 (June 3, 2015 - June 24, 2015)LexEVS S13-500 Agile Development - Sprint Status#SprintStatus-Sprint6
The following issues are the highest priority and, if possible, be put in the current or next sprint.
|Need to make a decision on what version of Lucene to use after Scott does some additional research.|
LEXEVS-942 - Getting issue details... STATUS J
JIRA item is updated with the results. DB timeout was increased from 8 to 24 hours and it still timed out.
Note from Larry that they are going from QA to Stage.
It may be on production in the next week or two.
Lucene Version Update - 5.1
Lucene release 5.2 has been released. We agreed that we will evaluate 5.2 to see if it works for the prototype.
We also will need to determine if Luke will work with 5.2.
At some point, we need to select a version and go with it.
Mayo as trusted site also VPN
Gilberto is waiting for some verification on what we can do
Remote apps will not allow you to run GUIs.
Terminology Updates on Dev and QA
Other interested parties agreed that QA should be updated with the latest terminology.
The open question is what should should be on DEV (i.e. current production data) and others?
Gilberto suggest the following:
Larry suggested we can add different Databases to DEV, if needed.
Tracy/Rob to lead this effort and work with systems.
We agreed that we should set up a virtual meeting/demo.
Larry will look into setting up a meeting with them to discuss/demo.
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|