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.3 | Continued to support LexEVS OWL2 API requirement validation. |
| Report Writer | The URL switch from the old environment to the shady grove environment was completed. |
| Term Browser | Testing for the 2.6 release on QA was completed and the test results were approved. Request for deployment to Stage has been submitted. Working on scope for the 2.7 release. |
| Meta Download Validation App | |
| Term Suggestion Form |
|
| NCIm Browser |
|
JIRA Issues
| Issue Number | Description | Status |
|---|---|---|
| LEXEVS-852 | The buildJsonPathFromRootTree method returns JSON string with no namespace. | Submitted this JIRA ticket. |
| NCITERM-603 | Improved presentation of NCIt role relationships. | Prepared power point slides to show various options available for presenting annotations for role and association relationships as well as property qualifiers. |
| NCITERM-658 | Migrate to LexEVSAPI 6.3. | Tested the latest tree extension jar in the v6.3 RC and identified two issues. First, the paths to roots were found to contain concepts that do not belong to the NPO coding scheme; secondly, the namespace of concepts contained in paths to roots are not found in the JSON string returned by the API. The Mayo team will investigate. |
| NCITERM-660 | UI Testing Utility. | Tested mapping search API and observed that the iterator returned by the API remains broken in v6.3 RC - it will not advance. The Mayo team will examine the issue in their next Agile Sprint. |
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. |
| Report Writer | Develop Project plan for 2.1 release. |
| Term Browser 2.7 Release | Scope development |
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 |
|---|---|---|
| . | ||
