Attendees
| Name | Role |
|---|---|
Action Items
| # | Assigned | Description | Date Identified | Due Date | Date Completed | Status |
|---|---|---|---|---|---|---|
| . |
Progress
| Area of Interest | Details |
|---|---|
| LexEVS | |
| Report Writer | Need a decision on where this functionality is going to go to start creating trackers and scope document. |
| Term Browser | MSSO support – created a interface for MedDRA to pull NCIt definition for MedDRA concepts in their browser. AppScan started Tuesday morning
If the data deployment happens before the appscan is completed we will contact security team and put the scan on hold and pick it back up once the data deployment is finished. |
| Meta Download Validation App | |
| NCIm Browser | Completed initial scope document. Working on the Unit test application. |
JIRA Issues
| Issue Number | Description | Status |
|---|---|---|
| NCITERM-688 | Partonomy Tree. | Fixed a refocusing node issue. |
| NCITERM-682 | Contains search failed on search strings containing a colon character. | Fixed. |
| NCITERM-670 | Term Browser AppScan Performance | Responded to appscan report. |
| NCITERM-694 | Can't select anything else besides 50 results per page. | Fixed. |
| NCITERM-693 | Help: Link to Release Notes still referencing version 2.6 and is still linked to 2.6 Release Notes | Fixed. |
| NCITERM-697 | Clicking on "Sources" link brings up an empty popup. | Fixed. |
| NCITERM-698 | MSSO Support. | Discussed with the Mayo team and found that the current CTS2 API is not adequate for supporting this effort. The API does not return property qualifier (definition source) that is required to identify NCI definition. Designed and implemented an AJAX call for client applications to retrieve NCI Definition(s). |
Schedule Changes
| # | Description | Due Date | Resources | Notes | Risks | Mitigation |
|---|---|---|---|---|---|---|
Planned Activities
| Area of Interest | Details |
|---|---|
| Term Browser 2.7 Release | Test and deployment of the 2.7 release. |
| NCIm Browser 2.6 Release | Planning for development of 2.6 release. |
Risks, Issues, Dependencies
Risks
| # | Opened Date | Due Date | Description | Likelihood (H, M, L) | Impact | Assigned | Status | Mitigation Strategy |
|---|---|---|---|---|---|---|---|---|
| 09/10/2015 | H | H | AppScan are taking long periods of time to complete. For Term browser, the minimum has been 5 days. | We are working on both the code base and configuration of the scan to try to improve performance. We are also looking at open source code scanners that could possibly be used ahead of the AppScan to at least limit the number appscans required. | ||||
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 |
|---|---|---|
| . | ||
