NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin
Scrollbar
iconsfalse

...

Panel
titleDocument Information

Author: Craig Stancl, Scott Bauer, Cory Endle
Email: Stancl.craig@mayo.edu, bauer.scott@mayo.edu, endle.cory@mayo.edu
Team: LexEVS
Contract: S13-500 MOD4
Client: NCI CBIIT
National Institutes of Heath
US Department of Health and Human Services

...

The focus is on the functionalities proposed by the stakeholders and target users to make a better product.

Design Scope and Requirements

The LexEVS 6.4 Scope Document can be found here: LexEVS 6.4 Scope Document

Requirements 

The LexEVS 6.4 Requirements Document can be found here: LexEVS 6.4 Requirements Definition Document

Detailed Design

The following sections specify how the design will satisfy the requirements for the Lucene search upgrade.  This design reflects the wide ranging changes that will be necessary to LexEVS to fully update over three full releases of Lucene.  Since Lucene is the heart of the search mechanism that powers efficient searches in LexEVS these changes are necessarily extensive.  The focus of these changes can be broken down, to some extent, into three areas. 

...

Add Page
nameLexEVS Text Match Algorithm Audit
linkTextLexEVS Text Match Algorithm Audit

Consideration of Build Impacts

Add Page
nameConsideration of Build Impacts
linkTextConsideration of Build Impacts

Index Compatibility with Previous Index Versions

...

Lazy loading pagination is a broad concept in LexEVS and can encompass both graph and node set capabilities.  Because this scope is large we are going to consider this out of scope for this project unless we can define a fairly narrow definition of what we want to do with Lucene's version of this.  Currently some lazy loading occurs under the covers in the iterators returned by the coded node set implementation.  We also have  node graph pagination.  In either case we may not need a reimplementation in order to update our Lucene implementation.  We are suggesting this become a possible priority for a later implementation and won't fully describe how this might be done here

Impacts to Existing Users / Applications

Minimal impact overall expected with increased performance and maintenance efficiency expected. 

Impact DescriptionReference to documented impact
Text Matching Algorithm Changes. Support for a wide ranging text matching capability creates potential for heavy maintenance. We have attempted to characterize the similarities between some term matching implementations with an eye towards exclusion or combination. This exclusion and combination only affects end users if we remove labels as algorithm switches. Not specifically impact documentation but a background document: LexEVS Text Match Algorithm Audit
Index File System Changes. Index files will exist per coding scheme. This creates the opportunity for unmerged terminology indexes that should improve maintenance efficiency through quicker load times and the ability to identify and remove broken indexes without having to reindex the entire service. This will change the appearance of the file system but should not cause any issues for end users. The API will remain the same.

Background:

LexEVS Multi-index Lucene Implementation

Faster Query Performance on at Least Some Queries. The goal is to at least make queries no slower than current queries. The use of Block Join Queries has a reputation for being faster. This implementation has some opportunity to provide small indexes if we can properly capitalize during implementation.

Background:

LexEVS Lucene Relational Representation

Index Optimization Function Will Go Away. Index optimization no longer serves the purpose originally intended in Lucene. The optimization function should be deprecated and the implementation changed to output a message that indexes no longer need optimizing. 

Decision Points - Approval Needed

Pagination in Lucene - DEFERRED

Reference: LexEVS 6.4 Software Design Document

Sign off

Date

Role

CBIIT or Stakeholder Organization

Approver's Comments (If disapproved indicate specific areas for improvement.)

Larry Wright4/24/2015Govt Project Manager

CBIIT EVS

---

Sherri de Coronado

4/30/2015

Govt Sponsor

CBIIT EVS

Kumar Kuntipuram

4/30/2015

TPM

Leidos Biomed

 

Reduction of Text Matching Algorithms 

Reference: LexEVS Text Match Algorithm Audit

Text Matching Algorithms to be continued:  This list to be provided when the development team begins to work on these algorithms.  

  • Consideration needs to be given to "Contains" search as it doesn't currently behave correctly. (JIRA LEXEVS-XX)

 

Sign off

Date

Role

CBIIT or Stakeholder Organization

Approver's Comments (If disapproved indicate specific areas for improvement.)

Larry Wright

4/24/2015

Govt Project Manager

CBIIT EVS

---

Sherri de Coronado

4/30/2015

Govt Sponsor

CBIIT EVS

Kumar Kuntipuram

4/30/2015

TPM

Leidos Biomed

 

Lucene Code Decoupling - DEFERRED

Reference: LexEVS Code Decoupling

Sign off

Date

Role

CBIIT or Stakeholder Organization

Approver's Comments (If disapproved indicate specific areas for improvement.)

Larry Wright

4/24/2015

Govt Project Manager

CBIIT EVS

---

Sherri de Coronado

4/30/2015

Govt Sponsor

CBIIT EVS

Kumar Kuntipuran

4/30/2015

TPM

Leidos Biomed

Relevant JIRA Items

Detailed Design - Provide the architecture and design for the new Lucene feature.

Jira
serverNCI Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId7954a81f-12da-3366-a0ef-97c806660e7c
keyLEXEVS-724

The following JIRA items are all part of LEXEVS-724.

Jira
serverNCI Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId7954a81f-12da-3366-a0ef-97c806660e7c
keyLEXEVS-813

Jira
serverNCI Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId7954a81f-12da-3366-a0ef-97c806660e7c
keyLEXEVS-814

Jira
serverNCI Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId7954a81f-12da-3366-a0ef-97c806660e7c
keyLEXEVS-815

Jira
serverNCI Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId7954a81f-12da-3366-a0ef-97c806660e7c
keyLEXEVS-816

Jira
serverNCI Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId7954a81f-12da-3366-a0ef-97c806660e7c
keyLEXEVS-817

Jira
serverNCI Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId7954a81f-12da-3366-a0ef-97c806660e7c
keyLEXEVS-818

Jira
serverNCI Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId7954a81f-12da-3366-a0ef-97c806660e7c
keyLEXEVS-819

Jira
serverNCI Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId7954a81f-12da-3366-a0ef-97c806660e7c
keyLEXEVS-820

Jira
serverNCI Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId7954a81f-12da-3366-a0ef-97c806660e7c
keyLEXEVS-821

Jira
serverNCI Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId7954a81f-12da-3366-a0ef-97c806660e7c
keyLEXEVS-822

Jira
serverNCI Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId7954a81f-12da-3366-a0ef-97c806660e7c
keyLEXEVS-823

Jira
serverNCI Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId7954a81f-12da-3366-a0ef-97c806660e7c
keyLEXEVS-824

Jira
serverNCI Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId7954a81f-12da-3366-a0ef-97c806660e7c
keyLEXEVS-825