|#||Assigned||Description||Date Identified||Due Date||Date Completed||Status|
|Area of Interest||Details|
|LexEVS||We are currently setting up the development environment with 6.4 remote API. So far everything works except for one mapping bug has reappeared.|
The devdata appscan test with the subset of data started on 5/13/2016 2:53:39 and ended sometime on Monday. The took 2 days and 11 hours so I don’t see the data size factoring in that much.
|Term Suggestion Application|
|Triple Store Prototype||Continuing work on the new Report Writer using triplestore. The development team is meeting with the operations team on Monday to get details on implementation.|
Generate reports without the UI.
Modified the code to allow the administrator to generate reports based on the NCIt version as specified in the ncireportwriter.properties configuration file.
Per additional request from the Operations team, modified the StandaloneReportGenerator to accept either a folder name containing all template files or a single template file name as a command line parameter and generate new reports accordingly.
Started to review the OWL2 formatted NCI Thesaurus.
|NCITERM-731||Concepts selected from a Value Sets' Released File: View Graph not viewable due to ns=null in the URL|
|NCITERM-710||Migrate to LexEVS 6.4.|
Installed the latest v6.4 release, LexEVS-install-SNAPSHOT.LUCENE.SPRINT29.2016.05.12, on a local development environment.
Reviewed the external dependency jar files contained in the new release, extLib-SNAPSHOT.LUCENE.SPRINT29.2016.05.12, to determine if any jar used by the browser needs to be updated.
Installed the war file, lexevsapi64-SNAPSHOT.LUCENE.SPRINT29.2016.05.12.waron on a local Tomcat engine.
Started to test the new v6.4 release.
|Area of Interest||Details|
|Term Browser 2.9 Release||Start development of the 2.9 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>|