NIH | National Cancer Institute | NCI Wiki  




Action Items

 #AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus


Area of InterestDetails
Report Writer


Term Browser 

Did not receive any additional feedback from the users about the 2.10 release.  It was decided to proceed with the deployment through the tiers as is.
Term Suggestion Application 
NCIm BrowserWill need to do a release for the Java 8 upgrade with the next release of the LexEVS API.
Triple Store Prototype

Deployed the latest SPARQL Report Writer to the VM so users can start evaluating it. 

Biomarkers Support

Awaiting direction on updates to the prototype from that discussion.

Neoplasm Core


Other Support 

JIRA Issues

Issue NumberDescriptionStatus
NCITERM-751Value Set Display Redesign

Value sets with a non-NCIt default coding scheme.

Value sets with an NCIt default coding scheme, no supported source specified or no non-NCI supported source exists.

Value sets with an NCIt default coding scheme, at least one supported source specified and there exists a non-NCI supported source (for example, FDA).

NCITERM-754NCIt hierarchy breaks on OWL2 load.

Performed trouble-shooting and found that a LexEVS API issue related to the handling of namespace by the OWL2 loader might have caused the TreeService getSubconcepts method to fail. Will informed Mayo of this observation.

NCITERM-755ALT-DEFINITION sources in OWL2 formatted ontologies are not showing.

Performed trouble-shooting and observed that there are discrepancies in the way ALT_DEFINITION sources are handled by the OWL and OWL2 loaders. The OWL loader stores the source data in Source whereas the OWL2 loader populates the same data in PropertyQualifier instead. This causes the downstream client application such as the term browser to break. 

Schedule Changes


#DescriptionDue DateResourcesNotesRisksMitigation
  •  Planned Activities

Area of InterestDetails
NCIm and Report Writer releaseDeveloping a new release of NCIm browser for a Chrome issue and Report writer to make compatible with the latest LexEVS API.

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
 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