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 | The Stage firewall exception has been approved for the API and CTS2 service. Submitting request for production firewall exception this week. |
| Report Writer | Still working on the DEV tier. CM Team tried deploying but not successful so far. |
| Term Browser | Received the firewall exception for stage tier. Submitting request for production firewall exception this week. Responded to comments on value set implementation by the user group. Worked on performance issue with the Concept Details page. Made some improvement to the Property tab page. Continued to perform trouble-shooting on the root cause for the long page rendering delay. Working on the issue with the slower performance on retrieving concept details from the "Release File" functionality. |
| Meta Download Validation App | |
| Term Suggestion Form | Deployment to production for the 2.4 release has been completed. Currently working on the firewall exception for Stage and Prod. |
| NCIm Browser | Received the firewall exception for stage tier. Submitting request for production firewall exception this week. |
JIRA Issues
| Issue Number | Description | Status |
|---|---|---|
| NCITERM-595 | Handle coding schemes with multiple namespaces. | Tested the new tree extension, lexevs-tree-2.1.0.jar, made available by the Mayo team at: https://cbiit-download.nci.nih.gov/evs/LexEVS/v6.2/lexevs-tree-2.1.0.jar. The namespace in tree node is now populated. But, there was a minor formatting issue. Informed Mayo of the observation. The Mayo team subsequently fixed the formatting issue. Will test path to root function as soon as the data for supporting the namespace navigation is set up properly on the DEV server. |
| TBD | Resolved the Proxy error triggered by the Values button on the home page of the value set, FDA Established Names and Unique Ingredient Identifier Codes Terminology. |
Schedule Changes
| # | Description | Due Date | Resources | Notes | Risks | Mitigation |
|---|---|---|---|---|---|---|
Planned Activities
| Area of Interest | Details |
|---|---|
| Term Browser 2.6 Release | Continue review fixes and deployment. |
| NCIm Browser 2.5 Release | Deployment to the DEV tier. |
| Report Writer | Develop Project plan for 2.1 release. |
| Term Browser 2.5 Release | Deployment to the Stage 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 |
|---|---|---|
| . | ||
