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 | x |
Pan, JJ | NIH/NCI [E] | x |
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 | x | |
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 | |||
136 | Scott | Point the CTS2 API page to PROD (wiki) - originally planned on Stage, but now planning on PROD. | done | |||
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 | open | ||
156 | Scott | Scott to work with Gilberto to determine what is needed for OWL 2 requirements | 2014.04.30 | open | ||
157 | Craig | Include the value set and namespace tacks back into plan (in case we do have time or extension) | 2014.04.30 | open | ||
158 | Jason | Jason to send note to Michael and Jacob (include Scott) to understand what the work around is for Struts | 2014.04.30 | open | ||
159 | Tracy/Scott | Tracy/Scott to provide example for UMLS problem and send that on to Alameda team. | 2014.04.30 | open | ||
160 | Scott | Scott to submit feature request to expand value set definitions (requires a model change). | 2014.04.30 | done | ||
161 | Cory | Add service information to include links (rest calls). | 2014.04.30 | open | ||
162 | Cory/Craig | Talk with Kevin about NCBO and what is exposed via value set client. | 2014.04.30 | done | ||
163 | Craig | Jason has dependencies so Craig to work with Jason on plans and will update and send out to the group. | 2014.04.30 | open | ||
164 | Cory | Cory to add implementation to CTS2 implementations page. | 2014.04.30 | open |
Progress
Immediate Priorities and Problems (Mayo Team) | Scott: MySQL 5.5 update, max clause count error on phrase, Lucene cleanup failure, failure of value sets to resolve on informatics
Cory: CTS2 Client UI
Craig: Project Plan Updates
|
| |
Struts update 2.3.16.2 |
| ||
caDSR and Value Set and other URIs (Weekly Status) | Term browser and other API places URI's are adhoc. Discussion continuing with caDSR. What is the format and requirements. A couple of choices – domain either NCI or Purl. What follows would be /valueset/<Identifier> Identifier would be from the NCIt. Suggested using a concept in the conceptual entities domain that would describe the value set. This could support concepts in other terminologies such as those supported for the NDFRT. It would be good to get these changed before the adhoc version get to be used. | ||
UMLS Mapping Files | Tracy tried to load and still has it failing. Scott to check environments and try another load – so far he's not had any failures. | ||
ARC Meeting | Consistent environments for all tiers discussed. Government sponsors for different silos of responsibility could be a problem for coordinating resources for the fall deployment.
| ||
Value Set URI proposal | See above | ||
Project Plan and JIRA Item management around additional requests. | Priority of how these responses are handled discussed.
|
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 |
---|---|
VSMC definition | Need a dialog defining module use around ResolvedValueSets |
Update LexEVS CTS2 Service to CTS2 1.1 | Need deployment tests |
Work on a variety of EVS JIRA Priorities | Scripting, convenience methods, tree extension namespace issues |
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 |
---|---|---|