NIH | National Cancer Institute | NCI Wiki  

Attendees

NameRole
  
  
  

 

Action Items

 #AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
 Mayo/JasonWe have run into multiple issues where the performance on the DEV tier has be a problem due to Mayo not being able to replicate the slow points due to the drastic difference in DEV resources.  We discuss this with the systems team and they requested us to put in a DRT ticket that provides the specs to match the Mayo DEV server.08/30/13 7/16/2014A new development server has been procured and is currently being setup.  This AI will be closed.

Progress

Area of InterestDetails
LexEVS 6.3

Setting up the 6.3 development environment

Report Writer

We were able to successfully deploy Report Writer to the DEV environment.  Running into some DAO issues that we are currently working through.  Anticipating another tag.

  • Resolved a database connection failure issue. The root cause is that Tomcat was unable to locate the jaas.config file. The application is now working properly on the DEV tier after an environment variable is added to a Tomcat configuration file.


Term Browser 

The 2.5 release of the Term Browser is now live on the production environment.

  • Provided technical support to the Operations team on modifying the NICHD terminology metadata file so the terminology name, Prenatal and Pediatric Terminology, can be display properly on the home page.
Meta Download Validation App

Term Suggestion Form

Term Suggestion Form 24 release is now live on production.

NCIm Browser

The 2.5 release of the Metathesaurus Browser is now live on the production environment.

JIRA Issues

Issue NumberDescriptionStatus
LEXEVS-720 

Insure Interfaces align with public implementation methods where appropriate.

Developed a test program for testing a remote API method in the Mapping extension. The mappingExtension.resolveMapping method previously found to fail under remote calls appears to be able to sort mapping columns properly in LexEVSAPI 6.2.

NCITERM-595Handle coding schemes with multiple namespaces.

Tested the tree extension lexevs-tree-2.1.0.jar. Reported an SQL too many results exceptions to Mayo for further investigation.

   

Schedule Changes

 

#DescriptionDue DateResourcesNotesRisksMitigation
       

 Planned Activities

Area of InterestDetails
Term Browser 2.6 ReleaseContinue review fixes and deployment.
NCIm Browser 2.5 Release

Deployment to the DEV tier.

Report WriterDevelop Project plan for 2.1 release.
Term Browser 2.5 ReleaseDeployment to the Stage tier.
Term Form 2.4 ReleaseDeployment to the DEV tier.

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