Attendees
Name | Role |
---|---|
Action Items
# | Assigned | Description | Date Identified | Due Date | Date Completed | Status |
---|---|---|---|---|---|---|
. |
Progress
Area of Interest | Details |
---|---|
LexEVS | |
Report Writer | |
Term Browser | Firewall exception for the 2.11 release have been approved for Stage and Production. Completed a patch release to include the DAP implementation. This made it to production in time for the August 2nd deadline. |
NCIm Browser | Firewall exception have been approved for Stage and Production. Updated release to include the DAP implementation. This will require another appscan and tiers deployment. |
Term Suggestion Application | Firewall exception have been approved for Stage and Production. Updated release to include the DAP implementation. This will require another appscan and tiers deployment. |
EVS REST API | Developed MainTypeHierarchy.java to implement:
|
Biomarkers Support |
|
Neoplasm Core |
|
Other Support |
|
JIRA Issues
Issue Number | Description | Status |
---|---|---|
NCITERM-764 | Implementing DAP. |
|
Schedule Changes
# | Description | Due Date | Resources | Notes | Risks | Mitigation |
---|---|---|---|---|---|---|
Planned Activities
Area of Interest | Details |
---|---|
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 |
---|---|---|---|---|---|
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 |
---|---|---|
. | ||