NIH | National Cancer Institute | NCI Wiki  

Attendees

NameRole
  
  
  

 

Action Items

 #AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
      .

Progress

Area of InterestDetails
LexEVSEntered a ticket to create a VM that images the current DEV environment to be used while the CentOS and Java 8 upgrades.
Report Writer

 

Term Browser 

Performed the trouble-shooting on resolved value set coding scheme containing only a single concept issue.

    • Retrieved all 743 value set definition files from DEV.
    • Dynamically retrieved concept entities from all corresponding resolved value set coding schemes.
Term Suggestion Application 
NCIm Browser 
Triple Store Prototype

 

Biomarkers Support

 

Neoplasm Core 
Other Support 

JIRA Issues

Issue NumberDescriptionStatus
NCITERM-745Top node of value sets deselected after search.Fixed
   
   

  • Schedule Changes

 

#DescriptionDue DateResourcesNotesRisksMitigation
       

  •  Planned Activities

Area of InterestDetails
Term Browser 2.9 ReleaseContinue 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