Create Elasticsearch indexes for Inventory search
Description
Priority
P2Labels
Fix versions
Development Team
Assignee
Magda ZacharskaSolution Architect
Parent Field Value
Parent Status
blocks
is defined by
Checklist
hideTestRail: Results
Activity
Steve Bischof December 11, 2020 at 6:47 PM
Probably the most obvious use case for Five Colleges is limiting by location in combination with things like identifiers, title, author. With multiple cataloging, acquisition and circulation units, this becomes a critical tool for finding the appropriate instance/holding/item
Magda Zacharska December 11, 2020 at 6:39 PM
The initial implementation of Elasticsearch for inventory does not mean to replace the existing Inventory search but add additional option for the user. and if this is showstopper for your institutions please provide use cases so we can prioritize.
Tod Olson December 10, 2020 at 9:43 PM
Chicago - The issue for us is around needed improvements to search and search results in Inventory, many of which have become tied to Elasticsearch implementation. The problem with search in Inventory is that there are many cases where the available identifying text is not enough distinguish between the results. Without those needed improvements, we will be having some difficult conversations about whether we can support our workflows.
Magda Zacharska December 9, 2020 at 11:05 PM
Hi could you provide some use cases where the current implementation of Inventory search is insufficient for Five Colleges' needs?
Steve Bischof December 9, 2020 at 7:46 PM
Five College Showstopper based the complexity of our locations
Details
Details
Reporter
Magda ZacharskaFront End Estimate
Front End Estimator
Magda ZacharskaFront-End Confidence factor
Back End Estimate
Back End Estimator
Magda Zacharska
Current situation or problem:
The existing inventory search does not provide enough flexibility in building the search criteria, does not perform as expected when searches in large collection takes long to return the data. Also, in searches that have more than 1000 records fulfilling the search, the count of the matching records is incorrect.
In scope
Searches against inventory instances, holdings and items:
Instance
Holdings
Items
Keyword search (title, contributor, identifier)
Effective location
Item Status
Effective location
Holdings permanent location
Effective location
Language
Suppress from discovery
Holdings permanent location
Resource type
Material type
Format
Suppress from discovery
Mode of issuance
Nature of content
Staff suppress
Suppress from discovery
Date created (from, to)
Date updated (from, to)
Source
Out of scope
Other than inventory records searches
Updates to existing inventory search.
Proposed solution/stories
1. Define mappings that will determine
which fields should be treated as full text search fields
which fields contain numbers and dates and their format
custom rules for dynamically added fields
2. Define approach to text analysis (tokenization and normalization)
Links to additional info
See tech council discussion on Oct 14: https://folio-org.atlassian.net/wiki/display/TC/2020-10-14+Meeting+notes
Search design discussion: https://folio-org.atlassian.net/wiki/display/DD/Search
Draft search planning: https://docs.google.com/document/d/1enxt2ZRwwVXzo9m1Ghl2tcBW6QxFJzlr6wIGAfTO7x4/edit#heading=h.gtly99rhjpm9
Questions