|#||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 Operation team regarding a potential OWL2 loader issue (data file: obi_2015-12-07.owl).
Provided support to the Operation team on extracting source data for all available value set definitions using LexEVSAPI.
It was decided that we are going to proceed with an interim 2.8 release to deploy important bug fixes. This release will continue to use the local 6.3 LexEVS API.
We received performance metrics from the QA team showing the response time for the Term Browser using both the local and remote API. In general, the response time from the remote API is 20% slower than the local API. However, in most circumstances this only equates to a few milliseconds.
We completed an AppScan on DEV which passed with no high or medium vulnerabilities. It also ran in under two days which is a significant improvement over previous releases.
|Term Suggestion Application|
|Triple Store Prototype||We now have the sparql endpoint and hierarchy tree working on the new VM. The search is now working but not fully functional.|
Some View Graph pages fail to render.
|Improve display of large graphs.|
Successfully tested the new graph reduction algorithm implemented.
|NCITERM-710||Migrate to LexEVS 6.4.|
Received LexEVS-6.4.0 installation package from Mayo.
Installed LexEVS-6.4.0 on a local development environment.
Performed initial comparison of jar files with those contained in the LexEVS6.3.0.RC1 distribution.
|NCITERM-712||Some relationship pages fail to render.||Fixed|
|NCITERM-703||OWL2 Qualifiers Display.|
Received an input from the user group that the property qualifier should be placed under property value instead of property name.
|NCITERM-701||UI test utility fails to detect broken OBO formatted ontology View-In-Hierarchy.|
|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>|