Attendees
| Name | Role | Present |
|---|---|---|
| Wright, Larry | NIH/NCI | |
| Fragoso, Gilberto | NIH/NCI | x |
De Coronado, Sherri | NIH/NCI | x |
Safran, Tracy | NIH/NCI | |
| Ong, Kim L | IS | x |
| Lucas, Jason R | IS | x |
| Bauer, Scott | Mayo | x |
| Stancl, Craig | Mayo | |
| Endle, Cory | Mayo | |
| Wynne, Robert | NIH/NCI | x |
| Tran, Tin | NIH/NCI [C] | x |
| Carlsen, Brian | (NIH/NCI) [C] | |
| Wong, Joanne | ||
Kuntipuram, Kumar | x |
Action Items
| # | Assigned | Description | Date Identified | Due Date | Date Completed | Status |
|---|---|---|---|---|---|---|
| 293 | Jason | Check into Mayo being designated a trusted site | 2015.06.03 | done |
Progress
| Scott |
|
| Cory |
|
| Craig |
|
Agenda
| Sprint Status | Current Sprint - Sprint 14 (September 17, 2015 - September 30, 2015) LexEVS S13-500 Agile Development - Sprint Status#SprintStatus-Sprint14
Current implementation allows queries on the same field for a given entity spread over a range of documents. Boolean query under the covers provides search on single entity rather than individual documents provides a finer set of returned values. This needs re-implementation in the current version. |
VPN and network evaluation | |
| Horizontal Coding Scheme searches | Future implementation. Currently multiple namespaces can exist in the terminology. NCI Thesaurus has relations between branches such as roles between diseases and genes. Use case requires possible modeling within the coding scheme. Create a role within NCIt that connects with an entity in GO. Need a place holder namespace and should we be able to navigate across coding scheme to target of navigation to named entity. Suggestion: feature request. Should have the ability to determine whether or not crossing boundaries of coding schemes is a possible. This might be allowed or not based on a determination in a preferences file. |
| Face-Face Planning | |
| CTS2 | One client should be able to connect to multiple instances of a service. Can one endpoint provide data to query against another? How can CTS2 be used in a manner that provides uri's that are not a part of the local resources. Possible face to face topic. |
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 |
|---|---|---|
Action Item Backlog
| # | 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 |
