Attendees
Name | Role | Present |
---|---|---|
Wright, Larry | NIH/NCI | x |
Fragoso, Gilberto | NIH/NCI | x |
De Coronado, Sherri | NIH/NCI | |
Safran, Tracy | NIH/NCI | |
Ong, Kim L | IS | x |
Lucas, Jason R | IS | x |
Bauer, Scott | Mayo | x |
Stancl, Craig | Mayo | x |
Endle, Cory | Mayo | x |
Peterson, Kevin | Mayo | |
Wynne, Robert | NIH/NCI | x |
Pan, JJ | NIH/NCI [E] | Removed |
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 |
---|---|---|---|---|---|---|
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 | ||
185 | Gilberto | Create Jira for OWL 2 Annotation issue in the API. | 2014.05.28 | 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 | ||
237 | Scott | Final code deliverables posted to SFTP site and wiki pages updated. | 2014.10.02 | done | ||
244 | Craig | Plan meeting with Tracy to discuss collaborative LexEVS development process | 2014.12.03 | open | ||
245 | Kim/NCI | Confirm that the manifest and Tree Jar that Scott put on sftp will work. | 2014.12.10 | done | ||
246 | Cory | Investigate if possible to use Apache as a proxy for NodeJS (if an issue with security appscan) | 2014.12.10 | on hold | ||
253 | Scott | LexEVS 6.2 sftp site to be updated with 6.2 related Jars | 2015.01.07 | done | ||
254 | Tracy/Rob | EVS download page to be updated for 6.2. | 2015.01.07 | open | ||
255 | Scott | LexEVS 6.2 download page to be updated to point to the sftp site. | 2015.01.07 | done | ||
256 | Gilberto | Complete OWL 2 review by Wednesday, January 14 | 2015.01.07 | done | ||
257 | Scott | Meet with Gilberto to discuss OWL 2 duplicate relationships. | 2015.01.07 | done | ||
259 | Scott/Cory/Kevin | Verify that all distributed interfaces that are exposed are surfaced. | 2015.01.14 | open | ||
260 | Craig | Update 6.3 plan to remove deployment tasks. | 2015.01.21 | open | ||
261 | Cory | Install Node.js on informatics and host the 6.2 CTS2 API documentation on Informatics. | 2015.01.21 | open |
Progress
Immediate Priorities and Problems (Mayo Team) | Scott:
Cory:
Kevin:
Craig: Project Plan for 6.3 and 6.4
|
6.3 release planning, (Craig) | Confirm tagging and deploying to Dev
Deployment of Node.JS (so we can point to 6.2 services)
|
Tree Evaluation – Feedback | Nothing |
Shady Grove Deployment | Questions about DNS naming conventions.
|
OWL2 Changes | Discussed the list of fixes (captured in spreadsheet) and those will be added to JIRA. Gilberto and Larry discussed and there are additional things to be considered in the near term. Would like to cover all the main features in the 6.3 timeframe. In the spreadsheet, the 5 (high priority) will be done first and continue down until 1. Scott and Gilberto will need to have further discussions. This effort will push out schedules (6.4). |
Distributed Interfaces | Kim identified "Sorting the mapping table" as a problem. Mayo team to review. NCI team would point the term browser to the remote API to see if anything is broke. |
Deployment Automation | It was discussed that we should not depend on anthill pro. Scott suggests that automation be for individual services (not one for all). There are some projects at NCI that uses Jenkins. In house deployment - lengthy process, often doesn't go quite right. If we could automate, then more frequent updates to make things available. Warren has been pushing this moving forward. Mayo team to discuss - when would it make sense to tackle this and start planning. |
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 |
---|---|---|