Attendees
Name | Role |
---|---|
Action Items
# | Assigned | Description | Date Identified | Due Date | Date Completed | Status |
---|---|---|---|---|---|---|
. |
Progress
Area of Interest | Details |
---|---|
LexEVS |
|
Report Writer |
|
Term Browser | The Term Browser 2.11.1 has been deployed to production. Term Browser 2.12 release - Continuing work on 508 compliance items. |
NCIm Browser |
|
Term Suggestion Application |
|
EVS REST API | Deployment is complete on production. |
Biomarkers Support |
|
SPARQL Report Writer | Continued development of the UI. Gave an updated command line version to operations team for testing and have some received some feedback which will be implemented. |
Other Support |
|
JIRA Issues
Issue Number | Description | Status |
---|---|---|
NCITERM-774 | 508 - Add role=presentation to table declaration. | Implemented |
NCITERM-775 | 508 All form elements must have a label. | Implemented |
NCITERM-776 | 508 Skip Navigation and Tabbing difficult. | Fixed |
NCITERM-777 | 508 All images must have an alt. | Fixed |
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 |
---|---|---|
. | ||