Attendees
| Name | Role | Present |
|---|---|---|
| Wright, Larry | NIH/NCI | x |
| Fragoso, Gilberto | NIH/NCI | x |
De Coronado, Sherri | NIH/NCI | x |
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 |
| Wynne, Robert | NIH/NCI [C] | x |
| Tran, Tin | NIH/NCI [C] | x |
| Carlsen, Brian | NIH/NCI [C] | |
| Wong, Joanne | NIH/NCI [C] | |
Kuntipuram, Kumar | NIH/NCI [C] |
Action Items
| Assigned | Description | Date Identified | Due Date | Date Completed | Status |
|---|---|---|---|---|---|
| Craig/Larry | Follow up with Jose (CTRP) in January 2016 to see if we can assist them and understand their requirements. | 2015.12.16 | 2016.01.31 | Open | |
| Scott/Cory | Determine if LEXEVS-1516 (Value Sets) issue is a LexEVS issue or not. | 2016.01.13 | 2016.01.31 | 2016.01.20 | Done |
| Scott | Request additional support from Mark about the the VPN issues. | 2016.01.13 | 2016.01.31 | 2016.01.22 | Done |
| Scott | Follow up with CaDSR team to see if they still have lucene questions. | 2016.01.13 | 2016.01.31 |
Progress
| Scott |
|
| Cory |
|
| Craig |
|
Agenda
| Sprint Status | Current Sprint - Sprint 22 ( January 21, 2016 – February 03, 2016 ) LexEVS S13-500 Agile Development - Sprint Status#SprintStatus-Sprint22 |
| Sprint Planning | Issue Prioritization Recent LexEVS Related Bugs and Features (within last week)
Recent CTS2 Service Related Issues (within last week)
Issue Grooming Prioritize JIRA issues (fix version 6.4)
|
CTRP Planning
| No updates from Sherri. Gilberto was at CTRP's demo on Monday for their requirements. He mentioned that there were no LexEVS requirements at this time. Sherri was wondering if there are any requirements for LexEVS. Larry commented that there were no requirements for us at this time. Larry will send a note to Jose to see if they have any requirements for LexEVS. |
Value Set Resolution LEXEVS-1516 - Getting issue details... STATUS | The properties file for the browser was missing the cache and max value properties. This properties file needs to be propagated from from DATA_QA to PROD to fix this issues. Rob will update the this JIRA issue with this information. |
6.4 Performance testing LEXEVS-1527 - Getting issue details... STATUS Ability to get and load all of the value sets | Tracy put the NCI value sets out on the SFTP site for Scott. Scott will load these value sets on our DEV system. Scott will be using Java JMH performance harness for performance testing of reading all of these value sets. This will show the difference between the multi index performance and the single index performance. |
Search Extension Testing Requirements | This what is used for text searching. We will want to focus our testing on the text searching performance. Jason mentioned they will test the 6.4 artifacts with the browser scripts. |
| Nexxus Testing | Scott will be testing the Nexxus upgrade on the Wednesday, 2016.02.03. |
Production Remote Service not accessible
| Scott is waiting to get the PROD logs to investigate further. Tracy will send the logs to Scott. |
6.4 Artifacts | We have sprint 21 artifacts available for 6.4. This release has the search extension features working. Scott/Cory will install this on the NCI DEV system. |
| 6.3.0.2 Testing Update | NCI will test and let us know their findings. |
| LexEVS External Users | No updates. |
Namespace Navigation between coding schemes
| Gilberto wanted to review way this namespace navigation works between coding schemes. The way it is implemented, we can go across coding schemes. Scott mentioned that there are limitations based on the namespaces. If there are two coding schemes with the same namespace, this is not supported. If there are multiple versions of the coding scheme, it will go to the PRODUCTION version. Scott suggested that Gilberto should come up with a scenario and then we can create a manifest to show how it can be supported. Gilberto suggested that they will test with OBI and NBO. |
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 |
