NIH | National Cancer Institute | NCI Wiki  




Action Items

 #AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus


Area of InterestDetails
LexEVSMaking preparations for the new environment.  Need the ARC and PTE document from Mayo and then we will put in the ticket.
Report Writer


Term Browser 

Still waiting for the AppScan to complete.  The security team said there was some issues with the AppScan automation and was having to manually do some test.

Term Suggestion Application

NCIm Browser 
Triple Store Prototype

Developed an OWL file for storing value set metadata (i.e., code, label, URI, and sources).

Loaded both Terminology_Value_Set.owl currently used by the term browser and the value data OWL file generated above to the Jena-Fuseki triple-store server as separate databases.

Created OWL annotation properties for supporting the mapping data conversion effort below.

Generated an OWL file for each mapping stored in the STAGE server.

    • GO_to_NCIt_Mapping
    • MA_to_NCIt_Mapping
    • NCIt_to_ChEBI_Mapping
    • NCIt_to_HGNC_Mapping
    • PDQ_2014_08_29_TO_NCI_2014_12E

Loaded all five mapping OWL files to the Jena-Fuseki triple-store server as separate databases.

Modified the property file to accommodate the mapping data.

Developed code for displaying the content of each mapping (i.e., mapping entries).

Modified the property file to accommodate value set metadata described above.

Produced code for displaying the list of value sets as defined in the value set metadata OWL mentioned above.

Produced code for resolving all value sets with a Concept-In-Subset referenced association through SPARQL calls.

Produced code for displaying the content with the above type of resolved value sets.

Developed a method for dynamically resolving values sets with a subClassOf referenced association without depending on the caching or serialization of  any object equivalent to LexEVS’s Resolved Value Set Coding Scheme.

JIRA Issues

Issue NumberDescriptionStatus

Unexpected behavior found in searching value set using LexEVSValueSetDefinitionServices API.


Modify search results returned from the search against resolved value set coding scheme.

LEXEVS-1731Allow exclusion of anonymous classes optionally in dynamic resolution of a value set definition.Submitted.
LEXEVS-1732Modify coding scheme name and version of ResolvedConceptReference returned from a resolved value set coding scheme.Submitted.
NCITERM-722When on the Values page of a Value Set, search is returning no results.

Tried to implement a workaround. The alternative approach was able to return matched concepts, but the coding scheme name for these returned concepts have a null value.

The Operations team identified that there is an NCI Thesaurus on the DEV server that has not been activated.

Tested the browser on DEV and confirmed that the inactivated NCI Thesaurus is the root cause for the failing resolved value set search.

Rolled back the code to the original implementation.

Verified by QA.

NCITERM-723Resolved value set contains anonymous classes.

Confirmed that the Tomcat ownership and file permission issue is the root cause for the failing dynamic resolution of value sets based on a value set definition.

Verified by QA.

NCITERM-725Hyperlinks on the resolved value set page is broken.


Verified by QA.

NCITERM-726Searching resolved value set returns incorrect coding scheme version.


Verified by QA.


View graph failed on concepts hyperlinked from the resolved value set (Values) and resolved value set search results pages.


Verified by QA.

NCITERM-728View Graph is not rendering when selecting Concepts listed on the Visited Concepts List.


Verified by QA.

  • Schedule Changes


#DescriptionDue DateResourcesNotesRisksMitigation
  •  Planned Activities

Area of InterestDetails
Term Browser 2.8 ReleaseContinue deployment of the 2.8 Term Browser release.  Look at the 2.9 Term Browser release items.
  • Risks, Issues, Dependencies

  • Risks

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.
  • Issues

 #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>
  • Dependencies

Opened DateDescriptionAssigned
  • No labels