|#||Assigned||Description||Date Identified||Due Date||Date Completed||Status|
|Mayo/Jason||We have run into multiple issues where the performance on the DEV tier has be a problem due to Mayo not being able to replicate the slow points due to the drastic difference in DEV resources. We discuss this with the systems team and they requested us to put in a DRT ticket that provides the specs to match the Mayo DEV server.||08/30/13||7/16/2014||A new development server has been procured and is currently being setup. This AI will be closed.|
|Area of Interest||Details|
Had class loading issues with the redeployment of the CTS2 Services. Made a copy of the corrected configuration and made configuration properties file that can be used for future deployments. This is noted in the PTE now.
We have been noticing some strange behavior with the last version of LexEVS. This has mostly been found through testing of the Term Browser. Scott thinks this could be a indexing issue. Tracy started re-indexing last night but received an error that there were “too many open files”. This is a configuration setting to fix. Jacob will find the setting, correct it, and send a note to Scott so he can add it to the PTE.
The URI Resolver passed the QA AppScan with no high or medium vulnerabilities. Scott is also looking at the large amount of low vulnerabilities.
|Report Writer||Put in DRT ticket for DEV tier setup for Report Writer 2.1 environment. |
There were several data discrepancy issues that we believe are due to the indexing issue. Tin will retest once the re-indexing is completed.
Performed trouble-shooting on the Term Browser Home page formatting issue. The extra blank lines were found to be related to inconsistent metadata value assigned to NCI Thesaurus. Added fault-tolerance to accommodate metadata display name naming variation.
|Meta Download Validation App|
|Term Suggestion Form|
The containers are still being worked on for the new development environment.
The Metathesaurus 2.5 container is now ready and the AHP setup has been completed. However, there was an issue where the CM team was pulling code from the wrong repository (NCIP instead of EVS) which caused issues. The CM team is making the update to the correct Git repository.
|EVSREPORT-94||Generate reports without the UI.|
Developed a method for querying available standard report template labels without using the UI.
Developed a method for retrieve the content of a standard report template without using the UI.
|Migrate to LexEVSAPI 6.2.|
Identified the difference between version 6.1 and version 6.2 of LexEVSAPI remote client jars.
|NCITERM-605||Update the on-line Help page for 2.6 Term browser release.|
Added a paragraph describing the usage of the Release File button to the Value Set Tab section.
Modified a paragraph to include the usage of keystrokes to navigate value set trees.
|Area of Interest||Details|
|Term Browser 2.6 Release||Continue design activities for new feature requests|
|NCIm Browser 2.5 Release|
Deployment to the DEV tier.
|Report Writer||Develop Project plan for 2.1 release.|
|Term Browser 2.5 Release||Deployment to the Stage tier.|
|Term Form 2.4 Release||Deployment to the DEV tier.|
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>|