Action Items

 #AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus


Area of InterestDetails

Reported a duplicated NCI_Thesaurus root nodes issue relating to the SourceAssertedValueSetHierarchyServicesImpl API to Mayo.

Report Writer


Term Browser 

Held he value set design meeting and believe we have a path for move forwarding. Still have a dependency on an update to LexEVS before we can proceed with the deployment of the 2.12 release.

Explored a possible solution to the display of resolved value sets with multiple supported sources (i.e., the Values button). The current implementation uses the first supported source returned by the LexEVS API. An alternative solution may involve creating a configurable partially ordered set of all possible supported sources.

NCIm Browser

Completed fixes for the 508 compliance but awaiting to see if there are other features required before deploying.

Term Suggestion Application


Biomarkers Support


SPARQL Report Writer

Continued development of the UI.  Development on schedule to complete mid January

Other Support


JIRA Issues

Issue NumberDescriptionStatus
LEXEVS-2183Tree Extension: TreeService API returns JSON String containing anonymous nodes.

Reproduced and tested code segment in responding to Mayo’s inquiry about the submitted JIRA item.

NCITERM-769Rebuild value set trees using SourceAssertedValueSetHierarchyServicesImpl.

Modified and


Schedule Changes


#DescriptionDue DateResourcesNotesRisksMitigation
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