Attendees
Name | Role | Present |
---|---|---|
Wright, Larry | NIH/NCI | x |
Fragoso, Gilberto | NIH/NCI | x |
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 | |
Pan, JJ | NIH/NCI [E] | 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 |
---|---|---|---|---|---|---|
64 | Scott | To follow up on URI's on OWL2 with Harold. | on hold | |||
156 | Scott | Scott to work with Gilberto to determine what is needed for OWL 2 requirements | 2014.04.30 | on hold | ||
164 | Cory | Cory to add implementation to CTS2 implementations page. | 2014.04.30 | on hold | ||
170 | Scott | Update the ARC dates to include range of dates for each tier. | 2014.05.14 | 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 | ||
209 | Craig/Larry | Plan Techical F2F/AMIA meetings. | 2014.07.30 | done | ||
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 | ||
235 | Mayo/NCI Team | Identify additional value set JIRA items to be included in 6.3 release. | 2014.10.02 | on hold | ||
237 | Scott | Final code deliverables posted to SFTP site and wiki pages updated. | 2014.10.02 | on hold | ||
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 | open | ||
246 | Cory | Investigate if possible to use Apache as a proxy for NodeJS | 2014.12.10 | open | ||
247 | Gilberto | Gilberto to follow up with NCI security team about the use of NodeJS. | 2014.12.10 | done | ||
248 | Cory | Look at alternative API documentation tools. | 2014.12.10 | done | ||
249 | Cory | Follow up with Tracy about the CTS2 landing page (configuration file) | 2014.12.10 | done | ||
250 | Craig/Larry | Cancel Dec 24 and Dec 31 meetings. | 2014.12.10 | done | ||
251 | Cory | Install NodeJS on NCI server. | 2014.12.17 | open | ||
251 | Craig | Update 6.3 project plan to include 6.2 release activities. | 2014.12.17 | open | ||
Progress
Immediate Priorities and Problems (Mayo Team) | Scott: OWL2
Planned Lucene discussion on Friday with Kevin. Cory: API Documentation, Informatics update
Craig: Project Plan for 6.3 and 6.4.
|
JIRA items feedback: Resume Batch JIRA 601 |
|
Tree Evaluation – Feedback | Kim will need to provide feedback. |
CTS2 API documentation | Possible hosting options - host on NCI or on external system (informatics). One suggestion was to have service on NCI and then point to another server with the content. Only concern would be the cross-site scripting (and associated filters). Plan - deploy Node js service on NCI and have it appscan'ed. Once confirmed, then we can then move onto providing the content on another server, etc. |
Shady Grove Deployment | Approaching the final steps in deployment. Once data and FW exceptions in place, then start with the browsers. Need to see how 6.2 will run on Shady Grove. Once verified, announce available for testing. Once confirmed, then point to the 6.2 services. Anticipated late December/early January. Once complete, will no longer need to update 6.1 data. Team will need to update release notes, artifacts. (~ mid-late January). Public announcement in mid-late January. Needs to be reflected in the 6.3 project plan. TODO It was discussed that 6.3 could be deployed over 6.2 deployment. Only concern is column widths. |
Automation Meeting | Scheduled on Friday at 10:30-11:30AM EST. |
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 |
---|---|---|