Attendees
Name | Role |
---|---|
Action Items
# | Assigned | Description | Date Identified | Due Date | Date Completed | Status |
---|---|---|---|---|---|---|
. |
Progress
Area of Interest | Details |
---|---|
LexEVS | Working on a schedule for participation of the browser testing of the 6.4 LexEVS API. Anticipating getting a release in February that will include the search extensions. |
Report Writer |
|
Term Browser | Currently working on the 2.8 release development. |
Term Suggestion Application | |
NCIm Browser | |
Triple Store Prototype | Working on the deployment of a Triple Store prototype using Apache Jena. A customer managed VM has been allocated to us. |
JIRA Issues
Issue Number | Description | Status |
---|---|---|
NCITERM-691 | View In Hierarchy tree node expand/collapse issue. | Performed trouble shooting on the tree-node expansion failure issue |
Schedule Changes
# | Description | Due Date | Resources | Notes | Risks | Mitigation |
---|---|---|---|---|---|---|
Planned Activities
Area of Interest | Details |
---|---|
Term Browser 2.8 Release | Finalize scope and schedule and start development on the 2.8 release and start development. |
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 |
---|---|---|
. | ||