Attendees
Name | Role | Present |
---|---|---|
Wright, Larry | NIH/NCI | x |
Fragoso, Gilberto | NIH/NCI | |
De Coronado, Sherri | NIH/NCI | x |
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 | |
Wynne, Robert | NIH/NCI | |
Pan, JJ | NIH/NCI [E] | x |
Tran, Tin | NIH/NCI [C] | x |
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. | done | |||
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 | open | ||
192 | Scott | Investigate logging or monitoring capabilities of URL Resolver | 2014.6.11 | done | ||
195 | Craig | Update Project Plan with performance testing tasks | 2014.6.11 | done | ||
196 | Jason | To discuss Agile fit and questions with counter part | 2014.6.18 | done | ||
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 | ||
198 | Scott | Look into whether git or github can fork from a fork | 2014.6.18 | done | ||
199 | Scott | Ask Ann Wiley to create a sticky for the VKC forum directing users to post to appropriate gitHub | 2014.6.18 | open | ||
200 | Larry/Sherry | Query current LexEVS users about use of SOAP, REST or QBE services in the legacy caCORE api's | 2014.6.18 | open | ||
201 | Scott | caCORE Inquiry - Outline the services that exist and what is proposed to be dropped. | 2014.06.25 | open |
Progress
Immediate Priorities and Problems (Mayo Team) | Scott: Tomcat verification testing, Loader testing against 5.5, Lucene Review.
Cory: Start JIRA Items Craig: Project Plan Updates |
| |
Agile adoption Schedule | Reviewed questions and concerns. Will plan on putting together presentation to present to our group. "How to get started with Agile" to be addressed during this presentation. | ||
caDSR and Value Set and other URIs (Weekly Status) | Report on URI Resolver logging. Need priority for this. Requirements specified. Need to be able to prioritize when to get this completed. Estimated 2 days of effort. Continue working on Lucene and then prioritize this work with the schedule Jira items. | ||
Dev DRT request | Requested ARC document. Larry updated ARC document with additional tier dates. Target is Shady Grove (not 6116). | ||
GitHub, build workflow | http://stackoverflow.com/questions/6675994/is-it-possible-to-fork-a-fork-in-github Report from Scott on fork. "Forking from a fork" - officially, you cannot. However, it may be possible, but things will not work correctly. Suggests that Master be LexEVS channel. Need to discuss with Gilberto. | ||
Forum Links on GitHub (Scott) | Scott spoke to Ann W. Ann suggested submitting a request to the helpdesk (needs access). | ||
Plans for the future of caCORE webservices. | Update (Larry or Sherri) Larry can send note via listserves, but want to start with more internal/smaller group. Need to outline the services that exist and what is proposed to be dropped. TODO: Scott Based on feedback, will learn how to address to a broader group. | ||
Update on Value Set Client services (Craig) | Looking at the issues with the NLM team. Cory to work on this during the next week. | ||
AMIA discussion (Craig) | AMIA poster accepted - few updates needed. |
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 |
---|---|---|