Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

In Inventory, the estimated result count dramatically changes when you click Load more the second time

Description

Steps to reproduce

  1. Perform a keyword search for the term "physics" in Inventory

  2. Note the (very) approximate result count: More than 10, 000 records found. In the json response, "totalRecords" is 999999999.

  3. The result list displays only a 100 records at a time. Scroll down the result list and click Load more, to see more results (you need to do this twice).

Expected result

When more results are loaded, the approximate total result count stays the same, More than 10, 000 records found.

Actual result

After I've clicked Load more a second time, the result count changes to 4 284 records found, which directly contradicts the original assertion that the amount of returned records was "More than 10, 000". In the json response, "totalRecords" is now 4284.

I click on *Load more *a few times more, and now the result count is consistently given as 4 284. To me as a user, this makes absolutely no sense. Do we anyhting above 10 000 records matching "physics"? Or exactly 4 284?

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

10

Checklist

hide

TestRail: Results

Activity

Show:

Lisa Sjögren October 19, 2020 at 1:07 PM

Verified in our Goldenrod test environment that total records is now displaying as 4 279 straight away. Closing as done!

Lisa Sjögren July 28, 2020 at 11:57 AM

Sounds very promising, thanks summarizing. I will keep my fingers crossed and check try this again after we've upgraded!

Cate Boerema July 28, 2020 at 11:25 AM

In Q2 we eliminated the code path that was generating the "more than 10,000", as that was being generated only some of the time (posing a consistency challenge) and could be wildly inaccurate (e.g. a result of "more than 10,000" when, in fact there were more than a million). The result counts you will see in Goldenrod will still be estimates, but they should be closer to the actuals in the DB and they should be consistent (i.e. the result count for the same search should not differ depending on how the search was executed or how the results were sorted).

We didn't do anything related to the Load more button, but I think the work done to eliminate this code path (see RMB-591 and UIIN-1071) may have resolved the problem you were seeing. But if you were never able to repro in BugFest, I guess we'll have to wait until you upgrade and test again in production!

Lisa Sjögren July 28, 2020 at 10:14 AM

Thanks for the update, ! I don't think I was ever able to repro this in bugfest, actually. Was the issue identified and fixed in Goldenrod?

Cate Boerema July 28, 2020 at 9:56 AM

, this no longer repros in Bugfest environment (https://bugfest-goldenrod.folio.ebsco.com/). See attached screencast.

Done

Details

Assignee

Reporter

Labels

Priority

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created May 14, 2020 at 8:49 AM
Updated October 19, 2020 at 1:07 PM
Resolved October 19, 2020 at 1:07 PM
TestRail: Cases
TestRail: Runs