 |
Page History
Attendees
| Name | Role | Present |
|---|---|---|
| Wright, Larry | NIH/NCI | x |
| Fragoso, Gilberto | NIH/NCI | x |
De Coronado, Sherri | NIH/NCI | |
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 |
| Peterson, Kevin | Mayo | x |
| Wynne, Robert | NIH/NCI | x |
| Tran, Tin | NIH/NCI [C] | x |
| Carlsen, Brian | (NIH/NCI) [C] | x |
| Wong, Joanne | ||
Kuntipuram, Kumar | x |
Action Items
| # | Assigned | Description | Date Identified | Due Date | Date Completed | Status |
|---|---|---|---|---|---|---|
| 293 | Jason | Check into Mayo being designated a trusted site | 2015.06.03 | done |
Progress
| Scott |
|
| Cory |
|
| Craig |
|
Agenda
| Sprint Status | Current Sprint - Sprint 15 (October 15, 2015 - October 28, 2015) LexEVS 6.4 S13-500 Agile Development - Sprint StatusStatus#SprintStatus-Sprint15
| ||||||||||||||||||||||||||||||||||||
| Sprint Planning
LEXEVS-1240 - Searching for parent of a root noted returns the entity with code @@
LEXEVS- 970 Is the overall OWL2 loader issue.
| 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)
| ||||||||||||||||||||||||||||||||||||
Property type investigation and Implementation
| Lucene doesn't have a "query" type mechanism. When "AND"ing these properties together, the results are different than expected. We are looking into how to implement with the latest Lucene 5.3.1. TODO: Scott to create a diagram/description of the problem on the wiki (design documents section) to help everyone understand. | ||||||||||||||||||||||||||||||||||||
Sprint Deliverables - Updates
| Lucene build - Cleanup script is broke. | ||||||||||||||||||||||||||||||||||||
| Build practice is out of date, discuss single jar vs zip file | The build is currently broke. The artifact built does not run due to the new lucene jars and their manifest files. The dev team will need to consider if we need to change the process to create a zip file, rather than a jar. The dev team is suggesting breaking the build up into multiple jars. This new multiple jar approach would break current users of the single jar. Users would need to update their classpath. TODO: Add two groups to work with on the NCI team to the Face to Face agenda. How will this affect NCI users? TODO: Mayo dev team to come up with a proposal on how to migrate to the new jar structure. | Sprint Deliverables
| Mayo to create snapshots for both branches of code 6.3.0.1 - OBI fix and UI dropdown filter on coding schemes Lucene - latest implementation | ||||||||||||||||||||||||||||||||||
VPN and network evaluation | Craig pingedis still waiting to hear back from the Mayo and NCI personnel and hasn't heard back yet/NCI IT. TODO: Craig will follow up with IT to get an update. | ||||||||||||||||||||||||||||||||||||
| Horizontal Coding Scheme searches | TODO: Craig will add this to the Face to Face topics. | ||||||||||||||||||||||||||||||||||||
| Face-Face Planning | December 8 - 10 on-site. There is a wiki link for agenda topics: LexEVS 6.3 and 6.4 Technical Face-To-Face Meetings | ||||||||||||||||||||||||||||||||||||
| CTS2 | One client should be able to connect to multiple instances of a service. Can one endpoint provide data to query against another? How can CTS2 be used in a manner that provides uri's that are not a part of the local resources. Possible face to face topic. | ||||||||||||||||||||||||||||||||||||
| Boolean searches in Lucene 5 | 1) Backwards compatibility, if no extra information is included in the lexevs search call the resultset should be (nearly) the same as we currently get.
2) Expose the ability to do Boolean queries over different user-specified fields (e.g. presentation & definition) a la https://lucene.apache.org/core/2_9_4/queryparsersyntax.html#Fields.
| ||||||||||||||||||||||||||||||||||||
TODO: NCI team to add additional information to the topics for the Face to Face meetings. | |||||||||||||||||||||||||||||||||||||
Search queries - accessing the database opposed to the Lucene index only
| Scott noted that unless you set the resolve flag in the query, it does not go to the DB. | ||||||||||||||||||||||||||||||||||||
LEXEVS- 970
| Scott was able to load the thesaurus locally without any errors. TODO: Scott to work with Gilberto and review a load with restrictions. Gilberto noted the following:
| ||||||||||||||||||||||||||||||||||||
| LexEVS Meeting next week (2015.10.28) | The Mayo team will be out next Wednesday. The NCI will cancel the meeting. The Mayo team will end the existing sprint and start the next one | ||||||||||||||||||||||||||||||||||||
| Questions around how NCI uses sorting mechanisms | We are re-implementing how we are restricting coded nodes. We are are seeing some differences in sorting when doing multi coding scheme index searches. If you do a union query across multiple code systems. Each code system has it's own index. Scoring is done on a each index. This is causing a junit ordering test to fail. We will need to see how this works with real data. | ||||||||||||||||||||||||||||||||||||
| MedDRA 18.1 | If the CUI is left blank will it cause a problem? We don't think so | Search queries | Discuss how to determine whether a search query requires accessing the database opposed to the Lucene index only. . |
JIRA Issues
Recent LexEVS Related Bugs and Features (within last week)
| Jira | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Recent CTS2 Service Related Issues (within last week)
| Jira | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
6.4 LexEVS Related Issues
| Jira | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
6.4 CTS2 Service Related Issues
| Jira | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
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 |
...
