|#||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||Received the specifications for the Mayo DEV server but found that it was much more robust than can be provided to the EVS applications at NCI. Put in DRT tickets to up the DEV VM by one vCPU and an additional 2GB RAM per recommendation by the systems team and we will go from there. They systems team also removed the load balancing from the all the applications. Having the applications loaded on both nodes was using up too many resources.|
|Area of Interest||Details|
|LexEVS 6.1||The API has been deployed to QA tier. Mayo is working with CM team to get the official release candidate on the DEV tier with all LexEVS components.|
|LexEVS 6.0 and 5.1|
The test plan has been created and submitted for approval for both LexEVS 5.1 and 6.0. QA team worked with Kim Ong to get the deployment and testing steps to proceed. Environment is now setup on QA tier.
|Term Browser 2.3 Release|
Testing is ongoing for the browsers. QA team ran into some HTTP status 500 errors which required a restart of the JBoss container. It looks like it may have started having issues on the mapping tab.
|Meta Download Validation App||Waiting for the final decision on whether to use the EVS or CBIIT interface. A meeting was held and the discussion items are being put together and are supposed to be distributed. Still waiting for the final decision. Development is on hold until then.|
|Term Suggestion Form||QA team has the tag to start testing but has not had time to do anything with it yet.|
|NCIm Browser||In the EVS meeting, the users requested a link to the Term Suggestion application from the Quick Links in Metathesaurus Browser. This is to make it consistent with the Term Browser.|
|GF#32941||NCI Thesaurus Subsets Page: Pediatric Terminology link is incorrect.|
The target page at http://www.cancer.gov/cancertopics/cancerlibrary/terminologyresources/pediatric is under construction.
Waiting for the user group’s final decision on whether to change the link.
|GF#32920||Drop the NCIt list_standard_reports page.||Implemented.|
|GF#32924||Update the on-line Help page.|
|GF#32942||Modify Introductory Text on the Value Set Home Page.|
|GF#32906||Update the NCIm Sources page.|
Made further modification to the page to correct the Vocabulary Knowledge Center (VKC) link.
Ready for QA validation.
|GF#32934||CDISC Form - Link to Excel Template.|
The Operations team will store the text description shown on the top of the page (currently being hard-coded) in a metadata element called source-header. The source help page will be modified to retrieve the text description directly from the metadata.
|GF#32816||Migrate to LexEVS API 6.1.||6/28/2013||1 Developer||We are still reviewing the new deployment of LexEVS 6.1 on DEV. This date is dependent on the value sets issues describe previously.|
|Moving up Development Time||7/17/2013||We are pushing to get the coding done for a July 17th review by the EVS users. This will give the users a chance to provide input on the implementation before we completely freeze the code.|
|Pushing back the start of the user evaluation||7/22/2013||Having an issue with the exact match search. Working with mayo to get it resolved but need it fixed before user can review.|
|Delay starting QA testing for Term Browser and NCIm Browser||7/13/2013||We had to delay the start of the QA testing since a fully functioning API has not been established on the QA tier.|
|Area of Interest||Details|
|Term Browser 2.3 Release||Provide any updates based on the user review/testing.|
|Term Browser 2.3 Release||Make any required fixes from QA testing.|
|Term Suggestion Application Release||Make any required fixes from QA testing.|
|NCIm Browser||Make any required fixes from QA testing.|
Risks, Issues, Dependencies
|#||Opened Date||Due Date||Description||Likelihood (H, M, L)||Impact||Assigned||Status||Mitigation Strategy|
|6/19/13||9/30/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.|
|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.||Received approval to proceed to QA tier with LexEVS 6.1.|
|Term Browser 2.3 release dependent on the LexEVS 6.1 release. See the Issue listed for 7/31/2013 for details on the status.|