|#||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||The server resources have been expanded with an addition vCPU and an additional 2GB memory. Initial tests have shown better performance but the testing is ongoing.|
|Area of Interest||Details|
Production environment has been setup and CTS2 and URI Resolver have been deployed.
Submitted a waiver for the LexEVS 6.1 firewall exception on stage tier. We have to get an exception for the JBoss 4.0.5 container on the server for LexEVS 6.1. We need to keep 5.1 running to support caDSR.
Put in a ticket for a container on the DataQA tier for LexEVS 6.1, CTS2, and URI resolver service.
There is also an issue with the remote calls for 6.1 on all tiers. The Mayo team is looking into the issue but says they are having a hard time replicating the issue.
|LexEVS 6.0 and 5.1||Both are on production and working. Per the comment above. We may be looking at a upgrade to JBoss 5.1.0 for LexEVS 5.1.|
|Term Browser||Working on finalizing the 2.4 release requirements. This will include an updated or removing of the NCBO graph widget.|
|Meta Download Validation App||Work on the GUI and continuing discussion on how the pages will be updated (Plone vs deployment from SVN)|
|Term Suggestion Form||Deployment to production has been completed. Need to re-deploy due to an issue to remove terminologies that have been retired that are showing up in production. Also need to do a manual step to update the CDISC spreadsheet.|
|NCIm Browser||Working on finalizing the 2.4 release requirements. This will includes updates to the contains search and lucene search added to advanced search.|
Provided technical support to the Operations team on trouble-shooting a multiple CDISC Submission Values issue. The issue appears to be data related. The new data have a source prefix that is not recognizable by the report writer application.
Make "Contains" the default on all searches.
Made “contains” the default algorithm for simple and advanced terminology search.
Made “contains” the default algorithm for value set search.
Made “contains” the default algorithm for mapping search.
|GF#31670||Changing standard width to 960 pixels.|
Modified width for all value set pages.
|GF#33141||Update the NCBO Visualization Widget.|
Reviewed NCBO new visualization widget implementation instruction. The new implementation requires NCBO ontology abbreviation and resource identifier. The NCBO ontology abbreviation for NCI Thesaurus is NCIT, which is not a local name of NCI Thesaurus in LexEVS. The resource identifier (i.e., class parameter in visualization widget) may not be accessible through the NCBO REST API. Therefore, both parameters would need to be configured via term browser property files. Terminology version is not used in the new visualization widget implementation.
Deprecated all code for the existing visualization widget implementation.
Modified the project.properties configuration file to include NCBO ontology abbreviation and class parameters for applicable terminologies.
Designed the beans and utility classes for processing the new configuration parameters.
Designed a new ncbo_widget.jsp for the new visualization widget.
Redesign the View Graph link in the concept_details.jsp.
|GF#33096||Link to subset page from the value set tab should be made non-static.|
Implemented and tested.
|Interim 2.4 release for the NCBO widget upgrade||TBD||There has been a change in the plans for the 2.4 release of the Term Browser due to the need to upgrade the NCBO graph widget which was scheduled to be retired at the end of January. We have been able to get this extended but need to do a limited release before the fully implemented features of the planned 2.4 release.|
|Area of Interest||Details|
|Term Browser 2.3 Release||Provide required support for deployment to Prod tier.|
|Term Browser 2.4 Release||Continue design activities for new feature requests|
|Term Suggestion Application Release||Make any required fixes from QA testing.|
|NCIm Browser 2.3 Release|
Provide required support for deployment to Prod tier.
|NCIm Browser 2.4 Release||Continue design activities for new feature requests.|
Risks, Issues, Dependencies
|#||Opened Date||Due Date||Description||Likelihood (H, M, L)||Impact||Assigned||Status||Mitigation Strategy|
|6/19/13||11/27/13||Term Browser 2.3 and LexEVS 6.1 are in parallel development with the Term Browser having a dependency on LexEVS release. Both have a hard deployment date of 9/30/2013. Anticipating some QA resource limitations with both schedules being in parallel.||M||Jason||Monitoring both schedules and will provide status to QA to make sure resources are available.|
|01/08/14||VPN access to the NIH network is going to be locked down to just GFE equipment. This could cause some problems with response time to issue after normal working hours.||We will work with the TPM on a mitigation strategy to include possibly getting a GFE laptop.|
|7/17/2013||Removal of JAVA 1.6 from desktops. The Term Browser deployments using AntHillPro require JAVA 1.6. Putting in a request for a waiver until we can upgrade.||This would affect the deployments and production environment for the EVS tools. It sounds like this is going to be a future issue but we should have time to upgrade before it is part of the CBIIT tech stack.||Provided a level of effort for migrating all of the EVS applications to Java 1.7 to the Technical Project Manager and government sponsor.|
|7/31/2013||We currently have an issue where the browsers are ready to move to the QA tier for testing but due to the dependency of LexEVS 6.1 cannot start the QA testing process. LexEVS 6.1 does not currently have all the pre-QA qualification to proceed with the deployment to the QA tier.||With a hard deadline of Sept. 30 for both the browsers and LexEVS API 6.1 there is concern that there will be time to finish all the testing and deployments on time.||This is closed. The hard deadline was expanded due to factors we cannot control.|