NIH | National Cancer Institute | NCI Wiki  

Attendees

NameRole
  
  
  

 

Action Items

 #AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
      .

Progress

Area of InterestDetails
LexEVS

Tested new resolved value set coding scheme load using LexEVS API 6.5.1.

Report Writer

 

Term Browser 

The 2.11.1 patch release is currently on QA awaiting completion of the appscan.

The 2.12 release is in development.  There have been several changes made to the Value Set page that require review from the EVS user group.

NCIm Browser

 

Term Suggestion Application

 

EVS REST API Met with EVS group to discuss possible requirements of the search capabilities of the API.  Also showed a demo of the current capabilities.
Biomarkers Support

 

SPARQL Report Writer

Continued development of the UI.

Other Support

 

JIRA Issues

Issue NumberDescriptionStatus
NCITERM-767

Blank page when going to cart after adding concept.

In the 2.11.1 patch release
NCITERM-766Blank Page when selecting 'show all versions'In the 2.11.1 patch release
NCITERM-768Migrate to lexevsapi65-6.5.1.In the 2.12 release on DEV
NCITERM-769Rebuild value set trees using SourceAssertedValueSetHierarchyServicesImplIn the 2.12 release on DEV

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