Details
-
New Feature
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
None
-
None
-
Prokopovych
-
-
0
-
R1
-
R1
-
R1
Description
Current situation or problem: Inventory app is currently using the technical approach using PostgreSQL, JSONB columns, CQL and RAML Module Builder. This approach has been time consuming to develop, and add supporting search indexes, and cumbersome to improve with precise result counts and a performance expected by the users.
New ideas and suggestions about exploring replacement of PostgreSQL with Elasticsearch was decided by the Technical Council, Autumn 2020.
If Elasticsearch is approved (Spring 2021), then the idea is to make Elasticsearch a FOLIO wide search approach, and having the technology implemented in Inventory, Orders, Users, Request, etc.
Here link to the POC Overview (April 2021) - https://wiki.folio.org/display/DD/Inventory+Search+-+POC+Overview.
And link to the POC evaluators report - https://docs.google.com/document/d/1qaWK-jLKByynlVtCHg761QQJBmyKLqPFZDb3SBfXOag/edit#heading=h.mzcbjmtxclv3
In scope:
- Inventory app - swapping PostgreSQL with Elastic Search
- Deprecate the POC app Inventory ES
- Filters using ES facets to be migrated to the existing Inventory app. Facets provide a significant improvement to the existing Inventory search functionality
Out of scope:
Implementation in other apps.
Use case(s):
As a staff user I search in Inventory, and my search performs fast, and returns relevant and precise results, which I then can access for doing my further work, CRUD, and misc. record management
Proposed solution/stories:
Proposed Inventory Search MVP Kiwi release.docx
Timeline: Kiwi (and possible some work to be postponed to Lotus).
Links to additional info
Searching in Inventory: https://wiki.folio.org/display/FOLIOtips/Searching
Elasticsearch: https://wiki.folio.org/display/DD/Search
Questions:
- What is the impact on automated tests? How many will need to be revised?
- When a change is needed to search, which team(s) will do the work?
TestRail: Results
Attachments
Issue Links
- blocks
-
UIIN-519 Inventory: Instance Sorting. Implement Index title as primary key for Result list
-
- Closed
-
-
UXPROD-2712 Inventory Elastic Search (Lotus): Timebox for Priority Inventory Search and Filter Enhancements
-
- Closed
-
- has to be done before
-
UX-436 UX: Inventory. Elastic Search. Search interface support easy view of search options, and use of boolean operators
-
- Draft
-
- is cloned by
-
UXPROD-3271 NFR: Look up instance plug-in. Swap from search tool PostgreSQL to Elasticsearch
-
- Closed
-
-
UXPROD-3430 Inventory. Implement Facets on filtering (Instance, Holdings, Item) when using Elasticsearch
-
- Closed
-
- is defined by
-
MSEARCH-173 Handle not initialized tenant
-
- Closed
-
-
UIIN-1566 convert existing search/filter endpoints to use ES paths
-
- Closed
-
-
UIIN-1567 incorporate ui-inventory-search facets
-
- Closed
-
-
UIIN-1631 Convert Action menu: Save instances UUIDs from existing search/filter endpoints to use ES paths
-
- Closed
-
-
UISEES-70 Deprecate ui-search-es
-
- Closed
-
-
UISEES-71 Permissions. Specific Inventory ES permissions to be deprecated
-
- Closed
-
- relates to
-
FOLIO-3292 deprecate builds related to platform-core
-
- Closed
-
-
UIPFI-37 Instance look-up component. Convert existing search/filter endpoints to use ES paths
-
- Closed
-
-
UXPROD-902 Faceted Search
-
- Open
-
-
UXPROD-2591 Elasticsearch
-
- Open
-
-
UXPROD-3271 NFR: Look up instance plug-in. Swap from search tool PostgreSQL to Elasticsearch
-
- Closed
-
- mentioned in
-
Page Loading...