Attendees
| Name | Role | Present |
|---|---|---|
| Wright, Larry | NIH/NCI | x |
| Fragoso, Gilberto | NIH/NCI | |
De Coronado, Sherri | NIH/NCI | x |
Safran, Tracy | NIH/NCI | x |
| Ong, Kim L | IS | x |
| Lucas, Jason R | IS | x |
| Bauer, Scott | Mayo | x |
| Stancl, Craig | Mayo | x |
| Endle, Cory | Mayo | x |
| Wynne, Robert | NIH/NCI | x |
| Tran, Tin | NIH/NCI [C] | x |
| Carlsen, Brian | (NIH/NCI) [C] | x |
| Wong, Joanne | ||
Kuntipuram, Kumar | x |
Action Items
| # | Assigned | Description | Date Identified | Due Date | Date Completed | Status |
|---|---|---|---|---|---|---|
| 64 | Scott | To follow up on URI's on OWL2 with Harold. | on hold | |||
| 164 | Cory | Cory to add implementation to CTS2 implementations page. | 2014.04.30 | on hold | ||
| 197 | Scott | Do a gap analysis on what the URI_Resolver logs and what NCI would like to know from these logs | 2014.6.18 | on hold | ||
| 200 | Larry/Sherry | Query current LexEVS users about use of SOAP, REST or QBE services in the legacy caCORE api's | 2014.6.18 | on hold | ||
| 207 | Cory | Write issue against CTS2 OMG regarding the ability to return INACTIVE concepts only. | 2014.07.30 | on hold | ||
| 210 | Larry/Gilberto | Determine if there is a need to meet with the CTRP | 2014.07.30 | on hold | ||
| 212 | Larry | Include LexGrid XML Export as part of the 5.1 retirement notice. | 2014.07.30 | on hold | ||
| 224 | Scott | URI Resolver - Provide overview of how to access the URI Resolver | 2014.09.03 | on hold | ||
| 225 | Scott | URI Resolver - Look at TLAMP and VSAC service to determine usage of URI Resolver | 2014.09.03 | on hold | ||
| 244 | Craig | Plan meeting with Tracy to discuss collaborative LexEVS development process | 2014.12.03 | on hold | ||
| 281 | Scott | Try to replicate what CTRP did to break our service (retrieve a tree through CTS2). | 2015.03.25 | on hold | ||
| 282 | Mayo Team | Look into implementing graph node in CTS2 for the path to root method (and path to leaf). | 2015.03.25 | on hold | ||
| 287 | Scott | Determine estimates for tree extension, mapping extension, and OWL2 fixes to be considered for 6.3. | 2015.04.08 | done | ||
| 288 | Gilberto | Follow up on the possibility of obtaining a license for the JIRA Capacity plugin (project portfolio management plugin) | 2015.04.08 | open | ||
| 289 | Craig/Cory | Complete the LexEVS 6.3 ARC document. | 2015.04.15 | done | ||
| 290 | Craig | Create JIRA item for Tree Extension Code Merge to LexEVS repository for 6.3 release | 2015.04.22 | done |
Progress
| Scott |
|
| Cory |
|
| Craig |
|
Agenda
| Sprint Status | Review Sprint 3 (finished)
|
| Sprint 4 Planning / Roadmap impact | Sprint 4 Overview
|
| Sprint Planning | Issue Grooming
|
LexEVS 6.3 logistics | Will LexEVS 6.2 persist once 6.3 is deployed? Goal is to move to the most recent service (6.3). CaDSR is testing LexEVS 6.2 (not complete) CTPR will need to test yet. Tracy mentioned that there are not many users on LexEVS 6.2 yet. The TERMS browser will need to test on 6.3 to make sure it works as expected. The plan then is to reuse the 6.2 containers and URLs for LexEVS 6.3. |
| ARC Meeting Update | LexEVS 6.3 and the CTS2 API documentation service ARC meeting went well. We need to create a PTE for the CTS2 API documentation service. |
| Design and Architecture Review Meeting Planning | Schedule for Thursday or Friday Larry will set up a meeting for Friday. |
| Next Release Planning - 6.4 or 7.0? | The question arose because Lucene is a large feature change, but the LexEVS API will not change. If we don't implement all of the search algorithms, then that could be an API change.
The suggestion is to go with 6.4 so external users wouldn't be concerned about large changes. |
| JIRA item - Sorting for Tree Hierarchy | Extraneous roots issue - we haven't been able to replicate here. Scott thought there was an additional request to sort the results. Kim confirmed this was not the case and there was nothing more to be done. As long as we don't break the current behavior, there is no concern. |
| JIRA item - RRF Loader resolution | A new JIRA item was created to capture the need to clean up the RRF loader (as per LEXEVS-879). This issue was discussed and it will be placed in the backlog until it is prioritized for a future release. |
| Tree Extension Code Merge to LexEVS repository discussion | This would tie the tree extension to a specific version of LexEVS. The tree extension usually needs to stay in sync with LexEVS change anyway. The overall conclusion is to pull the tree extension into the LexEVS code base within Git. TODO: Create a JIRA item and add this to the 6.3 release. |
JIRA Plugin - Update from Gilberto | Gilberto will be back next week to discuss. |
JIRA Issues
Recent LexEVS Related Bugs and Features (within last week)
Recent CTS2 Service Related Issues (within last week)
6.4 LexEVS Related Issues
6.4 CTS2 Service Related Issues
Project Plan Changes
| # | Description | Due Date | Resources | Notes | Risks | Mitigation |
|---|---|---|---|---|---|---|
| None | ||||||
Planned Activities
| Area of Interest | Details |
|---|---|
Risks, Issues, Dependencies
Risks
| # | Opened Date | Due Date | Description | Likelihood (H, M, L) | Impact | Assigned | Status | Mitigation Strategy |
|---|---|---|---|---|---|---|---|---|
Issues
| # | Opened Date | Description | Impact | Assigned | Status |
|---|---|---|---|---|---|
Dependencies
| Opened Date | Description | Assigned |
|---|---|---|
