NIH | National Cancer Institute | NCI Wiki  




Action Items

 #AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus


Area of InterestDetails
LexEVS 6.3

The AHP setup for LexEVS 6.3 on production has been completed.  Testing of the 6.2 CTS2 Service with LexEVS 6.3 was completed and it looks like it is behaving as expected.  We will proceed with the production deployment Thursday morning.  The SCM is also working on the AHP setup for the 6.3 CTS2 service on the DEV environment.  We are going to use the current 6.2 containers for the 6.3 CTS2 Service.


Development database updates - Kim and Scott doesn't think there would be issues from a software development side but the operations side sees some pitfalls. Mainly the compatibility of the indexes is needed to make the monthly updates doable from a time and resource side
Report Writer

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

Term Browser 

Still working on the automated testing tasks.  Having some issues with the reliability of the Selenium API. 

Meta Download Validation App

Term Suggestion Form


NCIm Browser


JIRA Issues

Issue NumberDescriptionStatus
NCITERM-675Please add source and target versions to the header for Mappings

Invested programming access to the source and target versions of a mapping coding scheme.

The user group has decided not to display source and target versions of the mapping on the banner. The Operations team will modify metadata to satisfy the feature request.

NCITERM-660UI Testing Utility.

Developed a test suite for testing advanced search.

Developed an initial capability for generating selenium test code.

Per the Operation team request, developed a Metathesaurus utility to retrieve GO to NCIt mapping data through Metathesaurus CUIs.

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