Attendees
Name | Role |
---|---|
Action Items
# | Assigned | Description | Date Identified | Due Date | Date Completed | Status |
---|---|---|---|---|---|---|
. |
Progress
Area of Interest | Details |
---|---|
LexEVS |
|
Report Writer |
|
Term Browser | Scheduled a meeting for January 10th to discuss the Value Set hierarchy design. This is the item to work out until we can deploy to 2.12. Explored methodologies for converting XML formatted mapping file to RDF. |
NCIm Browser | Scheduled to meet with user group in January to discuss future search options including searching by specific sources. |
Term Suggestion Application | 508 scan came back at 100% compliant. |
EVS REST API | Small issue on DEV and QA not returning results. Issue was resolved by the systems team. |
Biomarkers Support |
|
SPARQL Report Writer | Continued development of the UI. Development on schedule to complete mid January |
Other Support |
|
JIRA Issues
Issue Number | Description | Status |
---|---|---|
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 |
---|---|---|
. | ||