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 |
Brem, Larry | NIH/NCI [C] | |
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 | x | |
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 | |||
72 | Scott | Add release date to Release notes when appropriate | done | |||
129 | Scott | Further testing on Production around the breaking value set | done | |||
130 | Scott | Update 227 for flag for exceeding max clause count | open | |||
131 | Scott | Check the database to make sure the MOA value set entries are there | done | |||
132 | Scott | Fix the value set name truncation by the end of the week | done | |||
133 | Scott | Talk to Harold about value set versioning | done | |||
134 | Scott | Create a JIRA item to track the need to remove Struts | open | |||
135 | JJ | Follow up on security scan to find out what kind found the Struts issue | open | |||
136 | Scott | Point the CTS2 API page to Stage | open | |||
137 | Scott | Set up a time to meet about Value Set Versions | open |
Progress
Immediate Priorities and Problems (Mayo Team) | Value Set Module - still making progress. Coordinating with Kevin on queries across services. CTS2 Client UI - Demo at meetings end. Project Plan Updates - | ||
Tech Stack Notes (Project Plan Related) | Gilberto suggested skipping Java 1.7 and going to 1.8.
| ||
Struts Security Update (Jason) | Vulnerability in current struts version - but we don't use that feature.
| ||
Face To Face Followup | Notes review. No comments or additions. Review what is needed in the ARC meeting - what belongs in that part of notes - Hardware, performance requests. Team to review. | ||
6.1 Deployment | Production server needs to be updated and then another scan. Can point the CTS2 API page. (Scott) | ||
Resolved Value Sets from different Coding Scheme versions (Kim) | Need to consider what options are available to provide versions. Using coding scheme version to manage (but if several coding schemes, may not get what we need). Can set up a dedicated time to discuss. (Kim, Scott, Gilberto(optional)) | ||
JIRA or GitHub for forum (Jason) | Gilberto to show the HubZero forum GitHub - Seems like a better choice
Forum would be on lexevs/lexevs
| ||
Retiring Grid Services | Discussed during Tech meeting on Wed morning. Decided wasn't used in the past/recently, and could be retired. Tracy looked at usage - decided it was declining. (Larry) Thought usage was declining when looking at the IP list | ||
caDSR and Value Sets | Are there rest services that caDSR should be using? Will they use the same URIs that are provided on browser? Currently using the URI that defines the value set. | ||
Value Set UI Demo | Request Ability to search across all services. (feature request for production service) - Out of scope for demo. |
JIRA Issues
Description |
---|
LEXEVS-570 - Getting issue details... STATUS |
LEXEVS-572 - Getting issue details... STATUS |
LEXEVS-573 - Getting issue details... STATUS |
LEXEVS-574 - Getting issue details... STATUS |
LEXEVS-576 - Getting issue details... STATUS |
LEXEVS-579 - Getting issue details... STATUS |
LEXEVS-583 - Getting issue details... STATUS |
LEXEVS-584 - Getting issue details... STATUS |
LEXEVS-585 - Getting issue details... STATUS |
LEXEVS-586 - Getting issue details... STATUS |
LEXEVS-587 - Getting issue details... STATUS |
LEXEVS-588 - Getting issue details... STATUS |
LEXEVS-589 - Getting issue details... STATUS |
LEXEVS-592 - Getting issue details... STATUS |
LEXEVS-593 - Getting issue details... STATUS |
LEXEVS-594 - Getting issue details... STATUS |
LEXEVS-595 - Getting issue details... STATUS |
LEXEVS-596 - Getting issue details... STATUS |
LEXEVS-597 - Getting issue details... STATUS |
LEXEVS-598 - Getting issue details... STATUS |
LEXEVS-599 - Getting issue details... STATUS |
LEXEVS-600 - Getting issue details... STATUS |
LEXEVS-601 - Getting issue details... STATUS |
LEXEVS-602 - Getting issue details... STATUS |
LEXEVS-603 - Getting issue details... STATUS |
LEXEVS-604 - 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 |
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 |
---|---|---|