NIH | National Cancer Institute | NCI Wiki  

Attendees

NameRole
  
  
  

 

Action Items

 #AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
      .

Progress

Area of InterestDetails
LexEVS 
Report Writer 
Term Browser The QA team has started testing the 2.11 release of the Term Browser.  So far things look good.

NCIm BrowserThe QA team has started testing the 2.8 release of the NCIm browser.  So far things look good.
Term Suggestion ApplicationTesting has resumed on the QA tier. 
EVS REST API

Improved the performance of the prototype server application.

Implemented code for identifying if a concept is a stage concept, i.e., a source of a Disease_Is_Stage role relationship.

Developed SPARQL statements for retrieving roles, inverse roles, associations, and inverse associations from the triple-store server.

Biomarkers Support

 

Neoplasm Core

 

Other Support

In supporting the CTRP tiger team effort, developed a program to convert a report containing subtypes and stages of some main cancer terms to a specific format.

JIRA Issues

Issue NumberDescriptionStatus
   

Schedule Changes

 

#DescriptionDue DateResourcesNotesRisksMitigation
       
  •  Planned Activities

Area of InterestDetails
  
  

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
      
 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