Search Enhancements (UXPROD-1705)

[UXPROD-2369] Wait for POC of Elastic Search - Implement exact hit count (when using PostgreSql) Created: 31/Mar/20  Updated: 16/Sep/21  Resolved: 03/May/21

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Search Enhancements

Type: New Feature Priority: TBD
Reporter: Charlotte Whitt Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: elastic-search, inventory, result-count, search_result
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
is blocked by UXPROD-2806 Create Elasticsearch indexes for Inve... Closed
Relates
relates to RMB-679 Move totalRecords property to the top... Open
relates to RMB-673 totalRecords returns exact hit count ... Closed
relates to RMB-579 In a GET request, control whether the... Closed
relates to UXPROD-2623 Wait for POC of Elastic Search - Roun... Closed
relates to RMB-578 Inform whether totalRecords is exact ... Blocked
relates to RMB-724 totalRecords=none/auto Closed
relates to CHAL-243 Understand how/when CQL queries can b... Closed
relates to RMB-685 totalRecordsRounded Blocked
Epic Link: Search Enhancements
Development Team: None
PO Ranking Note: CW: This feature is in an undecided state, due to awaiting the outcome of the POC of using Elastic Search in Inventory. 
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R4
Rank: Duke (Full Sum 2021): R2
Rank: 5Colleges (Full Jul 2021): R4
Rank: GBV (MVP Sum 2020): R4
Rank: hbz (TBD): R4
Rank: MO State (MVP June 2020): R4
Rank: TAMU (MVP Jan 2021): R4
Rank: U of AL (MVP Oct 2020): R3

 Description   

CW: This feature is in an undecided state, due to awaiting the outcome of the POC of using Elastic Search in Inventory. 

  • - - - - - - 

SPIKE: Implement exact hit count in Inventory. Eventually roll out FOLIO wide.

This is the long term solution having exact hit count.
For Q1 2020 we'll due to limitation, and performance trade offs we must implement display of "rounded" numbers and then the user can get exact hit count by clicking a button.

There are two implementation options:

  1. The front-end may fetch the exact hit count using RMB-673 Closed "totalRecords returns exact hit count for limit=0" by sending an additional request to mod-inventory-storage.
  2. The front-end may fetch the exact hit count from Elastic Search.

Side note: See estimated totalRecords field how RMB calculates the estimation.
See also spread sheet with different test of searches and their search results in the UI compared with count directly in the DB: https://docs.google.com/spreadsheets/d/1ergJ7jDHdLbD_noWsL-ZdtVzB2NiiIPaCcUeO4ZFLZw/edit#gid=0



 Comments   
Comment by Julian Ladisch [ 17/Jul/20 ]

RMB v30.2.4 implements that limit=0 returns the exact count. ( RMB-673 Closed )

Comment by Charlotte Whitt [ 30/Apr/21 ]

Tod Olson lew235 - should we close this feature as 'Won't do' with the expected direction, that we'll be swapping PostgreSql with Elastic Search? All the associated stories are about RMB.

Any thoughts, or concerns?

CC: Holly Mistlebauer Jakub Skoczen

Comment by lew235 [ 30/Apr/21 ]

no concerns from me

Comment by Tod Olson [ 30/Apr/21 ]

Charlotte Whitt, I don't have a strong view. It sort of depends on what we think this ticket is tracking, work against the Postgresql backend, or a feature that the users see.

If this is tracking work to be done in Inventory with the Postgresql backend, then yes, close it.

If this is tracking the feature "exact hit counts" Inventory, then leave it open until we have the feature and relink to relevant Elasticsearch work.

Comment by Charlotte Whitt [ 03/May/21 ]

Hi Tod Olson - yes this feature is only from tracking Postgresql work. All the listed stories are with the RMB work, and has nothing to do with Exact hit count when using Elastic Search.

I'll go ahead and close the feature.

Generated at Fri Feb 09 00:23:23 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.