NIH | National Cancer Institute | NCI Wiki  




Action Items

 #AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus


Area of InterestDetails
LexEVS 6.3

Put in ticket for the AHP setup for LexEVS 6.3 CTS2 service to be deployed on DEV.  We need to test the LexEVS 6.3 against the 6.2 CTS2 interface because the 6.3 will be deployed before CTS2 makes it to production.  If the testing passes, we will continue deploying 6.3 to production, if there are issues we will need to wait until the 6.3 CTS2 implementation makes it to production.

We did put in the ticket for AHP setup for 6.3 on production in anticipation of the deployment.

Report Writer

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

Term Browser 

The original capability of the auto generating selenium scripts application is functioning and id now being installed by the test team.

Wrote the code to retrieve source and target coding scheme name and version through LexEVS but found out the version was not populated. Contacted Mayo about and Scott said he will look into it when he comes back from vacation.

Meta Download Validation App

Term Suggestion Form


NCIm Browser


JIRA Issues

Issue NumberDescriptionStatus
NCITERM-603Improved presentation of NCIt role relationships.

The user group has decided not to include equivalence classes in the role and inverse role tables on the Relationship tab.

NCITERM-659Unit test framework.

Continue to develop JUnit test suites.

Provided a JUnit test jar to the QA team.


NCITERM-660UI Testing Utility.

Continue to develop selenium test code generator.

Provided a selenium test code generator jar to the QA team.

Schedule Changes


#DescriptionDue DateResourcesNotesRisksMitigation

 Planned Activities

Area of InterestDetails
Report WriterDevelop Project plan for 2.1 release.
Term Browser 2.7 ReleaseScheduling the release and start development.

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