Page History
...
Sprint Status | Current Sprint - Sprint 14 (October 1, 2015 – October 14, 2015) LexEVS 6.4 Agile Development - Sprint Status
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 6.4 Agile Development - Sprint Status 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)
| ||||||||||||||||||||||||||||||||||||
Property type investigation and Implementation
| |||||||||||||||||||||||||||||||||||||
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. | ||||||||||||||||||||||||||||||||||||
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. |
...