|#||Assigned||Description||Date Identified||Due Date||Date Completed||Status|
|Area of Interest||Details|
Preston requested a new list of trackers for the 6.3 release, limiting to just the trackers that were used to make code changes.
Need a decision on where this functionality is going to go to start creating trackers and scope document.
|Term Browser||Believe we found how to fix the compatibility issue with the tree extension. Need to retain the 6.2 tree extension in its current location.|
|Meta Download Validation App|
|Term Suggestion Form|
|NCITERM-595||Handle coding schemes with multiple namespaces.|
Tested Version 6.3 LexEVSAPI new jars (with the merging of tree extension API into the main API.)
Assessed JSPs, backend beans and utility classes to identify codes required to be changed to pass the additional namespace parameter across the application.
|NCITERM-623||Link to Value Set Query from a Value Set Term.|
Identified a possible approach for linking an NCIt concept to a value set search results page that shows all value sets containing this particular concept.
|NCITERM-620||HGNC View Graph link no longer works.|
The user group has decided to remove the view graph link from the NGNC page because the difference in the format of concept code between NCI and NCBO.
|NCITERM-621||Link to the Value Set GUI from the Value Set Header Concept Page.|
Identified a possible approach to meet the feature request.
|Area of Interest||Details|
|Term Browser 2.6 Release||Continue review fixes and deployment.|
|Report Writer||Develop Project plan for 2.1 release.|
|Term Browser 2.7 Release||Scope development|
Risks, Issues, Dependencies
|#||Opened Date||Due Date||Description||Likelihood (H, M, L)||Impact||Assigned||Status||Mitigation Strategy|
|04/10/14||Deployments have been taking long periods of time. There is a lot of overhead getting through the iters||H||H||Speaking with members of the QA team to find ways to streamline the testing/deployment process||Finding ways to better integrate the development and QA team. Spoke to EVS Tools TPM requesting the correct communication channels.|
|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>|