NIH | National Cancer Institute | NCI Wiki  

  • Attendees



Action Items

 #AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus


Area of InterestDetails
Report Writer


Term Browser 

Neoplasm Core Support:

Exploring a more efficient way to retrieve role relationships from the NCIt by parsing the OWL file directly.

Term Suggestion Application

NCIm Browser 
Triple Store Prototype 

JIRA Issues

Issue NumberDescriptionStatus
  • Unexpected behavior found in searching value set using LexEVSValueSetDefinitionServices API.

Developed code for verify the bug fix.

Updated lexbig.jar according to LexEVS sprint 32.

Ran the test program and verified the fix.

LexEVS-1999TreeServer API fails on RadLex, Version 3_13_1.

Performed trouble shooting and observed that the JSON string returned by the “tree-extension” API is incorrect.

  • Schedule Changes


#DescriptionDue DateResourcesNotesRisksMitigation
  •  Planned Activities

Area of InterestDetails
Term Browser 2.9 ReleaseStart development of the 2.9 Term Browser release.
  • 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