Discussion Points:
- Systems related topics:
- LexEVS
- Browser/Tools
- Data
- Systems
- Triple Store/EVS API
- EVSRESTAPI firewall exceptions status
- No updates. Chuck will follow up with Jason.
Decision Points:
Sprint Status
Current Sprint - Sprint 97 (December 6, 2018 – December 19, 2018)
16X237 Agile Development - Sprint Status#16X237AgileDevelopment-SprintStatus-Sprint97
Planned Activities
- Release 6.5.2 RC 1
- Loader Fixes
- Security Updates
Anticipated Releases
- Release 6.5.2
Discussion Points:
Decision Points:
- Rob will deploy on Dev, if it hasn't been already
Discussion Points:
- The QA team will be ready to test this version when it is deployed to the QA tier.
Decision Points:
Discussion Points:
- Kim was working on a project for alternative to creating the mappings in CSV format outside the browsers.
- Kim would like source to target term/code mapping data to be populated.
- Kim suggested this should be in the next release (6.5.2)
Decision Points:
- We will need to discuss with Lyuba the priority of this issue.
- Should this go into the next release (6.5.2)?
- Scott will investigate how much work this issue requires.
Discussion Points:
- The LexEVS has a list of its LexEVS security alerts and will need to have a contact to send this list to and discuss.
Decision Points:
- Determine the security contact to discuss LexEVS security alerts with.
Discussion Points:
- Rob is transitioning with Tracy and Akelesh.
- He has a spreadsheet for tracking this.
Decision Points:
- Cory and Jason should add Akelesh to this meeting.
Discussion Points:
- Rob was doing CDISC publications. Tracy will be taking over this task.
- This CDISC publication is on 12/21.
Decision Points:
Discussion Points:
- Agenda for the kick-off meeting on the requirements for the mapping tool(s): What we have from previous years (Kim, Mayo team, Rob’s scripts…), Demo (Kim?)
- Rob suggested that there may be two parts to this mapping:
- Matching (LexEVS?) and Curation
- Lori suggested there will be requests for mapping to NCIt and other terminologies (will need Meta for other terminologies).
- Lori also suggested the mapping tool should be able to handle different spellings of the same word (such as British spelling) and synonyms (ex. stomach cancer and the synonyms of this)
- This mapping tool will hopefully decrease the manual load for the editor's work.
- We will need semantic mapping.
- Kim gave a demo of his mapping tool.
Decision Points:
- Lori will follow up with Lyuba about the kickoff meeting.
Discussion Points:
- Update from Scott on DB on DEV
- The load has the updates from our fix. DB looks OK. We will need to determine if there is an API fix necessary or if it's an additional loader fix.
- The namespaces and coding scheme relationship isn't connected how we expected.
- This should be just a lexevs REST API issue.
- The load has the updates from our fix. DB looks OK. We will need to determine if there is an API fix necessary or if it's an additional loader fix.
Decision Points:
- Scott to create a JIRA item to investigate/fix this issue.
Discussion Points:
Decision Points:
LexEVS External Users
Discussion Points:
Decision Points:
Mayo Team
- Cory - 12/24, 12,25, 12/31, 1/1
- Scott - 12/24, 12,25, 12/26, 1/1
- Craig - 12/24, 12,25, 1/1
NCI
- Tracy - 12/19 - 12/30
- Rob - Last day 12/14
- Kim -
