NIH | National Cancer Institute | NCI Wiki  

Attendees

NameRole
  
  
  

 

Action Items

 #AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
      .

Progress

Area of InterestDetails
LexEVS 
Report Writer

Continue to evaluate new report writer query builder requirements.

Term Browser 

Explored methodologies for show and hide property and role qualifiers.

Provided technical support to the Cads team to resolve a HTTP redirect problem.

Term Suggestion Application

NCIm Browser

Testing was completed on the NCIm Browser 2.6 release and a request to deploy to stage has been submitted.

Completed deployment to the Stage tier and passed the appscan with no high or medium vulnerabilities.

JIRA Issues

Issue NumberDescriptionStatus
NCIM-217

Current link to MedDRA MSSO and information needs updating.

Fixed.
NCIM-218Link to NCI Thesaurus is affected by move to SSL. Needs updating.

Fixed.

  • Schedule Changes

 

#DescriptionDue DateResourcesNotesRisksMitigation
       
  •  Planned Activities

Area of InterestDetails
Term Browser 2.8 ReleaseLook at possible requirements for 2.8 release.
NCIm Browser 2.6 ReleaseComplete deployment of the 2.6 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