EVS Focus Meeting Minutes - 31 July 2013

Attendees

Name	Role

Action Items

#

Assigned

Description

Date Identified

Due Date

Date Completed

Status

Mayo

Provide example code to assist us with the understanding of the handling of value sets as coding schemes. This understanding will assist in our development of a Value Set Entity Search (GF#32794) which is part of the Term Browser 2.3 scope.

Provide a convenience method for resolving value sets from a resolved concept reference.

6/19/13

6/25/13

10/26/13

Kim received the example code as part of the new release of LexEVS 6.1 to DEV.

Operations

Loading resolved value sets to test the performance to make sure additional work is not needed for the resolving value set performance.

6/19/13

6/21/13

Operations had an issue with with the latest release of the loader. Would not load a particular name field if over 50 characters. Mayo is updating so the it will be truncated at 50. Also had an issue with removing value sets but Mayo could not reproduce.

Progress

Area of Interest	Details
LexEVS 6.1	Waiting for approval for the latest tag to be deployed to QA tier so we can start testing the latest release of the browsers.
Term Browser 2.3 Release	Received feedback from the EVS user group. Not of the responses require code changes to the browsers at this point.
Meta Download Validation App	Development is complete except for updating skins and 508 compliance. Currently in the web development team's hands.

JIRA/Gforge Issues

Issue Number	Description	Status
GF#32870	Update the content of the NCI Thesaurus subset page.	Received input from federal sponsor and have updated the page.
TASKMGT-6030	AppScan for the Term Browser on DEV tier	The security team performed appscan on term browser and identified 3 low level items, one is related to email address passing (Email Address Pattern Found in Parameter Value), and the remaining two are related to NCIBO’s visualization widget (Flash parameter AllowScriptAccess was set to always).
TASKMGT-6032	EVS Applications on DEV keep going down.	Closed. The problem was found to be related to the deployment of the term form application using the GitHub repository.

#	Description	Due Date	Resources	Notes
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.

Planned Activities

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.

Risks, Issues, Dependencies

Risks

Opened Date	Due Date	Description	Likelihood (H, M, L)	Assigned	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.

Issues

Opened Date	Description	Impact	Status
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.	The removal of JAVA 1.6 on desktops has been put on hold.
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 word that LexEVS 6.1 can be deployed to QA if we receive approval from federal sponsor that the tag is a release candidate. We are currently preparing the approvals for this.

Dependencies

Opened Date	Description	Assigned
	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.

Content

Space Tools