Attendees
| Name | Role | Present |
|---|---|---|
| Wright, Larry | NIH/NCI | |
| Fragoso, Gilberto | NIH/NCI | |
De Coronado, Sherri | NIH/NCI | |
Safran, Tracy | NIH/NCI | |
| Ong, Kim L | IS | |
| Lucas, Jason R | IS | |
| Bauer, Scott | Mayo | |
| Stancl, Craig | Mayo | |
| Endle, Cory | Mayo | |
| Wynne, Robert | NIH/NCI | |
| Pan, JJ | NIH/NCI [E] | |
| Tran, Tin | NIH/NCI [C] | |
| Ahmed, Shamim | NIH/NC [C] | |
| Haber, Margaret | (NIH/NCI) | |
| Roth, Laura | (NIH/NLM) | |
| Ramani, Vivek | (NIH/NCI) [C] | |
| Carlsen, Brian | (NIH/NCI) [C] | |
| Wong, Joanne | ||
Kuntipuram, Kumar |
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 | |||
| 154 | Larry | Provide an email update to NCBO, NLM, and Mayo with current activities and what has been built. | open | |||
| 155 | Kumar | Verify that funds can be extended through Oct. | 2014.04.30 | 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 | open | ||
| 185 | Gilberto | Create Jira for OWL 2 Annotation issue in the API. | 2014.05.28 | open | ||
| 192 | Scott | Capture issues with Agile we may have | 2014.6.11 | done | ||
| 192 | Scott | Investigate logging or monitoring capabilities of URL Resolver | 2014.6.11 | open | ||
| 193 | Craig | Send out updated Project Plan | 2014.6.11 | done | ||
| 194 | Craig/Scott | Send a list of Known Common Value Set Client issues to Larry | 2014.6.11 | done | ||
| 195 | Craig | Update Project Plan with performance testing tasks | 2014.6.11 | open |
Progress
| Gforge retirement | |||
| Immediate Priorities and Problems (Mayo Team) | Scott: Tomcat verification testing, Loader testing agianst 5.5, Responding to requests around REST API Cory: Out Craig: Project Plan Updates |
| |
| Goals and performance document (Larry) | This performance will need to be included in the project plan - include creating performance profiles of 6.2 on DEV hardware on Shady Grove and then evaluate performance at that point and determine what else would need to be done. Additional work would need to be prioritized against the currently planned tasks at that time. | ||
| Agile adoption Schedule | Discuss issues and plan for any training/adoption framework | ||
| caDSR and Value Set and other URIs (Weekly Status) | Report on URI Resolver logging (Scott) | ||
| Dev DRT request | Update | ||
| GitHub, build workflow | |||
| Forum Links on GitHub (Scott) | Recently received a forum posting from the old VKC forum. Realized the readme was linking users to the VKC forum. We can fix the readme, but now that we need to modify the files and push to NCIP channel, we need to figure out how we would make the change and push to both channels. |
JIRA Issues
| Description |
|---|
| LEXEVS-570 - Getting issue details... STATUS |
| LEXEVS-573 - Getting issue details... STATUS |
| LEXEVS-579 - Getting issue details... STATUS |
| LEXEVS-586 - Getting issue details... STATUS |
| LEXEVS-594 - Getting issue details... STATUS |
| LEXEVS-597 - Getting issue details... STATUS |
| LEXEVS-598 - Getting issue details... STATUS |
| LEXEVS-599 - Getting issue details... STATUS |
| LEXEVS-605 - Getting issue details... STATUS |
| LEXEVS-606 - Getting issue details... STATUS |
| LEXEVS-607 - Getting issue details... STATUS |
| LEXEVS-608 - Getting issue details... STATUS |
| LEXEVS-609 - Getting issue details... STATUS |
| LEXEVS-612 - Getting issue details... STATUS |
| LEXEVS-613 - Getting issue details... STATUS |
| LEXEVS-615 - Getting issue details... STATUS |
| LEXEVS-616 - Getting issue details... STATUS |
| LEXEVS-617 - Getting issue details... STATUS |
| LEXEVS-618 - Getting issue details... STATUS |
| LEXEVS-619 - Getting issue details... STATUS |
| LEXEVS-620 - Getting issue details... STATUS |
| LEXEVS-621 - Getting issue details... STATUS |
| LEXEVS-622 - Getting issue details... STATUS |
| LEXEVS-623 - Getting issue details... STATUS |
| LEXEVSCTS2-2 - Getting issue details... STATUS |
| LEXEVSCTS2-3 - Getting issue details... STATUS |
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 |
|---|---|---|
