NIH | National Cancer Institute | NCI Wiki  

Attendees

NameRole
  
  
  

 

Action Items

 #AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
      .

Progress

Area of InterestDetails
LexEVS 
Report Writer 
Term Browser 

Value set search on the QA tier failed. Performed trouble shooting and observed that three FDA value sets are not resolvable. The Operations team will work with editors to fix the data issue in the next baseline.

QA testing and AppScan was completed on the QA tier.  Deploying to the stage tier now.

NCIm BrowserQA testing and AppScan was completed on the QA tier.  Deploying to the stage tier now.
Term Suggestion ApplicationQA testing and AppScan was completed on the QA tier.  Deploying to the stage tier now.
EVS REST API

Developed codes for querying isDieaseStage and isMainType.

Developed metadata.owl for allowing client applications to query prefixes and identifiers (e.g., NHC0 for NCIt and oboInOwl for GO) using the vocabulary name and version).

Biomarkers Support

 

Neoplasm Core

 

Other Support

 

JIRA Issues

Issue NumberDescriptionStatus
LEXEVS-3136Possible HistoryService getDescendants method failure.Submitted the JIRA ticket

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