De Coronado, Sherri
|Ong, Kim L ||IS||x|
|Lucas, Jason R ||IS||x|
|Tran, Tin||NIH/NCI [C]||x|
|Carlsen, Brian||(NIH/NCI) [C]||x|
|#||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|
|283||Scott||Set up meeting with Mayo team and Jacob to discuss CTS2 API Service Documentation PTE regarding start up scripts for the services.||2015.05.13||done|
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||open|
|286||Rob||Attempt to load OB with OWL2 loader and review the results||2015.05.20||open|
|287||Mayo Team||Mayo team to verify the latest 6.3 code is tagged properly and updated the PTE.||2015.05.20||open|
Current Sprint - Sprint 5 (May 13, 2015 - June 2, 2015)
Remote API 6.2 and 6.3 support
Iterator (remote) - was broken in 6.3 (and in previous versions) and a partial fix was put in during the 6.3 development.
The local iterator works, but the remote iterator fails. Any fix may break backwards compatibility.
A fix may require a Spring fix (a new constructor).
Who are the clients (ones that use the remote client)? NCI as well as others that download and use it our open source release/code.
Further investigation needs to be done to determine the impact/compatibility with existing and previous versions.
Larry suggested that we note that this feature was broke in all previous versions of 6. If you want this feature, then you need to get the latest version with the fix in it.
TODO - Document across all 6.x versions that this feature doesn't work (unless you use the local API)
TODO - Note that this may be fixed in a future release.
Mapping Extension Discussion
LEXEVS-942 - Getting issue details... STATUS
PDQ to NCIT map is the original. Other maps are causing loading timeouts (like SMOMED mappings).
Scott recalls that the loader only loads a single map.
TODO - Review how this is implemented and see if there is a short term fix to increase the performance. (hold until next sprint)
CTS2 API Documentation
LEXEVSCTS2-32 - Getting issue details... STATUS
Code system updates are twice a month.
For code system versions - use latest MedRA (17.1)
For mapping - MA to NCIT (last updated in 2012)
Tracy/Rob will verify once the changes are implemented.
LEXEVS-946 - Getting issue details... STATUS
In 6.2 we are not handling namespaces correctly
If Rob loads OBI w/o a preference file, he sees different results.
How do we declare root nodes in the preference files with multiple namespaces?
TODO: Rob will try loading with OWL2 loader and let us know the results.
|LEXEVS-942 - Getting issue details... STATUS|
Critical Partners Meeting
|Larry to send out details of the meeting when they become available.|
Scott to review what Preston has tested.
After this, we should be ready to move the QA.
TODO: Mayo team to verify the latest code is tagged properly and update the PTE.
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|