Attendees
| Name | Role |
|---|---|
Action Items
| # | Assigned | Description | Date Identified | Due Date | Date Completed | Status |
|---|---|---|---|---|---|---|
| . |
Progress
| Area of Interest | Details |
|---|---|
| LexEVS | The testable LexEVS 6.4 release should be available in 2 weeks. We are hoping to have the Term Browser 2.8 released in time so that there is no delay in the LexEVS 6.4 deployment to DEV. |
| Report Writer |
|
| Term Browser | Provided a tag for the 2.8 Term Browser release to QA. QA team is currently verifying the trackers and I believe was going to start the automated tests. QA team was having some issue with the automated test generation and will work with Kim to resolve. Looking at the possible 2.9 scope items. |
| Term Suggestion Application | |
| NCIm Browser | |
| Triple Store Prototype | Made some updates to the simple and advanced search capabilities. Looking at some additional technologies for tree view and indexing of triple store. |
JIRA Issues
| Issue Number | Description | Status |
|---|---|---|
| NCITERM-703 | OWL2 Qualifiers Display. | Added a configuration parameter, owl_role_quantifiers, to the project.properties configuration file. The syntax is:
Modified the backend code to show or hide property qualifiers and association qualifiers based on the value of the owl_role_quantifiers configuration parameter defined above. Started to review additional comments received from the user group. Tested the generation of automated selenium UI Junit test class, TestTermBrowserTestCase.java. Ran the Junit test and found that the View In Hierarchy function for OBO formatted coding schemes and NPO are still failing |
Schedule Changes
| # | Description | Due Date | Resources | Notes | Risks | Mitigation |
|---|---|---|---|---|---|---|
Planned Activities
| Area of Interest | Details |
|---|---|
| Term Browser 2.8 Release | Continue development of the 2.8 Term Browser release. |
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 |
|---|---|---|
| . | ||
