Attendees
| Name | Role |
|---|---|
Action Items
| # | Assigned | Description | Date Identified | Due Date | Date Completed | Status |
|---|---|---|---|---|---|---|
| Mayo/Jason | We 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/2014 | A new development server has been procured and is currently being setup. This AI will be closed. |
Progress
| Area of Interest | Details |
|---|---|
| LexEVS 6.2 | Pushing this week to get the QA and Stage containers setup for next week. QA server is in place and the systems team is working on the containers. Stage server is available and should be setup by Sept 19th. Submitted a new JIRA item: [LEXEVS-667] TreeService getTree method fails on remote call when the root node code appears in multiple namespaces |
| Report Writer | Sent the Scope of to the users and received some feedback. Will update the scope document this week. |
| Term Browser | The 2.5 release is now working on both the DEV and QA tiers. Put in ticket for the stage tier container. Updated the value of application.version and application.version.display (i.e., lexevsapi version) in the project.properties configuration file. Tested build and deployment of the browser on AntHillPro3 and failed. Apparently, the old war directory and related files were not removed when the new war was deployed on AntHillPro3. The Systems team has identified and fixed the problem subsequently. |
| Meta Download Validation App | Deployment to production has been completed. We may need to revert to the old site because permission to update the CBIIT website have been taken away. |
| Term Suggestion Form | The containers are still being worked on for the new development environment. |
| NCIm Browser | The containers are still being worked on for the new development environment. |
JIRA Issues
| Issue Number | Description | Status |
|---|---|---|
| LexEVS-598 | TreeService getTree method can fail when the root node code appears in multiple namespaces. | Tested remote lexevsapi62 API and encountered an unexpected error getting generic extension for tree-utility - LogID Reference [LOG_ID 12]. The Mayo team explained that the fix is applicable to local call only (See {LEXEVS-667]). |
NCITERM-595 | Handle coding schemes with multiple namespaces. | Set up a local development environment in responding to the limitation of LexEVSAPI 6.2
|
Schedule Changes
| # | Description | Due Date | Resources | Notes | Risks | Mitigation |
|---|---|---|---|---|---|---|
Planned Activities
| Area of Interest | Details |
|---|---|
| Term Browser 2.6 Release | Continue design activities for new feature requests |
| NCIm Browser 2.5 Release | Deployment to the DEV tier. |
| Term Browser 2.5 Release | Deployment to the DEV tier. |
| Term Form 2.4 Release | Deployment to the DEV tier. |
Risks, Issues, Dependencies
Risks
| # | Opened Date | Due Date | Description | Likelihood (H, M, L) | Impact | Assigned | Status | Mitigation Strategy |
|---|---|---|---|---|---|---|---|---|
| 04/10/14 | Deployments have been taking long periods of time. There is a lot of overhead getting through the iters | H | H | Speaking with members of the QA team to find ways to streamline the testing/deployment process | Finding ways to better integrate the development and QA team. Spoke to EVS Tools TPM requesting the correct communication channels. | |||
Issues
| # | Opened Date | Description | Impact | Assigned | Status |
|---|---|---|---|---|---|
| 7/17/2014 | Deployment 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/2014 | Getting 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 Date | Description | Assigned |
|---|---|---|
| . | ||
