NIH | National Cancer Institute | NCI Wiki  




Action Items

 #AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus


Area of InterestDetails
Report Writer

Provided a new tag for the issues the systems team was having with deploying to the new DEV blade server.

Resolved a root node ordering issue in Neoplasm Core Hierarchy and Neoplasm Core Hierarchy Plus html files.

Produced CTRP reports to include NCIt code, NCIt preferred name, Disease_Is_Grade and Disease_Is_Stage role relationships, and Semantic_Type data for all NCIt concepts coded by CTRP trials.  

Developed and implemented an algorithm for finding Stage concepts relevant to a CTRP lead cancer category.

Term Browser 

NCIm Browser 
Term Suggestion ApplicationWaiting for deployment of the new tag to the new blade server for testing.
Triple Store Prototype

Had to reschedule the SPARQL report writer meeting for Tuesday at 1:00.

Biomarkers Support

Need to shutdown the application until work can be done on a SOLR issue.

Neoplasm Core

Resolved a root node ordering issue in Neoplasm Core Hierarchy and Neoplasm Core Hierarchy Plus html files.

Other Support


JIRA Issues

Issue NumberDescriptionStatus
  EVSREPORT-105JAVA 8 UpgradeRebuilt neopl-core.jar for generating the neoplasm core package.

Schedule Changes


#DescriptionDue DateResourcesNotesRisksMitigation
  •  Planned Activities

Area of InterestDetails

Risks, Issues, Dependencies


Opened DateDue DateDescriptionLikelihood (H, M, L)ImpactAssignedStatusMitigation Strategy
 09/10/2015  H H AppScan are taking long periods of time to complete.  For Term browser, the minimum has been 5 days.We are working on both the code base and configuration of the scan to try to improve performance.  We are also looking at open source code scanners that could possibly be used ahead of the AppScan to at least limit the number appscans required.


 #Opened DateDescriptionImpactAssignedStatus
 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