Paused due to POC of Elastic Search. SPIKE: Bugfest: Inventory. Item segment. Filtering on Suppress from discovery: Yes and No Don't Add Up (Off by Unacceptable Amount)

SPIKE: The first step of investigating this issue is for a front-end dev to do a bit of investigation to see if there is any information they can provide to point us in the right direction. To complete the spike, please provide comments with anything you learned, move the issue to whatever project it belongs in (likely a backend project) and advise on which team should pick this up (Core Functional vs Core Platform). Thank you!

Overview: Filtering on Suppress from discovery: No - results in different test alway in 1000 records found, and not the exact count of records found.

Steps to reproduce:

1. Login to FOLIO BugFest, go to Inventory
2. Select the Item segment in the Search and filter pane
3. Search in the search box on Keyword (title, contributor, identifier) on: Nielsen (7,631 records found)
4. Filter on Suppress from discovery: Yes. Get 4 instance results:
   https://bugfest.folio.ebsco.com/inventory?filters=discoverySuppress.true&segment=items
   
5. Clear all searched, and then repeat step 3, and now combine with
6. Filter on Suppress from discovery: No

Actual Result:
Search on Keyword (title, contributor, identifier): Nielsen => 7,631 records found
Search on Keyword (title, contributor, identifier): Nielsen && suppress from discovery == yes => 4 records found
Search on Keyword (title, contributor, identifier): Nielsen && suppress from discovery == no => 1,000 records found

Expected Result:
Search on Keyword (title, contributor, identifier): Nielsen => 7,631 records found
Search on Keyword (title, contributor, identifier): Nielsen && suppress from discovery == yes => 4 records found
Search on Keyword (title, contributor, identifier): Nielsen && suppress from discovery == no => something approximate to 7,627 records found

https://bugfest.folio.ebsco.com/inventory?filters=discoverySuppress.false&segment=items

Additional info:

• Suppressed from discovery is an optional boolean (it doesn't have to be yes or no), but we have a script that should make sure one or the other is populated. Would be interesting to look at the data to see if there are nulls
• We know that the results