EVS Tools Meeting Minutes - 02 August 2017

Attendees

#	Assigned	Description	Date Identified	Due Date	Date Completed	Status
						.

Area of Interest	Details
LexEVS
Report Writer
Term Browser	Firewall exception for the 2.11 release have been approved for Stage and Production. Completed a patch release to include the DAP implementation. This made it to production in time for the August 2nd deadline.
NCIm Browser	Firewall exception have been approved for Stage and Production. Updated release to include the DAP implementation. This will require another appscan and tiers deployment.
Term Suggestion Application	Firewall exception have been approved for Stage and Production. Updated release to include the DAP implementation. This will require another appscan and tiers deployment.
EVS REST API	Developed MainTypeHierarchy.java to implement: IsMainType, isSubtype, isDiseaseStage, isDiseaseGrade, getMainMenuAncestors
Biomarkers Support
Neoplasm Core
Other Support

Issue Number	Description	Status
NCITERM-764	Implementing DAP.	Produced a new tag 2017-07-25.1-v2.11 (v2.11-Beta.2) for QA. Produced a new tag 2017-07-27.1-v2.10 (v2.10-Beta.8) based on 2017-04-04.1-v2.10-branch) for QA.

#	Description	Due Date	Resources	Notes	Risks	Mitigation

Area of Interest	Details

Risks

#	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.

Opened Date	Description	Impact	Status

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>