EVS Focus Meeting Minutes - 20 May 2015

Attendees

#	Assigned	Description	Date Identified	Due Date	Date Completed	Status
						.

Area of Interest	Details
LexEVS 6.3	While testing the remote API using the Term Browser we found an issue with the Mapping iterator not working. It was determined that this would not be fixable in the 6.3 release and will be documented in the 2.6 Term Browser release notes.
Report Writer	Need a decision on where this functionality is going to go to start creating trackers and scope document.
Term Browser	Had a discussion with Mayo and operations team discussing the current configuration of the Browsers and LexEVS. It was determined that there should not be any compatibility issues with the current 2.6 browser running on LexEVS after the 6.3 deployment. The browser would essentially be still running on 2.6 as the current components needed will not be removed.
Meta Download Validation App
Term Suggestion Form
NCIm Browser	It was determined that a 2.6 release will be needed when 2.7 Term Browser is deployed. This will mostly be for the LexEVS 6.3 compatibility.

Issue Number	Description	Status
NCITERM-623	Link to Value Set Query from a Value Set Term.	Completed the design. Distributed a file containing the screen-shots of the proposed design to the user group.
NCITERM-621	Link to the Value Set GUI from the Value Set Header Concept Page.	Completed the design. Distributed a file containing the screen-shots of the proposed design to the user group.
NCITERM-668	PDQ Definitions not correctly formatted.	Performed preliminary trouble-shooting and observed that the root cause is likely related to the missing definition source property qualifier. The browser uses this qualifier to identify PDQ definitions.
NCITERM-665	Add View Mapping button to the Mapping Search Results Page.	Completed the design.
LEXEVS-829	Mapping extension iterator delivers incorrect or infinite number of next() values.	Currently, the mapping extension iterator works under local mode, but not distributed mode. The Mayo team believes it is a data issue and will explain how to use a SQL insert statement to fix the equivalent namespaces in mapping coding schemes. Will retest the API when this data issue is resolved on NCI DEV.
LEXEVS-913	Establish and execute on backwards compatibility for 6.3.	Tested the new LexEVSAPI 6.3 release candidate (dated 5/08/2015) and identified that for LexEVS 6.3 to be backward compatible, the server needs to have the lexevs-tree-2.1.0.jar placed in the runtime/extension folder.

#	Description	Due Date	Resources	Notes	Risks	Mitigation

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

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

Opened Date	Description	Impact	Status
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>