 |
Page History
...
| Name | Role | Present |
|---|---|---|
| Wright, Larry | NIH/NCI | x |
| Fragoso, Gilberto | NIH/NCI | x |
De Coronado, Sherri | NIH/NCI | |
Safran, Tracy | NIH/NCI [C] | x |
| Ong, Kim L | IS | x |
| Lucas, Jason R | IS | x |
| Bauer, Scott | Mayo | x |
| Stancl, Craig | Mayo | x |
| Endle, Cory | Mayo | x |
| Sharma, Deepak | Mayo | x |
| Wynne, Robert | NIH/NCI [C] | x |
| Tran, Tin | NIH/NCI [C] | x |
| Carlsen, Brian | NIH/NCI [C] | x |
| Wong, Joanne | NIH/NCI [C] | |
Kuntipuram, Kumar | NIH/NCI [C] | x |
Action Items
| Assigned | Description | Date Identified | Due Date | Date Completed | Status | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Rob | Close issue
| 2016.02.09 | 2016.04.10 | Open | |||||||||||
| Cory | Create JIRA issue to update CTS2 service to use Apache Commons Collections Version 3.2.1 (security issue)
| 2016.03.09 | 2016.08.30 | 2016.07.28 | Done | ||||||||||
| Cory | Create JIRA issue to remove caCore legacy code
| 2016.04.20 | 2016.08.30 | 2016.07.28 | Done |
...
Sprint Status
| Current Sprint - Sprint 35 (July 21, 2016 – August 3, 2016) LexEVS 6.4 S13-500 Agile Development - Sprint StatusStatus#SprintStatus-Sprint35 Tracy is working on Data deployment to DEV and QA The indexes were created on DEV. These indexes will need to be propagated to QA. Tracy will be doing this move. We closed out Sprint 35. Tasks associated to the 6.4 release have been closed. We will create a build that has the OWL2 loader changes. This will be done in the next sprint | ||||||||||||
QA Tier Status
| Jacob is assigned these tasks and is working on them. | ||||||||||||
OWL2 Discussion
| LEXEVS-1299 - Scott asked if these properties belong in the system as supported properties?
LEXEVS-1976 - Scott suggested the preferences could be updated for this.
LEXEVS-1160 - Scott suggested that the browser should add logic to determine what to display.
| ||||||||||||
OWL2 Loader build
| TODO: Cory/Scott will create a build with the OWL2 loader enhancements in the next sprint. | ||||||||||||
LexEVS using HTTPs - December 31st, 2016 deadline
| There is an NCI department level requirement that all services need to use HTTPs. If they don't, the current services will be shutdown at the end of December. We don't want to force end users to migrate to 6.5, if that had the HTTPs fix in it by the end of the year. Larry suggested that we need to upgrade the existing LexEVS 6.3 and/or 6.4 to use HTTPs prior to the end of the year. If LexEVS 6.3 was updated and the end user clients have to rebuild their clients, then we should just consider upgrading the clients to the LexEVS 6.4/6.5 The Mayo team will start to investigate and discuss with the NCI systems team. | ||||||||||||
LexEVS versions - Previous/Deprecated/Retired | LexEVS 6.3 should be moved to deprecated. Remove the "Previous" section. TODO: Cory will make these changes. | ||||||||||||
LexEVS Remote API and LexEVS service (CTS2) have been deployed to QA. Larry approved the test plan. Tin will start the testing on QA. Next, the AppScan will be submitted. | |||||||||||||
LexEVS using HTTPs - Update
| Remote API - the client will need to change based on SSL changes. Because the Remote API client will need to change, we decided to not update LexEVS 6.3. Instead, we will add the HTTPs ability to LexEVS 6.4 and not LexEVS 6.3. TODO: Cory will need to add a warning message that Remote clients will need to use SSL. This should be added the notes about how to upgrade from LexEVS 6.4 to LexEVS 6.4.
| ||||||||||||
| Java 8 and Spring 4 update - not needed | We have found that the current versions of Java 8 and our current Spring 2.x are building and testing with one issue with CTS2. Deepak will investigate further. Deepak is using Java 8.92 in the Docker system test scripts. LexEVS is running Spring 2.x. At some point this should be updated to Spring 4. Larry suggested the Mayo team should investigate the quickest path to getting the Remote API set up for HTTPs. Tracy suggested that we have an HTTPs fix by the end of August. The Mayo team will investigate to see if this is possible. At this point we will not upgrade to Spring 4. Priority for upgrades (in this order): HTTPs, CentOS 7, Java 8. LexEVS 6.4.0 testing will continue and will be pushed up the tiers. We will put the HTTPs changes only into LexEVS 6.4.1. No Java upgrade. Jacob/Tracy/Sarah can be contacted for configuration on DEV TODO: We need to get an announcement on this change to users as soon as we understand the impact and the wiki updated for this. | ||||||||||||
| Data issues on Prod | This has been discussed and there is a plan is in place. | ||||||||||||
| 6.5 Planning | Craig will explain the changes in detail next week when the board is completed |
| Based on the investigation from Cory, the field is a VARCHAR (250). We can increase the length to accommodate a longer description. Larry suggested increasing the length to 1000. Tracy agreed with this. TODO: Cory will send out an email to confirm everyone agrees with the suggestion from Larry. | ||||||||||
LexEVS External Users
| Brian added a couple comments to the issue. Scott will follow up with some additional suggestions We think this may be a source issue - loading from RRF. Brian will look into this issue. | ||||||||||||
| Team Absences | Mayo Team
|
JIRA Issues
Recent LexEVS Related Bugs and Features (within last week)
...
