NIH | National Cancer Institute | NCI Wiki  

Attendees

NameRole
  
  
  

 

Action Items

 #AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
      .

Progress

Area of InterestDetails
LexEVS 6.3

Scott will send Preston an email with what was done so it can be used to get waivers for the AppScan, 508, and minimized QA test plan/results. 

Report Writer

Need a decision on where this functionality is going to go to start creating trackers and scope document.

Term Browser 

We have been reviewing the rest of the scope items to make sure 6.3 LexEVS covers our requirements.  We did find some compatibility issue with 6.3 and 2.6 browser. 

Worked with the Operations team to resolve a few metadata issues found on the Stage tier.

Meta Download Validation App

Term Suggestion Form

 

NCIm Browser

 

JIRA Issues

Issue NumberDescriptionStatus
NCITERM-595Handle coding schemes with multiple namespaces.

Tested Version 6.3 LexEVSAPI new jars and identified a backward compatibility issue due to the refactoring of the tree extension. The package name of tree service class was changed when the tree extension API was merged into the core LexEVS API. 

NCITERM-660UI Testing Utility.

Provided the QA team a sample output of the selenium code generator.

NCITERM-654Value Sets: After performing a simple search in the Released File view, the formatting of the page needs adjustment.

Assessed the JSP code required to fix the reported problem.

NCITERM-657View In Hierarchy: When viewing a concept in Zebrafish, clicking on the View In Hierarchy link does not bring up the Zebrafish Hierarchy Tree.

This is likely due to multiple namespaces in  Zebrafish.

NCITERM-610Update caBIG VKC link.

Identified two welcome pages where changes need to be made to satisfy the feature request. 

NCITERM-620HGNC View Graph link no longer works.

Performed trouble-shooting and identified the root cause being that NCBO uses code with an underscore (‘_’) whereas NCI uses ‘:’ instead.

NCITERM-661Allow browser startup without value sets.

Assessed the complexity of implementing the feature request.

   

Schedule Changes

 

#DescriptionDue DateResourcesNotesRisksMitigation
       

 Planned Activities

Area of InterestDetails
Term Browser 2.6 ReleaseContinue review fixes and deployment.
Report WriterDevelop Project plan for 2.1 release.
Term Browser 2.7 ReleaseScope development

Risks, Issues, Dependencies

Risks

Opened DateDue DateDescriptionLikelihood (H, M, L)ImpactAssignedStatusMitigation Strategy
 04/10/14 Deployments have been taking long periods of time. There is a lot of overhead getting through the itersH H Speaking with members of the QA team to find ways to streamline the testing/deployment processFinding ways to better integrate the development and QA team. Spoke to EVS Tools TPM requesting the correct communication channels.
         

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