Attendees
Name | Role | Present |
---|---|---|
Wright, Larry | NIH/NCI | x |
Fragoso, Gilberto | NIH/NCI | x |
De Coronado, Sherri | NIH/NCI | x |
Safran, Tracy | NIH/NCI [C] | x |
Ong, Kim L | IS | |
Lucas, Jason R | IS | x |
Bauer, Scott | Mayo | x |
Stancl, Craig | Mayo | x |
Endle, Cory | Mayo | x |
Wynne, Robert | NIH/NCI [C] | x |
Tran, Tin | NIH/NCI [C] | x |
Carlsen, Brian | NIH/NCI [C] | |
Wong, Joanne | NIH/NCI [C] | x |
Kuntipuram, Kumar | NIH/NCI [C] |
|
Action Items
Assigned | Description | Date Identified | Due Date | Date Completed | Status |
---|---|---|---|---|---|
Craig/Larry | Follow up with Jose (CTRP) in January 2016 to see if we can assist them and understand their requirements. | 2015.12.16 | 2016.01.31 | Open | |
Scott | Summarize the namespace issue (LEXEVS-1427). This summary should be in the JIRA item itself. | 2016.01.06 | 2016.01.31 | 2016.01.12 | Done |
Scott/Cory | Determine if LEXEVS-1516 (Value Sets) issue is a LexEVS issue or not. | 2016.01.13 | 2016.01.31 | 2016.01.20 | Done |
Scott | Request additional support from Mark about the the VPN issues. | 2016.01.13 | 2016.01.31 | ||
Scott | Follow up with CaDSR team to see if they still have lucene questions. | 2016.01.13 | 2016.01.31 |
Progress
Scott |
|
Cory |
|
Craig |
|
Agenda
Sprint Status | Current Sprint - Sprint 21 ( January 07, 2016 – January 20, 2016 ) LexEVS S13-500 Agile Development - Sprint Status#SprintStatus-Sprint21 |
Sprint Planning | Issue Prioritization Recent LexEVS Related Bugs and Features (within last week)
Recent CTS2 Service Related Issues (within last week)
Issue Grooming Prioritize JIRA issues (fix version 6.4)
|
Triple-Store/SPARQL Discussion | This discussion is to touch base with three different groups to bring everyone up to speed on the latest developments: Northrup Grummond, Mayo, and Gilberto. Jason - Now has a "customer managed" VM set up. Still need to move the existing triple store to this VM. Jason's team also looked at NCBO OWL converter. They had an issue with NCI OWL being converted (RRF to turtle). Scott asked what is the use case for the triple store? NCI suggested the following:
Another use case would be for a triple store over the Metathesaurus. Gilberto suggested two use cases:
Scott suggested that if a SPARQL endpoint is behind LexEVS, our hierarchy API (isA relationships) would call the endpoint instead of the underlying DB now.
Graph DB vs. Triple store - there hasn't been a decision to go with one or the other. If a graph DB works better for LexEVs, than this would be an option. Gilberto mentioned that the paper review is complete. They will be getting demos from vendors:
|
CTRP Planning
| No Update. |
Value Set Resolution LEXEVS-1516 - Getting issue details... STATUS | Tracy has a ticket to update the group to lexevsdb. Jason has implemented the change. If the problem still persists, we will need to debug this issue. |
Tree Extension Issue LEXEVS-1528 - Getting issue details... STATUS | Scott reviewed this issue and this will need further investigation. Depending on how critical this is, it may need to be looked at during the next Sprint. Jason mentioned this is critical for the next release of the browser - release 2.8. The scenario is when you pull up a tree, and click on the "..." it freezes the whole tree. Jason said they are planning to deploy in April. We will need to prioritize this issue to be completed before then. Larry suggested that we work on this right after the lucene issues are fixed. |
Search Extension Testing | The search extension API is now complete. We would like to understand the use cases from the NCI team. We will need to test 6.3 and 6.4 in a test harness to determine any performance issues. In 6.3, search (query across a large number of systems) could take a long time (timeout after 5 minutes). |
LexEVS External Users | No updates. |
Nexxus Testing | Scott is able to log into Ant Hill Pro. He should be able to test the build/deploy when the new Nexxus system is deployed on Saturday 2016.01.30. |
JIRA Issues
Recent LexEVS Related Bugs and Features (within last week)
Recent CTS2 Service Related Issues (within last week)
6.4 LexEVS Related Issues
6.4 CTS2 Service Related Issues
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 |
---|---|---|
Action Item Backlog
# | Assigned | Description | Date Identified | Due Date | Date Completed | Status |
---|---|---|---|---|---|---|
64 | Scott | To follow up on URI's on OWL2 with Harold. | on hold | |||
164 | Cory | Cory to add implementation to CTS2 implementations page. | 2014.04.30 | on hold | ||
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 | ||
200 | Larry/Sherry | Query current LexEVS users about use of SOAP, REST or QBE services in the legacy caCORE api's | 2014.6.18 | on hold | ||
207 | Cory | Write issue against CTS2 OMG regarding the ability to return INACTIVE concepts only. | 2014.07.30 | on hold | ||
210 | Larry/Gilberto | Determine if there is a need to meet with the CTRP | 2014.07.30 | on hold | ||
212 | Larry | Include LexGrid XML Export as part of the 5.1 retirement notice. | 2014.07.30 | on hold | ||
224 | Scott | URI Resolver - Provide overview of how to access the URI Resolver | 2014.09.03 | on hold | ||
225 | Scott | URI Resolver - Look at TLAMP and VSAC service to determine usage of URI Resolver | 2014.09.03 | on hold | ||
244 | Craig | Plan meeting with Tracy to discuss collaborative LexEVS development process | 2014.12.03 | on hold | ||
281 | Scott | Try to replicate what CTRP did to break our service (retrieve a tree through CTS2). | 2015.03.25 | on hold | ||
282 | Mayo Team | Look into implementing graph node in CTS2 for the path to root method (and path to leaf). | 2015.03.25 | on hold |