|#||Assigned||Description||Date Identified||Due Date||Date Completed||Status|
|Area of Interest||Details|
Working on a schedule for participation of the browser testing of the 6.4 LexEVS API. Mayo said that they will need three more weeks of development before a browser ready API will be deployed to DEV.
Provided support to the Operations team on the issue that the new ComplexMapsTo property failed to load by the OWL2 loader.
We are currently having issues getting the Term Browser working now that LexEVS 6.4 is installed on DEV. We have an update to the graph implementation but we cannot verify until 6.4 is ready or we point to 6.3 on another tier. I put in a ticket for an AHP track for 2.8 that point to the dataQA API.
We are also looking at the possibility of moving the browsers to the remote API. The QA team is running browser performance test using both the remote and local API to see if remote API performance is still in an issue with the browser. There is also a mapping extension issue with the remote API that will need to be considered before switching over.
We are looking at the possibility of cutting the Term Brower 2.8 release development short to release an important bug fix where relationship are failing to display on certain concepts when going through the View in Hierarchy.
|Term Suggestion Application|
|Triple Store Prototype||We now have the sparql endpoint and hierarchy tree working on the new VM. We still have a little work to get the browser search working but that should be fixed this week.|
Improve display of large graphs.
Enhanced the graph reduction algorithm to support grouping of both inbound and outbound relationships to and from the focus node. (Test case: NCI Thesaurus, Heart (Code C12727)).
Fixed a bug that View Graph page fails to render when a node label contains a single quite character (Test case, NCI Thesaurus, Mouse Kaposi's Sarcoma (Code C24019)).
|Migrate to LexEVS 6.4.|
LexEVS API 6.4 will not be backward compatible.
Requested new client jars from the Mayo team.
|Area of Interest||Details|
|Term Browser 2.8 Release||Continue development of the 2.8 Term Browser release.|
Risks, Issues, Dependencies
|#||Opened Date||Due Date||Description||Likelihood (H, M, L)||Impact||Assigned||Status||Mitigation Strategy|
|09/10/2015||H||H||AppScan are taking long periods of time to complete. For Term browser, the minimum has been 5 days.||We are working on both the code base and configuration of the scan to try to improve performance. We are also looking at open source code scanners that could possibly be used ahead of the AppScan to at least limit the number appscans required.|
|7/17/2014||Deployment of software, even small upgrades, have been a lengthy process.||This especially affects smaller releases in which there are security or bug fixes.||The Agile practices migration have been put on hold for now.|
|09/10/2014||Getting the environment in place for the Mayo trip to NCI.||Need to get each of the environment (DEV,QA,Stage) in place before the Mayo trip on September 22nd. We are currently one week behind. The impact is that the Mayo developer will be onsite to work on the deployments and the tiers will not be in place.||Currently we only have the DEV environment setup for the LexEVS API>|