NIH | National Cancer Institute | NCI Wiki  




Action Items

 #AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus


Area of InterestDetails
LexEVS 6.3

The SCM team was working on the AHP setup but found an issue with the build where the CTS framework was not found.  The Mayo team is working with them to get the build fixed.

Still having some issues to resolve on the Nexus end, the proxy was not being updated with the new framework and we had to take the Proxy offline because we were having some issues with Mayo over flooding the Nexus Logs.

Report Writer

Need a decision on where this functionality is going to go to start creating trackers and scope document.

Term Browser 

Kim has cleared many of the error messages and has expanded the automated test to the view in hierarchy.

Meta Download Validation App

Term Suggestion Form


NCIm Browser

 Evaluated the effort of expanding the automated test application to the NCIm Browser.  Effort for the NCIm browser should be considerably less than Term Browser.

JIRA Issues

Issue NumberDescriptionStatus
NCITERM-660UI Testing Utility.

Implemented code for generating test cases for view hierarchy.

Modified code to accommodate coding schemes without a hierarchy (e.g., HL7).

Performed trouble shooting on advanced relationship search. The values in the relationship name combo box are not populated properly causing the automatically generated selenium validation code to fail.

Provided the latest jar files developed to the QA team.

Updated the value set configuration file.



Schedule Changes


#DescriptionDue DateResourcesNotesRisksMitigation

 Planned Activities

Area of InterestDetails
Term Browser 2.7 ReleaseContinue development of the 2.7 release.

Risks, Issues, Dependencies


Opened DateDue DateDescriptionLikelihood (H, M, L)ImpactAssignedStatusMitigation Strategy
 04/10/14 Deployments have been taking long periods of time. There is a lot of overhead getting through the itersH H Speaking with members of the QA team to find ways to streamline the testing/deployment processFinding ways to better integrate the development and QA team. Spoke to EVS Tools TPM requesting the correct communication channels.


 #Opened DateDescriptionImpactAssignedStatus
 7/17/2014Deployment 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/2014Getting 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>


Opened DateDescriptionAssigned
  • No labels