Attendees
| Name | Role |
|---|---|
Action Items
| # | Assigned | Description | Date Identified | Due Date | Date Completed | Status |
|---|---|---|---|---|---|---|
| . |
Progress
| Area of Interest | Details |
|---|---|
| LexEVS | Tested new resolved value set coding scheme load using LexEVS API 6.5.1. |
| Report Writer |
|
| Term Browser | The Term Browser 2.11.1 patch release has been deployed to stage, passed testing, and a request to deploy to production has been submitted. Term Browser 2.12 release - We made a couple of fixes before continuing up the tiers. |
| NCIm Browser |
|
| Term Suggestion Application |
|
| EVS REST API | EVSRESTAPI production firewall exception – Has been approved and completed. We now have a production environment. The new keyword search capabilities are going to be deployed up the tiers. We will request CTRP to test from the CBIIT environment to ensure nothing breaks their API. Explored methodologies for accessing terminology data through available SPARQL endpoints using coding scheme name and version (instead of graph name). Performed trouble-shooting on a possible firewall related issue. |
| Biomarkers Support |
|
| SPARQL Report Writer | Continued development of the UI. Giving the command line application to operations team for testing. |
| Other Support |
|
JIRA Issues
| Issue Number | Description | Status |
|---|---|---|
| NCITERM-771 | Support download of file based mappings. | The user group reviewed and accepted the implementation. |
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 |
|---|---|---|
| . | ||
