NIH | National Cancer Institute | NCI Wiki  




Action Items

 #AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus


Area of InterestDetails
Report Writer 
Term Browser The QA team has started testing the 2.11 release of the Term Browser.  So far things look good.

NCIm BrowserThe QA team has started testing the 2.8 release of the NCIm browser.  So far things look good.
Term Suggestion ApplicationTesting has resumed on the QA tier. 

Separated "common" properties from "additional/other" properties.

Implemented the isStage method for identifying concepts with a Disease_Is_Stage role.

Implemented queries for retrieving all relationships (superconcepts, subconcepts, roles, inverse roles, associations, inverse associations).

Modified path enumeration algorithm to accept an additional concept code, the path will stop when the corresponding node is reached.

Developed a method for improving the performance of the path enumeration algorithm through the caching of distance-one (i.e., hierarchical) relationships.

Biomarkers Support


Neoplasm Core


Other Support


JIRA Issues

Issue NumberDescriptionStatus

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