Page History
...
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 |
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 |
...
Sprint Status | Current Sprint - Sprint 14 (October 1, 2015 – October 14, 2015) LexEVS 6.4 S13-500 Agile Development - Sprint StatusStatus#SprintStatus-Sprint14
Current implementation allows queries on the same field for a given entity spread over a range of documents. Boolean query under the covers provides search on single entity rather than individual documents provides a finer set of returned values. This needs re-implementation in the current version. | ||||||||||||||||||||||||||||||||||||
Sprint Planning |
LexEVS S13-500 LexEVS 6.4 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)
| ||||||||||||||||||||||||||||||||||||
VPN and network evaluation | |||||||||||||||||||||||||||||||||||||
Horizontal Coding Scheme searches | Future implementation. Currently multiple namespaces can exist in the terminology. NCI Thesaurus has relations between branches such as roles between diseases and genes. Use case requires possible modeling within the coding scheme. Create a role within NCIt that connects with an entity in GO. Need a place holder namespace and should we be able to navigate across coding scheme to target of navigation to named entity. Suggestion: feature request. Should have the ability to determine whether or not crossing boundaries of coding schemes is a possible. This might be allowed or not based on a determination in a preferences file. | ||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||
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
| 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 pinged the Mayo and NCI personnel and hasn't heard back yet. | ||||||||||||||||||||||||||||||||||||
Horizontal Coding Scheme searches | |||||||||||||||||||||||||||||||||||||
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 | Face-Face Planning | |||||||||||||||||||||||||||||||||||
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.
| ||||||||||||||||||||||||||||||||||||
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)
...