Attendees
| Name | Role | Present |
|---|---|---|
| Wright, Larry | NIH/NCI | |
| Fragoso, Gilberto | NIH/NCI | x |
De Coronado, Sherri | NIH/NCI | |
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 | |
| Tran, Tin | NIH/NCI [C] | x |
| Carlsen, Brian | (NIH/NCI) [C] | |
| Wong, Joanne | ||
Kuntipuram, Kumar | ||
| Liu, Sichen |
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 | open | ||
| 246 | Cory | Investigate if possible to use Apache as a proxy for NodeJS (if an issue with security appscan) | 2014.12.10 | on hold | ||
| 264 | Rob | Update download links once code on NCIP Channel | 2015.01.28 | open | ||
| 266 | Craig | Set up Lucene Search Review | 2015.02.18 | open | ||
| 281 | Scott | Try to replicate what CTRP did to break our service (retrieve a tree through CTS2). | 2015.03.25 | open | ||
| 282 | Mayo Team | Look into implementing graph node in CTS2 for the path to root method (and path to leaf). | 2015.03.25 | open | ||
| 283 | Craig | Discuss what it means to deploy 6.3 to PROD at our next meeting (4/8/2015). | 2015.03.25 | open | ||
| 284 | Craig/Cory | Create the Architecture document for the CTS2 API service. | 2015.04.01 | open | ||
| 285 | Scott | Create a new JIRA item to capture issue investigate for LEXEVS-828 | 2015.04.01 | open | ||
| 286 | Scott | Create a JIRA issue for the issue Kim found with the tree extension (path to root and namespace). | 2015.04.01 | open |
Progress
| Scott |
|
| Cory |
|
| Craig |
|
Agenda
| API Doc | TODO: Craig/Cory to get Arc. document template and fill out. Jason to set up a meeting after an Arc. document is done. Currently deployed at https://lexevscts2.herokuapp.com/cts2 |
| 6.3 Deployment | Browser may need 6.3 features sooner than 6.4 would be deployed. We will discuss further next week when everyone is present. |
| Lucene and Agile process | Currently on Sprint 2. Reviewed the agile sprint 2 board with the group. https://tracker.nci.nih.gov/secure/RapidBoard.jspa?rapidView=220 The project roadmap is available here: |
| Scott has investigated this mapping extension issue. Junit that is failing addresses this problem that the iterator is working properly. TODO: Scott to create a new JIRA item to capture this issue and what the fix could be. This is a 6.3 issue. |
Mayo Security initiative - binary code review (similar to Jenkins) | Mayo has a toolset to scan code for security concerns. It may be possible to run LexEVS binaries through our security scan. This is a static analyzer for the binary code. The dynamic analyzer is available to hit the end REST services. Mayo team will meet with the security team to start this process. |
| Tree extension issue (Kim) | Trying to find the path to root. Namespace was the same, the NPO boundary was brought in. TODO: Scott to create a JIRA issue and place in the backlog. |
JIRA Issues
Recent LexEVS Related Issues (within last week)
Recent CTS2 Service Related Issues (within last week)
6.3 LexEVS Related Issues
6.3 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 |
|---|---|---|
