<!-- 
RSS generated by JIRA (1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d) at Thu Feb 08 23:22:13 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary add field=key&field=summary to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>FOLIO Jira</title>
    <link>https://folio-org.atlassian.net</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>1001.0.0-SNAPSHOT</version>
        <build-number>100246</build-number>
        <build-date>07-02-2024</build-date>
    </build-info>

<item>
            <title>[UXPROD-2623] Wait for POC of Elastic Search - Round estimated search result hit count (totalRecords)</title>
                <link>https://folio-org.atlassian.net/browse/UXPROD-2623</link>
                <project id="10000" key="UXPROD">UX Product</project>
                    <description>&lt;p&gt;&lt;font color=&quot;#ff8b00&quot;&gt;CW: This feature is in an undecided state, due to awaiting the outcome of the POC of using Elastic Search in Inventory.&lt;/font&gt;&#160;&lt;/p&gt;

&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;- - -&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;&lt;b&gt;Purpose:&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;The totalRecords search result hit count number returned by RMB is precise if totalRecords is below 1000 and it is only an estimation if totalRecords &amp;gt;= 1000 (&lt;a href=&quot;https://github.com/folio-org/raml-module-builder#estimated-totalrecords&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;details&lt;/a&gt;).&lt;br/&gt;
 The front-end currently displays &quot;8081 records found&quot; for estimations.&lt;br/&gt;
 This is misleading (&lt;a href=&quot;https://en.wikipedia.org/wiki/False_precision&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;false precision&lt;/a&gt;).&lt;/p&gt;

&lt;p&gt;&quot;about&quot; should be prepended for &amp;gt;= 1000.&lt;/p&gt;

&lt;p&gt;The number should be rounded for &amp;gt;= 1000.&lt;/p&gt;

&lt;p&gt;&lt;b&gt;Scenarios:&lt;/b&gt;&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;Scenario
	&lt;ul&gt;
		&lt;li&gt;Given a result count is estimated (current understanding is that result counts above 1,000 are estimates)&lt;/li&gt;
		&lt;li&gt;When displayed in FOLIO&lt;/li&gt;
		&lt;li&gt;Then:
		&lt;ul&gt;
			&lt;li&gt;Result count should be preceded by &quot;about&quot;&lt;/li&gt;
			&lt;li&gt;Result count should be rounded using the &quot;Rounded to first digit&quot; method&lt;/li&gt;
			&lt;li&gt;For example:
			&lt;ul&gt;
				&lt;li&gt;Estimated result count from Postgres = 32351&lt;/li&gt;
				&lt;li&gt;Displays in FOLIO as &quot;about 30,000 records found&quot;&lt;/li&gt;
			&lt;/ul&gt;
			&lt;/li&gt;
		&lt;/ul&gt;
		&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
	&lt;li&gt;Scenario
	&lt;ul&gt;
		&lt;li&gt;Given a result count is NOT estimated (current understanding is that result counts under 1,000 are exact)&lt;/li&gt;
		&lt;li&gt;When displayed in FOLIO&lt;/li&gt;
		&lt;li&gt;Then:
		&lt;ul&gt;
			&lt;li&gt;Result count should NOT be preceded by &quot;about&quot;&lt;/li&gt;
			&lt;li&gt;Result count should NOT be rounded&lt;/li&gt;
			&lt;li&gt;For example:
			&lt;ul&gt;
				&lt;li&gt;Exact result count from Postgres = 845&lt;/li&gt;
				&lt;li&gt;Displays in FOLIO as &quot;845 records found&quot;&lt;/li&gt;
			&lt;/ul&gt;
			&lt;/li&gt;
		&lt;/ul&gt;
		&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;&lt;b&gt;Algorithm for the front-end:&lt;/b&gt;&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
&lt;span class=&quot;code-keyword&quot;&gt;if&lt;/span&gt; totalRecordsEstimated is &lt;span class=&quot;code-keyword&quot;&gt;true&lt;/span&gt;
  print &lt;span class=&quot;code-quote&quot;&gt;&quot;about &quot;&lt;/span&gt; + totalRecordsRounded
&lt;span class=&quot;code-keyword&quot;&gt;else&lt;/span&gt; &lt;span class=&quot;code-keyword&quot;&gt;if&lt;/span&gt; totalRecordsEstimated is &lt;span class=&quot;code-keyword&quot;&gt;false&lt;/span&gt;
  print totalRecords
&lt;span class=&quot;code-comment&quot;&gt;// totalRecordsEstimated is undefined until all back-ends have upgraded RMB,
&lt;/span&gt;&lt;span class=&quot;code-comment&quot;&gt;// handle &lt;span class=&quot;code-keyword&quot;&gt;this&lt;/span&gt; gracefully &lt;span class=&quot;code-keyword&quot;&gt;for&lt;/span&gt; folio-testing:
&lt;/span&gt;&lt;span class=&quot;code-keyword&quot;&gt;else&lt;/span&gt; &lt;span class=&quot;code-keyword&quot;&gt;if&lt;/span&gt; totalRecords &amp;lt; 1000
  print totalRecords
&lt;span class=&quot;code-keyword&quot;&gt;else&lt;/span&gt;
  print &lt;span class=&quot;code-quote&quot;&gt;&quot;about &quot;&lt;/span&gt; + totalRecords + &lt;span class=&quot;code-quote&quot;&gt;&quot; (upgrade back-end &lt;span class=&quot;code-keyword&quot;&gt;for&lt;/span&gt; rounding)&quot;&lt;/span&gt;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;&lt;b&gt;Background Discussion:&lt;/b&gt;&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Three rounding proposals were considered&lt;/li&gt;
	&lt;li&gt;Option B, &quot;Round to first digit&quot; was selected&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;&lt;b&gt;Details on Rounding Options Considered:&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;3 rounding proposals are in the comments of MODINVSTOR-468:&lt;/p&gt;

&lt;p&gt;A) Round to magnitude:&lt;/p&gt;
&lt;div class=&apos;table-wrap&apos;&gt;
&lt;table class=&apos;confluenceTable&apos;&gt;&lt;tbody&gt;
&lt;tr&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;about 10,000&lt;/td&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;(3,000-29,999)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;about 100,000&lt;/td&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;(30,000-299,999)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;about 1,000,000&lt;/td&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;(300,000-2,999,999)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;about 10,000,000&lt;/td&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;(3,000,000-29,999,999)&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;&lt;/table&gt;
&lt;/div&gt;


&lt;p&gt;B) Round to first digit:&lt;/p&gt;
&lt;div class=&apos;table-wrap&apos;&gt;
&lt;table class=&apos;confluenceTable&apos;&gt;&lt;tbody&gt;
&lt;tr&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;about 2,000&lt;/td&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;(1,500-2,499)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;about 3,000&lt;/td&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;(2,500-3,499)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;about 4,000&lt;/td&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;(3,500-4,499)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;about 5,000&lt;/td&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;(4,500-5,499)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;about 6,000&lt;/td&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;(5,500-6,499)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;about 7,000&lt;/td&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;(6,500-7,499)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;about 8,000&lt;/td&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;(7,500-8,499)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;about 9,000&lt;/td&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;(8,500-9,499)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;about 10,000&lt;/td&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;(9,500-14,999)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;about 20,000&lt;/td&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;(15,000-24,999)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;about 30,000&lt;/td&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;(25,000-34,999)&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;&lt;/table&gt;
&lt;/div&gt;


&lt;p&gt;C) Round first digit to 1, 2 or 5:&lt;/p&gt;
&lt;div class=&apos;table-wrap&apos;&gt;
&lt;table class=&apos;confluenceTable&apos;&gt;&lt;tbody&gt;
&lt;tr&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;about 2,000&lt;/td&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;(1,500-3,999)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;about 5,000&lt;/td&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;(4,000-7,999)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;about 10,000&lt;/td&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;(8,000-14,999)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;about 20,000&lt;/td&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;(15,000-39,999)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;about 50,000&lt;/td&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;(40,000-79,999)&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;&lt;/table&gt;
&lt;/div&gt;


&lt;p&gt;This issue is about deciding whether there should be a FOLIO standard for rounding, and if yes, which to choose, and whether the front-end or the back-end should round the number.&lt;/p&gt;

&lt;p&gt;&lt;b&gt;Proposed API as of July 28, 2020&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;If the back-end rounds it should also provide to original (non-rounded) estimate, for example&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
totalRecords: 1431
totalRecordsRounded: 1000
totalRecordsEstimated: &lt;span class=&quot;code-keyword&quot;&gt;true&lt;/span&gt;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;No rounding is needed for an exact number:&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
totalRecords: 1509
totalRecordsEstimated: &lt;span class=&quot;code-keyword&quot;&gt;false&lt;/span&gt;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href=&quot;https://github.com/folio-org/raml/blob/raml1.0/schemas/resultInfo.schema&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/raml/blob/raml1.0/schemas/resultInfo.schema&lt;/a&gt; needs to be extended accordingly.&lt;/p&gt;</description>
                <environment></environment>
        <key id="11469">UXPROD-2623</key>
            <summary>Wait for POC of Elastic Search - Round estimated search result hit count (totalRecords)</summary>
                <type id="10002" iconUrl="https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10322?size=medium">New Feature</type>
                                            <priority id="10005" iconUrl="https://dev.folio.org/assets/jira-priority/tbd.svg">TBD</priority>
                        <status id="6" iconUrl="https://folio-org.atlassian.net/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10000">Won&apos;t Do</resolution>
                                                        <assignee accountid="557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d">Jakub Skoczen</assignee>
                                                                <reporter accountid="5ee89462f7aa140abd82d11d">Julian Ladisch</reporter>
                                    <labels>
                            <label>NFR</label>
                            <label>elastic-search</label>
                            <label>q3-2020-spillover</label>
                            <label>result-count</label>
                            <label>search</label>
                            <label>searching</label>
                    </labels>
                <created>Wed, 17 Jun 2020 16:13:54 +0000</created>
                <updated>Wed, 11 Aug 2021 21:06:50 +0000</updated>
                            <resolved>Wed, 11 Aug 2021 20:11:47 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>18</watches>
                                                                <comments>
                                                            <comment id="14877" author="5af5ed55244bc90a106063c7" created="Thu, 18 Jun 2020 11:02:28 +0000"  >&lt;p&gt;Thanks for filing this, &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ee89462f7aa140abd82d11d&quot; class=&quot;user-hover&quot; rel=&quot;5ee89462f7aa140abd82d11d&quot; data-account-id=&quot;5ee89462f7aa140abd82d11d&quot; accountid=&quot;5ee89462f7aa140abd82d11d&quot; rel=&quot;noreferrer&quot;&gt;Julian Ladisch&lt;/a&gt;.  I added columns O, P and Q to the result count testing spreadsheet.  Could you add a formula to those columns showing what the output of each strategy would result in?  It would be helpful in evaluating which is the best.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://docs.google.com/spreadsheets/d/1ergJ7jDHdLbD_noWsL-ZdtVzB2NiiIPaCcUeO4ZFLZw/edit#gid=0&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://docs.google.com/spreadsheets/d/1ergJ7jDHdLbD_noWsL-ZdtVzB2NiiIPaCcUeO4ZFLZw/edit#gid=0&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;+ &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Af80403de-e149-421e-8750-af45c853402f&quot; class=&quot;user-hover&quot; rel=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; data-account-id=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; accountid=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; rel=&quot;noreferrer&quot;&gt;Charlotte Whitt&lt;/a&gt; and &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=63e2a2771b13d42998e4e706&quot; class=&quot;user-hover&quot; rel=&quot;63e2a2771b13d42998e4e706&quot; data-account-id=&quot;63e2a2771b13d42998e4e706&quot; accountid=&quot;63e2a2771b13d42998e4e706&quot; rel=&quot;noreferrer&quot;&gt;Marc Johnson&lt;/a&gt;&lt;/p&gt;</comment>
                                                            <comment id="14881" author="63e2a2771b13d42998e4e706" created="Thu, 18 Jun 2020 11:06:26 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5ed55244bc90a106063c7&quot; class=&quot;user-hover&quot; rel=&quot;5af5ed55244bc90a106063c7&quot; data-account-id=&quot;5af5ed55244bc90a106063c7&quot; accountid=&quot;5af5ed55244bc90a106063c7&quot; rel=&quot;noreferrer&quot;&gt;Cate Boerema&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ab8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; class=&quot;user-hover&quot; rel=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; data-account-id=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; accountid=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; rel=&quot;noreferrer&quot;&gt;Jakub Skoczen&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Has it been decided that we are going to round these estimated counts? And we are now trying to decide what rounding approach to take?&lt;/p&gt;</comment>
                                                            <comment id="14884" author="5ee89462f7aa140abd82d11d" created="Thu, 18 Jun 2020 11:24:28 +0000"  >&lt;p&gt;Quote from this issues description:&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;This issue is about deciding whether there should be a FOLIO standard for rounding, and if yes, which to choose.&lt;/p&gt;&lt;/blockquote&gt;</comment>
                                                            <comment id="14887" author="5ee89462f7aa140abd82d11d" created="Thu, 18 Jun 2020 11:27:37 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5ed55244bc90a106063c7&quot; class=&quot;user-hover&quot; rel=&quot;5af5ed55244bc90a106063c7&quot; data-account-id=&quot;5af5ed55244bc90a106063c7&quot; accountid=&quot;5af5ed55244bc90a106063c7&quot; rel=&quot;noreferrer&quot;&gt;Cate Boerema&lt;/a&gt; I&apos;ve added number ranges showing the rounding rules to the issue description. Programming a formula takes longer than manually filling the columns. Could you fill the columns?&lt;/p&gt;</comment>
                                                            <comment id="14890" author="557058:f80403de-e149-421e-8750-af45c853402f" created="Thu, 18 Jun 2020 12:06:54 +0000"  >&lt;p&gt;Of the three suggested solutions, then I definitely prefer solution &lt;b&gt;B) Round to first digit.&lt;/b&gt;&lt;br/&gt;
I can ask the MM-SIG at today&apos;s meeting - if that brings us forward in making a decision.&lt;/p&gt;

&lt;p&gt;CC: &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5ed55244bc90a106063c7&quot; class=&quot;user-hover&quot; rel=&quot;5af5ed55244bc90a106063c7&quot; data-account-id=&quot;5af5ed55244bc90a106063c7&quot; accountid=&quot;5af5ed55244bc90a106063c7&quot; rel=&quot;noreferrer&quot;&gt;Cate Boerema&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ee89462f7aa140abd82d11d&quot; class=&quot;user-hover&quot; rel=&quot;5ee89462f7aa140abd82d11d&quot; data-account-id=&quot;5ee89462f7aa140abd82d11d&quot; accountid=&quot;5ee89462f7aa140abd82d11d&quot; rel=&quot;noreferrer&quot;&gt;Julian Ladisch&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=63e2a2771b13d42998e4e706&quot; class=&quot;user-hover&quot; rel=&quot;63e2a2771b13d42998e4e706&quot; data-account-id=&quot;63e2a2771b13d42998e4e706&quot; accountid=&quot;63e2a2771b13d42998e4e706&quot; rel=&quot;noreferrer&quot;&gt;Marc Johnson&lt;/a&gt;&lt;/p&gt;</comment>
                                                            <comment id="14892" author="557058:f80403de-e149-421e-8750-af45c853402f" created="Thu, 18 Jun 2020 12:21:40 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ee89462f7aa140abd82d11d&quot; class=&quot;user-hover&quot; rel=&quot;5ee89462f7aa140abd82d11d&quot; data-account-id=&quot;5ee89462f7aa140abd82d11d&quot; accountid=&quot;5ee89462f7aa140abd82d11d&quot; rel=&quot;noreferrer&quot;&gt;Julian Ladisch&lt;/a&gt;&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;Could you fill the columns?&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;I can fill in the columns - np &lt;img class=&quot;emoticon&quot; src=&quot;/images/icons/emoticons/smile.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt;&lt;/p&gt;</comment>
                                                            <comment id="14895" author="5af5ed55244bc90a106063c7" created="Thu, 18 Jun 2020 13:22:01 +0000"  >&lt;p&gt;Thank you &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ee89462f7aa140abd82d11d&quot; class=&quot;user-hover&quot; rel=&quot;5ee89462f7aa140abd82d11d&quot; data-account-id=&quot;5ee89462f7aa140abd82d11d&quot; accountid=&quot;5ee89462f7aa140abd82d11d&quot; rel=&quot;noreferrer&quot;&gt;Julian Ladisch&lt;/a&gt; and &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Af80403de-e149-421e-8750-af45c853402f&quot; class=&quot;user-hover&quot; rel=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; data-account-id=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; accountid=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; rel=&quot;noreferrer&quot;&gt;Charlotte Whitt&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Af80403de-e149-421e-8750-af45c853402f&quot; class=&quot;user-hover&quot; rel=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; data-account-id=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; accountid=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; rel=&quot;noreferrer&quot;&gt;Charlotte Whitt&lt;/a&gt;, when assessing the methods, please refer to column W which represents the actual count in the DB.  &lt;/p&gt;

&lt;p&gt;Thanks!&lt;/p&gt;</comment>
                                                            <comment id="14898" author="557058:f80403de-e149-421e-8750-af45c853402f" created="Thu, 18 Jun 2020 14:00:58 +0000"  >&lt;p&gt;Okay - now done with filling in estimated counts in column N, O, and P for the rows where we have actual count in the DB (see row W) - &lt;a href=&quot;https://docs.google.com/spreadsheets/d/1ergJ7jDHdLbD_noWsL-ZdtVzB2NiiIPaCcUeO4ZFLZw/edit#gid=0&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://docs.google.com/spreadsheets/d/1ergJ7jDHdLbD_noWsL-ZdtVzB2NiiIPaCcUeO4ZFLZw/edit#gid=0&lt;/a&gt;&lt;/p&gt;</comment>
                                                            <comment id="14901" author="63e2a2771b13d42998e4e706" created="Thu, 18 Jun 2020 15:12:56 +0000"  >&lt;p&gt;I had a follow up conversation with &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5ed55244bc90a106063c7&quot; class=&quot;user-hover&quot; rel=&quot;5af5ed55244bc90a106063c7&quot; data-account-id=&quot;5af5ed55244bc90a106063c7&quot; accountid=&quot;5af5ed55244bc90a106063c7&quot; rel=&quot;noreferrer&quot;&gt;Cate Boerema&lt;/a&gt; to try to understand what the current situation is. Based upon that I have some follow-up questions.&lt;/p&gt;

&lt;h2&gt;&lt;a name=&quot;Toroundornot%3F&quot;&gt;&lt;/a&gt;To round or not?&lt;/h2&gt;

&lt;p&gt;My understanding is that &lt;b&gt;it has been decided to round &lt;em&gt;some&lt;/em&gt; of the &lt;em&gt;estimated&lt;/em&gt; record counts&lt;/b&gt;. Does that fit with everyone else&apos;s understanding?&lt;/p&gt;

&lt;p&gt;If so, shall I change the description of this issue to reflect that decision? (I will also need to document this in a decision log, where is yet to be decided)&lt;/p&gt;

&lt;p&gt;The rest of my comment will assume that this initial decision has been made.&lt;/p&gt;

&lt;h2&gt;&lt;a name=&quot;Whichrecordcountsshouldberounded%3F&quot;&gt;&lt;/a&gt;Which record counts should be rounded?&lt;/h2&gt;

&lt;p&gt;Does this decision only apply to instance searches within inventory?&lt;/p&gt;

&lt;p&gt;Does it apply to other records in inventory, e.g. items, loan types or resource types?&lt;/p&gt;

&lt;p&gt;Or does this apply to any searches where the record counts are estimated? &lt;/p&gt;

&lt;p&gt;Given that the estimation technique and limitations are specific to RAML Module Builder and may not apply to other parts of FOLIO, if we intend for this to be a general decision, we may need a way to distinguish between estimated and non-estimated counts.&lt;/p&gt;

&lt;h2&gt;&lt;a name=&quot;How%2Fwhereistheroundinggoingtobeapplied%3F&quot;&gt;&lt;/a&gt;How / where is the rounding going to be applied?&lt;/h2&gt;

&lt;p&gt;This may depend upon the scope of this decision. If we intend to be selective about which record counts we want to round, this is likely going to need to be design/compile time configurable, e.g. switched on for mod-inventory-storage / UI inventory, off elsewhere.&lt;/p&gt;

&lt;p&gt;There are likely trade-offs to where we do this rounding, I shall defer sharing my understanding of those until we have progressed this conversation a little further.&lt;/p&gt;

&lt;h2&gt;&lt;a name=&quot;Whatgovernanceisneededforthisdecision%3F&quot;&gt;&lt;/a&gt;What governance is needed for this decision?&lt;/h2&gt;

&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ab8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; class=&quot;user-hover&quot; rel=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; data-account-id=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; accountid=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; rel=&quot;noreferrer&quot;&gt;Jakub Skoczen&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5cf6c546b87c300f36eb7b9a&quot; class=&quot;user-hover&quot; rel=&quot;5cf6c546b87c300f36eb7b9a&quot; data-account-id=&quot;5cf6c546b87c300f36eb7b9a&quot; accountid=&quot;5cf6c546b87c300f36eb7b9a&quot; rel=&quot;noreferrer&quot;&gt;Craig McNally&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=615afd1cd9820f0070a09ef0&quot; class=&quot;user-hover&quot; rel=&quot;615afd1cd9820f0070a09ef0&quot; data-account-id=&quot;615afd1cd9820f0070a09ef0&quot; accountid=&quot;615afd1cd9820f0070a09ef0&quot; rel=&quot;noreferrer&quot;&gt;Zak Burke&lt;/a&gt; Is this a significant enough decision that this needs review by the Technical Leads or the Technical Council? (this might depend upon how far reaching this decision is)&lt;/p&gt;</comment>
                                                            <comment id="14905" author="5ee89462f7aa140abd82d11d" created="Thu, 18 Jun 2020 16:12:49 +0000"  >&lt;p&gt;Using column W (actual count in DB) for examples might be misleading. When implemented the rounding is applied to the estimated count, not the actual count in DB. Half of the cases are rounded towards the actual count in DB and the other half are rounded away.&lt;/p&gt;</comment>
                                                            <comment id="14908" author="557058:f80403de-e149-421e-8750-af45c853402f" created="Thu, 18 Jun 2020 16:35:05 +0000"  >&lt;p&gt;Oh ... &lt;em&gt;(sigh)&lt;/em&gt; &lt;/p&gt;

&lt;p&gt;I can do it all one more time ... when I&apos;m out of meetings.&lt;br/&gt;
Thanks for clarifying this &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ee89462f7aa140abd82d11d&quot; class=&quot;user-hover&quot; rel=&quot;5ee89462f7aa140abd82d11d&quot; data-account-id=&quot;5ee89462f7aa140abd82d11d&quot; accountid=&quot;5ee89462f7aa140abd82d11d&quot; rel=&quot;noreferrer&quot;&gt;Julian Ladisch&lt;/a&gt; &lt;img class=&quot;emoticon&quot; src=&quot;/images/icons/emoticons/smile.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt;&lt;/p&gt;</comment>
                                                            <comment id="14911" author="5af5ed55244bc90a106063c7" created="Fri, 19 Jun 2020 09:50:07 +0000"  >&lt;blockquote&gt;&lt;p&gt;Using column W (actual count in DB) for examples might be misleading. When implemented the rounding is applied to the estimated count, not the actual count in DB. Half of the cases are rounded towards the actual count in DB and the other half are rounded away.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Yeah, but we want to see how the displayed result counts compare to the &lt;em&gt;actuals&lt;/em&gt;.  That&apos;s what matters.  I know that, in some cases it will make them the displayed count less accurate.  I think it is very important that we look at how often that happens and how big of a problem it is.  Hence, we should compare what will be displayed to the &lt;em&gt;actuals&lt;/em&gt;.&lt;/p&gt;</comment>
                                                            <comment id="14914" author="5af5ed55244bc90a106063c7" created="Fri, 19 Jun 2020 09:55:22 +0000"  >&lt;p&gt;Oh, I see what &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Af80403de-e149-421e-8750-af45c853402f&quot; class=&quot;user-hover&quot; rel=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; data-account-id=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; accountid=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; rel=&quot;noreferrer&quot;&gt;Charlotte Whitt&lt;/a&gt; did.  Yeah, I didn&apos;t mean to apply the rounding rules to the actual count.  I meant to compare the results of the various rounding rules as applied to the raw result count (columns O,P and Q) to the actual counts (now in column Z (was column W)).  &lt;/p&gt;</comment>
                                                            <comment id="14917" author="5af5ed55244bc90a106063c7" created="Mon, 27 Jul 2020 09:59:36 +0000"  >&lt;p&gt;We want to do this in Q3, so we need to decide:&lt;br/&gt;
1. What do we want to round and how&lt;br/&gt;
2. Where do we want to do it (front end vs back end)&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Af80403de-e149-421e-8750-af45c853402f&quot; class=&quot;user-hover&quot; rel=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; data-account-id=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; accountid=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; rel=&quot;noreferrer&quot;&gt;Charlotte Whitt&lt;/a&gt; and I can work on an answer to the first question (e.g. actuals aren&apos;t estimated, estimates are and they should be estimated as follows...).  Tech folks (&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=63e2a2771b13d42998e4e706&quot; class=&quot;user-hover&quot; rel=&quot;63e2a2771b13d42998e4e706&quot; data-account-id=&quot;63e2a2771b13d42998e4e706&quot; accountid=&quot;63e2a2771b13d42998e4e706&quot; rel=&quot;noreferrer&quot;&gt;Marc Johnson&lt;/a&gt;, &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ee89462f7aa140abd82d11d&quot; class=&quot;user-hover&quot; rel=&quot;5ee89462f7aa140abd82d11d&quot; data-account-id=&quot;5ee89462f7aa140abd82d11d&quot; accountid=&quot;5ee89462f7aa140abd82d11d&quot; rel=&quot;noreferrer&quot;&gt;Julian Ladisch&lt;/a&gt;, &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=615afd1cd9820f0070a09ef0&quot; class=&quot;user-hover&quot; rel=&quot;615afd1cd9820f0070a09ef0&quot; data-account-id=&quot;615afd1cd9820f0070a09ef0&quot; accountid=&quot;615afd1cd9820f0070a09ef0&quot; rel=&quot;noreferrer&quot;&gt;Zak Burke&lt;/a&gt;, &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5cf6c546b87c300f36eb7b9a&quot; class=&quot;user-hover&quot; rel=&quot;5cf6c546b87c300f36eb7b9a&quot; data-account-id=&quot;5cf6c546b87c300f36eb7b9a&quot; accountid=&quot;5cf6c546b87c300f36eb7b9a&quot; rel=&quot;noreferrer&quot;&gt;Craig McNally&lt;/a&gt;) should decide where.&lt;/p&gt;

&lt;p&gt;Also need a decision on what the intended scope is for Q3 (I&apos;m currently thinking it&apos;s okay if we only manage to do this in Inventory even if it means inconsistency with rest of FOLIO).  &lt;/p&gt;</comment>
                                                            <comment id="14920" author="615afd1cd9820f0070a09ef0" created="Tue, 28 Jul 2020 03:28:04 +0000"  >&lt;p&gt;It doesn&apos;t much matter to me where rounding or estimation happens, i.e. if the backend or frontend is responsible for implementing the algorithm, or how to round the values, which seems like the domain of a SIG. What matters to me as a developer, and I suspect to anybody using the API directly, is knowing when a value reflects an exact count, when a value reflects an estimated count, and when a value has been rounded. Confusion about the meaning of &lt;tt&gt;totalRecords&lt;/tt&gt; has led to a lot of heartache (
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;RMB-684&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/RMB-684&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;GET query returns no records when offset value &amp;gt; estimated totalRecords&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10303?size=medium&quot; /&gt;
            RMB-684
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
, 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;MODINVSTOR-321&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/MODINVSTOR-321&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;999 999 999 Records found&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10303?size=medium&quot; /&gt;
            MODINVSTOR-321
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
, 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;STSMACOM-259&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/STSMACOM-259&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Instance search result total is wrong when there are 10K+ records in Inventory&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10303?size=medium&quot; /&gt;
            STSMACOM-259
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
, 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;UIIN-1055&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UIIN-1055&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Bugfest: Inventory. Sorting by Title gives different result counts than no sort when *searching*&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10303?size=medium&quot; /&gt;
            UIIN-1055
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
, 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;UIIN-1071&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UIIN-1071&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Bugfest: Inventory. Sorting by Title gives different result counts when *filtering* (&amp;quot;More than 10,000 records found&amp;quot; (approximation is not close enough))&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10303?size=medium&quot; /&gt;
            UIIN-1071
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
, etc).&lt;/p&gt;

&lt;p&gt;Personally, I would like to see &lt;tt&gt;totalRecords&lt;/tt&gt; deprecated, or at least supplemented, by a set of values such as &lt;tt&gt;exactCount&lt;/tt&gt; and/or &lt;tt&gt;estimatedCount&lt;/tt&gt; and/or &lt;tt&gt;roundedCount&lt;/tt&gt; so the consumer of that value (whether a person using Postman or a UI like stripes) can make an intelligent decision about what to do based on what kind of value is available. &lt;/p&gt;</comment>
                                                            <comment id="14924" author="5ee89462f7aa140abd82d11d" created="Tue, 28 Jul 2020 07:27:37 +0000"  >&lt;p&gt;I agree, this is out of scope of this Jira and should be discussed in other Jiras:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;
    &lt;span class=&quot;jira-issue-macro&quot; data-jira-key=&quot;RMB-578&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/RMB-578&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Inform whether totalRecords is exact or an estimate&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10322?size=medium&quot; /&gt;
            RMB-578
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-complete jira-macro-single-issue-export-pdf&quot;&gt;Blocked&lt;/span&gt;
            &lt;/span&gt;
 Inform whether totalRecords is exact or an estimate&lt;/li&gt;
	&lt;li&gt;UXPROD-2369/RMB-673 Implement exact hit count&lt;/li&gt;
&lt;/ul&gt;
</comment>
                                                            <comment id="14927" author="5af5ed55244bc90a106063c7" created="Tue, 28 Jul 2020 10:00:32 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ee89462f7aa140abd82d11d&quot; class=&quot;user-hover&quot; rel=&quot;5ee89462f7aa140abd82d11d&quot; data-account-id=&quot;5ee89462f7aa140abd82d11d&quot; accountid=&quot;5ee89462f7aa140abd82d11d&quot; rel=&quot;noreferrer&quot;&gt;Julian Ladisch&lt;/a&gt; where should we have a conversation about whether the rounding is done on the frontend or the backend?  Neither of the two tickets you linked seem like they concern that question.&lt;/p&gt;</comment>
                                                            <comment id="14930" author="615afd1cd9820f0070a09ef0" created="Tue, 28 Jul 2020 11:18:16 +0000"  >&lt;p&gt;I don&apos;t have strong feelings about where rounding is implemented. &lt;/p&gt;

&lt;p&gt;RMB seems like an easy place to implement rounding on the backend, but that means that every module that wants rounding needs to update its RMB version, &lt;em&gt;and&lt;/em&gt; we&apos;ll have to make some front-end updates to find that new property. Given that, maybe rounding is best handled in the front-end, because all UI modules share a common stripes-connect version and since we have to handle it there anyway, we might as well only handle it there. &lt;/p&gt;</comment>
                                                            <comment id="14934" author="63e2a2771b13d42998e4e706" created="Tue, 28 Jul 2020 11:44:14 +0000"  >&lt;p&gt;The questions that &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5ed55244bc90a106063c7&quot; class=&quot;user-hover&quot; rel=&quot;5af5ed55244bc90a106063c7&quot; data-account-id=&quot;5af5ed55244bc90a106063c7&quot; accountid=&quot;5af5ed55244bc90a106063c7&quot; rel=&quot;noreferrer&quot;&gt;Cate Boerema&lt;/a&gt; is asking came about from a conversation her and I had.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ee89462f7aa140abd82d11d&quot; class=&quot;user-hover&quot; rel=&quot;5ee89462f7aa140abd82d11d&quot; data-account-id=&quot;5ee89462f7aa140abd82d11d&quot; accountid=&quot;5ee89462f7aa140abd82d11d&quot; rel=&quot;noreferrer&quot;&gt;Julian Ladisch&lt;/a&gt; I agree that the details of the API response representation for indicating whether the count is an estimate or not is best discussed on 
    &lt;span class=&quot;jira-issue-macro&quot; data-jira-key=&quot;RMB-578&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/RMB-578&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Inform whether totalRecords is exact or an estimate&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10322?size=medium&quot; /&gt;
            RMB-578
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-complete jira-macro-single-issue-export-pdf&quot;&gt;Blocked&lt;/span&gt;
            &lt;/span&gt;
&lt;/p&gt;

&lt;p&gt;I think this issue is a good place (unless someone wants to write a design proposal, which might be what we should do) to discuss the overall decisions about rounding.&lt;/p&gt;

&lt;p&gt;I think those questions can be separated into organisational policy (these might influence the technical design) and technical design.&lt;/p&gt;

&lt;p&gt;&lt;b&gt;Organisational policy&lt;/b&gt;&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Should all estimated counts be rounded e.g. should only the counts in the staff reference UI be estimated, or should the rounding also apply to discovery systems or other clients?&lt;/li&gt;
	&lt;li&gt;What rules should be used to do the rounding? Are these the same everywhere, e.g. inventory vs. acquisitions, staff vs. discovery views, instances vs. locations?&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;&lt;b&gt;Technical Design&lt;/b&gt;&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Should the rounding be done in the reference back end or reference front end modules?&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5ed55244bc90a106063c7&quot; class=&quot;user-hover&quot; rel=&quot;5af5ed55244bc90a106063c7&quot; data-account-id=&quot;5af5ed55244bc90a106063c7&quot; accountid=&quot;5af5ed55244bc90a106063c7&quot; rel=&quot;noreferrer&quot;&gt;Cate Boerema&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Af80403de-e149-421e-8750-af45c853402f&quot; class=&quot;user-hover&quot; rel=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; data-account-id=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; accountid=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; rel=&quot;noreferrer&quot;&gt;Charlotte Whitt&lt;/a&gt; The question about which counts should be rounded is especially imported and might influence technical decisions. &lt;/p&gt;

&lt;p&gt;For example, if we decide that some clients e.g. discovery want to apply their own rounding rules (or not round at all), then that either means the back-end should not round at all, or whether it does or not should be controlled by the client.&lt;/p&gt;

&lt;p&gt;(I think the questions I asked from my previous comment mostly overlap with this, however they might be useful for reference)&lt;/p&gt;

&lt;p&gt;cc: &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5cf6c546b87c300f36eb7b9a&quot; class=&quot;user-hover&quot; rel=&quot;5cf6c546b87c300f36eb7b9a&quot; data-account-id=&quot;5cf6c546b87c300f36eb7b9a&quot; accountid=&quot;5cf6c546b87c300f36eb7b9a&quot; rel=&quot;noreferrer&quot;&gt;Craig McNally&lt;/a&gt;&lt;/p&gt;</comment>
                                                            <comment id="14940" author="5af5ed55244bc90a106063c7" created="Tue, 28 Jul 2020 11:55:43 +0000"  >&lt;p&gt;Thanks for your thoughts, &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=615afd1cd9820f0070a09ef0&quot; class=&quot;user-hover&quot; rel=&quot;615afd1cd9820f0070a09ef0&quot; data-account-id=&quot;615afd1cd9820f0070a09ef0&quot; accountid=&quot;615afd1cd9820f0070a09ef0&quot; rel=&quot;noreferrer&quot;&gt;Zak Burke&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;I&apos;ve done a bit of analysis on the relative accuracy of the different rounding methods.  See columns R, S and T here: &lt;a href=&quot;https://docs.google.com/spreadsheets/d/1ergJ7jDHdLbD_noWsL-ZdtVzB2NiiIPaCcUeO4ZFLZw/edit#gid=0&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://docs.google.com/spreadsheets/d/1ergJ7jDHdLbD_noWsL-ZdtVzB2NiiIPaCcUeO4ZFLZw/edit#gid=0&lt;/a&gt;  I compared the estimates that would come from each rounding method (&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ee89462f7aa140abd82d11d&quot; class=&quot;user-hover&quot; rel=&quot;5ee89462f7aa140abd82d11d&quot; data-account-id=&quot;5ee89462f7aa140abd82d11d&quot; accountid=&quot;5ee89462f7aa140abd82d11d&quot; rel=&quot;noreferrer&quot;&gt;Julian Ladisch&lt;/a&gt; provided these in columns O, P and Q ) with the actuals from the DB (column Z).  The &quot;Rounded to first digit&quot; method was the closest to actual more often than the other methods (17 times vs 14 for &quot;Rounded first digit to 1, 2 or 5&quot; and 9 for &quot;Rounded to magnitude&quot;).  I know this is a relatively small sample size, but I think it&apos;s probably good enough.&lt;/p&gt;

&lt;p&gt;Does anyone have any concerns with this methodology?&lt;/p&gt;

&lt;p&gt;Assuming no concerns, I think the business requirements should be something like the following:&lt;/p&gt;

&lt;ol&gt;
	&lt;li&gt;Scenario
	&lt;ul&gt;
		&lt;li&gt;Given a result count is estimated (current understanding is that result counts above 1,000 are estimates)&lt;/li&gt;
		&lt;li&gt;When displayed in FOLIO&lt;/li&gt;
		&lt;li&gt;Then:
		&lt;ul&gt;
			&lt;li&gt;Result count should be preceded by &quot;about&quot;&lt;/li&gt;
			&lt;li&gt;Result count should be rounded using the &quot;Rounded to first digit&quot; method&lt;/li&gt;
			&lt;li&gt;For example:
			&lt;ul&gt;
				&lt;li&gt;Estimated result count from Postgres = 32351&lt;/li&gt;
				&lt;li&gt;Displays in FOLIO as &quot;about 30,000 records found&quot;&lt;/li&gt;
			&lt;/ul&gt;
			&lt;/li&gt;
		&lt;/ul&gt;
		&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
	&lt;li&gt;Scenario
	&lt;ul&gt;
		&lt;li&gt;Given a result count is NOT estimated (current understanding is that result counts under 1,000 are exact)&lt;/li&gt;
		&lt;li&gt;When displayed in FOLIO&lt;/li&gt;
		&lt;li&gt;Then:
		&lt;ul&gt;
			&lt;li&gt;Result count should NOT be preceded by &quot;about&quot;&lt;/li&gt;
			&lt;li&gt;Result count should NOT be rounded&lt;/li&gt;
			&lt;li&gt;For example:
			&lt;ul&gt;
				&lt;li&gt;Exact result count from Postgres = 845&lt;/li&gt;
				&lt;li&gt;Displays in FOLIO as &quot;845 records found&quot;&lt;/li&gt;
			&lt;/ul&gt;
			&lt;/li&gt;
		&lt;/ul&gt;
		&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;Thoughts &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Af80403de-e149-421e-8750-af45c853402f&quot; class=&quot;user-hover&quot; rel=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; data-account-id=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; accountid=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; rel=&quot;noreferrer&quot;&gt;Charlotte Whitt&lt;/a&gt;, &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=63e2a2771b13d42998e4e706&quot; class=&quot;user-hover&quot; rel=&quot;63e2a2771b13d42998e4e706&quot; data-account-id=&quot;63e2a2771b13d42998e4e706&quot; accountid=&quot;63e2a2771b13d42998e4e706&quot; rel=&quot;noreferrer&quot;&gt;Marc Johnson&lt;/a&gt;, &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ee89462f7aa140abd82d11d&quot; class=&quot;user-hover&quot; rel=&quot;5ee89462f7aa140abd82d11d&quot; data-account-id=&quot;5ee89462f7aa140abd82d11d&quot; accountid=&quot;5ee89462f7aa140abd82d11d&quot; rel=&quot;noreferrer&quot;&gt;Julian Ladisch&lt;/a&gt;?&lt;/p&gt;</comment>
                                                            <comment id="14943" author="63e2a2771b13d42998e4e706" created="Tue, 28 Jul 2020 12:11:19 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5ed55244bc90a106063c7&quot; class=&quot;user-hover&quot; rel=&quot;5af5ed55244bc90a106063c7&quot; data-account-id=&quot;5af5ed55244bc90a106063c7&quot; accountid=&quot;5af5ed55244bc90a106063c7&quot; rel=&quot;noreferrer&quot;&gt;Cate Boerema&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;In general I think this is ok. &lt;/p&gt;

&lt;p&gt;I believe some of the outstanding issues around this area are for folks expectations around specific searches. How does this fit in with expectations around those?&lt;/p&gt;

&lt;p&gt;For example, when searching for suppressed by discovery yes or no? If we assume that the estimated matching records before applying those filters is less that 10 000, then the margin for cumulative error on the matching record is nearly 1000 (998 I think), in the sense that we might get a count from the two searches using the suppress from discovery filter that have a sum of maybe 1000 different from the total given without the filter.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ee89462f7aa140abd82d11d&quot; class=&quot;user-hover&quot; rel=&quot;5ee89462f7aa140abd82d11d&quot; data-account-id=&quot;5ee89462f7aa140abd82d11d&quot; accountid=&quot;5ee89462f7aa140abd82d11d&quot; rel=&quot;noreferrer&quot;&gt;Julian Ladisch&lt;/a&gt; please do correct my logic if I&apos;ve misunderstood or over simplified this example (I&apos;m mostly ignoring the error in the underlying estimates).&lt;/p&gt;</comment>
                                                            <comment id="14946" author="5af5ed55244bc90a106063c7" created="Tue, 28 Jul 2020 12:40:14 +0000"  >&lt;p&gt;Given the result counts are estimates, I would not expect searching for things like suppressed for discovery y/n to add up.  SMEs would, of course, love for all result counts to be exact and for everything to add up precisely, but my understanding is that simply isn&apos;t possible until we have Elastic search (and, even then, it&apos;s not clear it will be as precise as people would like).  Still, given what we have, I believe that appending the &quot;about&quot; and rounding the estimates will help users to better understand the situation.  I wish the estimates could be more accurate (some are still quite a bit off, percentage-wise) but we need to work with what we have.  Unless you think there is something additional we can do now to help with this?&lt;/p&gt;</comment>
                                                            <comment id="14950" author="5af5ed55244bc90a106063c7" created="Tue, 28 Jul 2020 12:46:59 +0000"  >&lt;blockquote&gt;&lt;p&gt;For example, if we decide that some clients e.g. discovery want to apply their own rounding rules (or not round at all), then that either means the back-end should not round at all, or whether it does or not should be controlled by the client.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=63e2a2771b13d42998e4e706&quot; class=&quot;user-hover&quot; rel=&quot;63e2a2771b13d42998e4e706&quot; data-account-id=&quot;63e2a2771b13d42998e4e706&quot; accountid=&quot;63e2a2771b13d42998e4e706&quot; rel=&quot;noreferrer&quot;&gt;Marc Johnson&lt;/a&gt; I wouldn&apos;t think discovery systems would rely on FOLIO for result counts at all.  But &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5cf6c546b87c300f36eb7b9a&quot; class=&quot;user-hover&quot; rel=&quot;5cf6c546b87c300f36eb7b9a&quot; data-account-id=&quot;5cf6c546b87c300f36eb7b9a&quot; accountid=&quot;5cf6c546b87c300f36eb7b9a&quot; rel=&quot;noreferrer&quot;&gt;Craig McNally&lt;/a&gt; may have some insight into whether this kind of data would be used by discovery or other integrations.&lt;/p&gt;</comment>
                                                            <comment id="14953" author="63e2a2771b13d42998e4e706" created="Tue, 28 Jul 2020 13:34:34 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5ed55244bc90a106063c7&quot; class=&quot;user-hover&quot; rel=&quot;5af5ed55244bc90a106063c7&quot; data-account-id=&quot;5af5ed55244bc90a106063c7&quot; accountid=&quot;5af5ed55244bc90a106063c7&quot; rel=&quot;noreferrer&quot;&gt;Cate Boerema&lt;/a&gt;&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;I wouldn&apos;t think discovery systems would rely on FOLIO for result counts at all&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Where would you expect discovery systems to get the information from?&lt;/p&gt;

&lt;p&gt;As I understand it, the OAI-PMH and RTAC modules are being used by discovery systems, is that not the case?&lt;/p&gt;

&lt;p&gt;cc: &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=70121%3Ae70f578f-dc5a-4a30-8836-fc2418025d21&quot; class=&quot;user-hover&quot; rel=&quot;70121:e70f578f-dc5a-4a30-8836-fc2418025d21&quot; data-account-id=&quot;70121:e70f578f-dc5a-4a30-8836-fc2418025d21&quot; accountid=&quot;70121:e70f578f-dc5a-4a30-8836-fc2418025d21&quot; rel=&quot;noreferrer&quot;&gt;Matt Reno&lt;/a&gt;&lt;/p&gt;</comment>
                                                            <comment id="14955" author="557058:f80403de-e149-421e-8750-af45c853402f" created="Tue, 28 Jul 2020 14:34:21 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=63e2a2771b13d42998e4e706&quot; class=&quot;user-hover&quot; rel=&quot;63e2a2771b13d42998e4e706&quot; data-account-id=&quot;63e2a2771b13d42998e4e706&quot; accountid=&quot;63e2a2771b13d42998e4e706&quot; rel=&quot;noreferrer&quot;&gt;Marc Johnson&lt;/a&gt;, &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5ed55244bc90a106063c7&quot; class=&quot;user-hover&quot; rel=&quot;5af5ed55244bc90a106063c7&quot; data-account-id=&quot;5af5ed55244bc90a106063c7&quot; accountid=&quot;5af5ed55244bc90a106063c7&quot; rel=&quot;noreferrer&quot;&gt;Cate Boerema&lt;/a&gt; is right, discovery systems &lt;b&gt;do not rely&lt;/b&gt; on FOLIO search result count. E.g. has &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5cd423bebc70090d6ce241b1&quot; class=&quot;user-hover&quot; rel=&quot;5cd423bebc70090d6ce241b1&quot; data-account-id=&quot;5cd423bebc70090d6ce241b1&quot; accountid=&quot;5cd423bebc70090d6ce241b1&quot; rel=&quot;noreferrer&quot;&gt;Ian Hardy&lt;/a&gt; when setting up VuFind for the Simmons library, elegantly implemented facetted search - see: &lt;br/&gt;
&lt;a href=&quot;https://libcat.simmons.edu&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://libcat.simmons.edu&lt;/a&gt;&lt;/p&gt;
</comment>
                                                            <comment id="14959" author="557058:f80403de-e149-421e-8750-af45c853402f" created="Tue, 28 Jul 2020 14:42:08 +0000"  >&lt;blockquote&gt;&lt;p&gt;&lt;br/&gt;
Given the result counts are estimates, I would not expect searching for things like suppressed for discovery y/n to add up. SMEs would, of course, love for all result counts to be exact and for everything to add up precisely, but my understanding is that simply isn&apos;t possible until we have Elastic search (and, even then, it&apos;s not clear it will be as precise as people would like). &lt;b&gt;Still, given what we have, I believe that appending the &quot;about&quot; and rounding the estimates will help users to better understand&lt;/b&gt; the situation. I wish the estimates could be more accurate (some are still quite a bit off, percentage-wise) but we &lt;em&gt;need to work with what we have&lt;/em&gt;. Unless you think there is something additional we can do now to help with this?&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;I agree with your comments above &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5ed55244bc90a106063c7&quot; class=&quot;user-hover&quot; rel=&quot;5af5ed55244bc90a106063c7&quot; data-account-id=&quot;5af5ed55244bc90a106063c7&quot; accountid=&quot;5af5ed55244bc90a106063c7&quot; rel=&quot;noreferrer&quot;&gt;Cate Boerema&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;When would we know if Elastic Search would be a much better option, and be much more precise than what we have today?&lt;/p&gt;

&lt;p&gt;CC: &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=70121%3Abe36acda-040d-4925-b3df-ebd7e16d4b5b&quot; class=&quot;user-hover&quot; rel=&quot;70121:be36acda-040d-4925-b3df-ebd7e16d4b5b&quot; data-account-id=&quot;70121:be36acda-040d-4925-b3df-ebd7e16d4b5b&quot; accountid=&quot;70121:be36acda-040d-4925-b3df-ebd7e16d4b5b&quot; rel=&quot;noreferrer&quot;&gt;lew235&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=712020%3A363234f4-7171-418a-92d6-83fbb9f543fc&quot; class=&quot;user-hover&quot; rel=&quot;712020:363234f4-7171-418a-92d6-83fbb9f543fc&quot; data-account-id=&quot;712020:363234f4-7171-418a-92d6-83fbb9f543fc&quot; accountid=&quot;712020:363234f4-7171-418a-92d6-83fbb9f543fc&quot; rel=&quot;noreferrer&quot;&gt;Felix Hemme&lt;/a&gt;&lt;/p&gt;</comment>
                                                            <comment id="14964" author="557058:f80403de-e149-421e-8750-af45c853402f" created="Tue, 28 Jul 2020 14:52:12 +0000"  >&lt;p&gt;Sorry - I&apos;m working my way backwards on today&apos;s comments in this thread. But to your suggestion above &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5ed55244bc90a106063c7&quot; class=&quot;user-hover&quot; rel=&quot;5af5ed55244bc90a106063c7&quot; data-account-id=&quot;5af5ed55244bc90a106063c7&quot; accountid=&quot;5af5ed55244bc90a106063c7&quot; rel=&quot;noreferrer&quot;&gt;Cate Boerema&lt;/a&gt; - &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-2648?focusedCommentId=14940&amp;amp;page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://folio-org.atlassian.net/browse/FOLIO-2648?focusedCommentId=14940&amp;amp;page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&lt;/a&gt; - then &lt;b&gt;I agree&lt;/b&gt;. &lt;/p&gt;

&lt;p&gt;Using result count to be rounded using the &quot;Rounded to first digit&quot; method - is aligned with my comment on 6/18/2020 - &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-2648?focusedCommentId=14890&amp;amp;page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://folio-org.atlassian.net/browse/FOLIO-2648?focusedCommentId=14890&amp;amp;page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;CC: &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=70121%3Abe36acda-040d-4925-b3df-ebd7e16d4b5b&quot; class=&quot;user-hover&quot; rel=&quot;70121:be36acda-040d-4925-b3df-ebd7e16d4b5b&quot; data-account-id=&quot;70121:be36acda-040d-4925-b3df-ebd7e16d4b5b&quot; accountid=&quot;70121:be36acda-040d-4925-b3df-ebd7e16d4b5b&quot; rel=&quot;noreferrer&quot;&gt;lew235&lt;/a&gt; &lt;/p&gt;</comment>
                                                            <comment id="14967" author="63e2a2771b13d42998e4e706" created="Tue, 28 Jul 2020 14:52:21 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5ed55244bc90a106063c7&quot; class=&quot;user-hover&quot; rel=&quot;5af5ed55244bc90a106063c7&quot; data-account-id=&quot;5af5ed55244bc90a106063c7&quot; accountid=&quot;5af5ed55244bc90a106063c7&quot; rel=&quot;noreferrer&quot;&gt;Cate Boerema&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Af80403de-e149-421e-8750-af45c853402f&quot; class=&quot;user-hover&quot; rel=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; data-account-id=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; accountid=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; rel=&quot;noreferrer&quot;&gt;Charlotte Whitt&lt;/a&gt;&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5ed55244bc90a106063c7&quot; class=&quot;user-hover&quot; rel=&quot;5af5ed55244bc90a106063c7&quot; data-account-id=&quot;5af5ed55244bc90a106063c7&quot; accountid=&quot;5af5ed55244bc90a106063c7&quot; rel=&quot;noreferrer&quot;&gt;Cate Boerema&lt;/a&gt; is right, discovery systems do not rely on FOLIO search result count.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Does that mean that we are comfortable assuming that no external systems are going to use FOLIOs record counts and so the only audience for this change is the internal, staff oriented reference UI?&lt;/p&gt;
</comment>
                                                            <comment id="14970" author="70121:e70f578f-dc5a-4a30-8836-fc2418025d21" created="Tue, 28 Jul 2020 15:04:32 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=63e2a2771b13d42998e4e706&quot; class=&quot;user-hover&quot; rel=&quot;63e2a2771b13d42998e4e706&quot; data-account-id=&quot;63e2a2771b13d42998e4e706&quot; accountid=&quot;63e2a2771b13d42998e4e706&quot; rel=&quot;noreferrer&quot;&gt;Marc Johnson&lt;/a&gt; the current RTAC implementation in FOLIO, which is used by EDS, does not use or report record counts. The API returns RTAC info for a specified instance ID and we retrieve with limit set to Integer.MAX_VALUE instead of paging.&lt;/p&gt;

&lt;p&gt;However, we are using counts for the EBSCO Analytics project in order to extract data from FOLIO and possibly for stats. If the counts are not accurate, then we may not be retrieving everything as expected. I guess we&apos;ll need to be aware of this when paging and maybe come up with another approach to know when we are done retrieving all pages.&lt;/p&gt;</comment>
                                                            <comment id="14975" author="615afd1cd9820f0070a09ef0" created="Tue, 28 Jul 2020 15:14:32 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=70121%3Ae70f578f-dc5a-4a30-8836-fc2418025d21&quot; class=&quot;user-hover&quot; rel=&quot;70121:e70f578f-dc5a-4a30-8836-fc2418025d21&quot; data-account-id=&quot;70121:e70f578f-dc5a-4a30-8836-fc2418025d21&quot; accountid=&quot;70121:e70f578f-dc5a-4a30-8836-fc2418025d21&quot; rel=&quot;noreferrer&quot;&gt;Matt Reno&lt;/a&gt;: &lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;If the counts are not accurate, then we may not be retrieving everything as expected. I guess we&apos;ll need to be aware of this when paging and maybe come up with another approach to know when we are done retrieving all pages.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Discussion at SUP-8; we face the same dilemma in the UI WRT how to handle paging. &lt;/p&gt;</comment>
                                                            <comment id="14978" author="5af5ed55244bc90a106063c7" created="Tue, 28 Jul 2020 15:28:28 +0000"  >&lt;blockquote&gt;&lt;p&gt;When would we know if Elastic Search would be a much better option, and be much more precise than what we have today?&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Af80403de-e149-421e-8750-af45c853402f&quot; class=&quot;user-hover&quot; rel=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; data-account-id=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; accountid=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; rel=&quot;noreferrer&quot;&gt;Charlotte Whitt&lt;/a&gt;, my understanding is that the Shanghai folks are working on a proof of concept for Elastic search in Q3.  I hope we will know more about result count precision when that is available.&lt;/p&gt;

&lt;p&gt;FYI &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ff60d224d2179006ebd8a15&quot; class=&quot;user-hover&quot; rel=&quot;5ff60d224d2179006ebd8a15&quot; data-account-id=&quot;5ff60d224d2179006ebd8a15&quot; accountid=&quot;5ff60d224d2179006ebd8a15&quot; rel=&quot;noreferrer&quot;&gt;twliu&lt;/a&gt;&lt;/p&gt;
</comment>
                                                            <comment id="14980" author="5af5ed55244bc90a106063c7" created="Tue, 28 Jul 2020 15:35:54 +0000"  >&lt;p&gt;I just restructured the description of this issue to include the scenarios.  I&apos;m thinking we can just use this as our development story now (unless this actually spins off several stories).  Thoughts? &lt;/p&gt;

&lt;p&gt;BTW,when I was reorganizing the content, I noticed that, in the last sentence of the description, Julian wrote &quot;This issue is about deciding whether there should be a FOLIO standard for rounding, and if yes, which to choose. If the decision has been made &lt;b&gt;Stripes should provide a round function to be used by all front-end modules&lt;/b&gt;.&quot;  Another vote for doing this on the frontend, I guess.&lt;/p&gt;


</comment>
                                                            <comment id="14983" author="63e2a2771b13d42998e4e706" created="Tue, 28 Jul 2020 15:42:29 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5ed55244bc90a106063c7&quot; class=&quot;user-hover&quot; rel=&quot;5af5ed55244bc90a106063c7&quot; data-account-id=&quot;5af5ed55244bc90a106063c7&quot; accountid=&quot;5af5ed55244bc90a106063c7&quot; rel=&quot;noreferrer&quot;&gt;Cate Boerema&lt;/a&gt;&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;I&apos;m thinking we can just use this as our development story now (unless this actually spins off several stories). Thoughts?&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;I think if it has been decided that we should do the rounding on the front end, then I think &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=615afd1cd9820f0070a09ef0&quot; class=&quot;user-hover&quot; rel=&quot;615afd1cd9820f0070a09ef0&quot; data-account-id=&quot;615afd1cd9820f0070a09ef0&quot; accountid=&quot;615afd1cd9820f0070a09ef0&quot; rel=&quot;noreferrer&quot;&gt;Zak Burke&lt;/a&gt; is probably best placed to outline what would be involved in achieving that.&lt;/p&gt;

&lt;p&gt;I think it is likely that any work be blocked on both 
    &lt;span class=&quot;jira-issue-macro&quot; data-jira-key=&quot;RMB-578&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/RMB-578&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Inform whether totalRecords is exact or an estimate&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10322?size=medium&quot; /&gt;
            RMB-578
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-complete jira-macro-single-issue-export-pdf&quot;&gt;Blocked&lt;/span&gt;
            &lt;/span&gt;
 and it being implemented by at least one (probably mod-inventory-storage) module.&lt;/p&gt;

&lt;p&gt;I think we should be aware that this means that any client that is not the reference UI might present different information from the same searches.&lt;/p&gt;

&lt;p&gt;(I&apos;d like someone like &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5cf6c546b87c300f36eb7b9a&quot; class=&quot;user-hover&quot; rel=&quot;5cf6c546b87c300f36eb7b9a&quot; data-account-id=&quot;5cf6c546b87c300f36eb7b9a&quot; accountid=&quot;5cf6c546b87c300f36eb7b9a&quot; rel=&quot;noreferrer&quot;&gt;Craig McNally&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5cf6c265e7d2310e9fc0c5ac&quot; class=&quot;user-hover&quot; rel=&quot;5cf6c265e7d2310e9fc0c5ac&quot; data-account-id=&quot;5cf6c265e7d2310e9fc0c5ac&quot; accountid=&quot;5cf6c265e7d2310e9fc0c5ac&quot; rel=&quot;noreferrer&quot;&gt;VBar&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=615afd1cd9820f0070a09ef0&quot; class=&quot;user-hover&quot; rel=&quot;615afd1cd9820f0070a09ef0&quot; data-account-id=&quot;615afd1cd9820f0070a09ef0&quot; accountid=&quot;615afd1cd9820f0070a09ef0&quot; rel=&quot;noreferrer&quot;&gt;Zak Burke&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ae08bd47b44642d39d323c4&quot; class=&quot;user-hover&quot; rel=&quot;5ae08bd47b44642d39d323c4&quot; data-account-id=&quot;5ae08bd47b44642d39d323c4&quot; accountid=&quot;5ae08bd47b44642d39d323c4&quot; rel=&quot;noreferrer&quot;&gt;Mike Gorrell&lt;/a&gt; to maybe comment here as to whether we think this kind of decision needs any technical governance from the Technical Council or Leads)&lt;/p&gt;</comment>
                                                            <comment id="14986" author="5ee89462f7aa140abd82d11d" created="Tue, 28 Jul 2020 15:49:34 +0000"  >&lt;p&gt;I no longer advocate for front-end rounding (and removed my sentence from the issue description that the front-end should round).&lt;br/&gt;
If the back-end calculates and sends the rounded estimates it has these advantages:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Consistency: The same query shows the same number everywhere (in internal and external software).&lt;/li&gt;
	&lt;li&gt;The back-end may adjust the rounding. PostgreSQL allows to set the sample size separately for each database index resulting in more accurate estimates; this may allow for rounding to first 2 digits or some other rounding scheme.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;This is not a strong advantage of back-end rounding so I will also be happy with front-end rounding.&lt;/p&gt;

&lt;p&gt;The back-end APIs are designed to be used by external software and will be used by external software.&lt;/p&gt;

&lt;p&gt;If the back-end rounds it should also provide to original (non-rounded) estimate, for example&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
totalRecords: 1431
totalRecordsRounded: 1000
totalRecordsEstimated: &lt;span class=&quot;code-keyword&quot;&gt;true&lt;/span&gt;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;No rounding is needed for an exact number:&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
totalRecords: 1509
totalRecordsEstimated: &lt;span class=&quot;code-keyword&quot;&gt;false&lt;/span&gt;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;(Q3 2020 will have &quot;totalRecordsEstimated&quot; flag 
    &lt;span class=&quot;jira-issue-macro&quot; data-jira-key=&quot;RMB-578&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/RMB-578&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Inform whether totalRecords is exact or an estimate&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10322?size=medium&quot; /&gt;
            RMB-578
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-complete jira-macro-single-issue-export-pdf&quot;&gt;Blocked&lt;/span&gt;
            &lt;/span&gt;
.)&lt;br/&gt;
If I have collected the history of the estimated count of some query I&apos;d rather have the original estimated numbers (1263, 1362, 1473, 1594) than the rounded numbers (1000, 1000, 1000, 2000).&lt;br/&gt;
If a table is sorted by estimates the front-end may sort by the original (non-rounded) estimate even if only the rounded estimate is shown.&lt;/p&gt;</comment>
                                                            <comment id="14988" author="63e2a2771b13d42998e4e706" created="Tue, 28 Jul 2020 16:07:19 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ee89462f7aa140abd82d11d&quot; class=&quot;user-hover&quot; rel=&quot;5ee89462f7aa140abd82d11d&quot; data-account-id=&quot;5ee89462f7aa140abd82d11d&quot; accountid=&quot;5ee89462f7aa140abd82d11d&quot; rel=&quot;noreferrer&quot;&gt;Julian Ladisch&lt;/a&gt;&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;Consistency: The same query shows the same number everywhere (in internal and external software).&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;I agree that this is the most important aspect of the back end vs. front end technical decision.&lt;/p&gt;

&lt;p&gt;My questions about external systems like discovery were to try to explore whether this consistency was desirable, or if it might even be problematic.&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;If the back-end rounds it should also provide to original (non-rounded) estimate&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;This is interesting, because it would allow and require a client to make the choice. If we chose this design, there would need to be front end work as well.&lt;/p&gt;

&lt;p&gt;I&apos;ll admit I was premature in assuming the client would be ignorant of the rounding and they would only receive an already rounded estimate.&lt;/p&gt;</comment>
                                                            <comment id="14991" author="5ae08bd47b44642d39d323c4" created="Tue, 28 Jul 2020 16:46:39 +0000"  >&lt;p&gt;My take would be to do it on the backend for the reasons Julian stated (consistency internally or externally). And it feels like a core team decision to me.&lt;/p&gt;</comment>
                                                            <comment id="14993" author="5ee89462f7aa140abd82d11d" created="Wed, 29 Jul 2020 08:00:17 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=63e2a2771b13d42998e4e706&quot; class=&quot;user-hover&quot; rel=&quot;63e2a2771b13d42998e4e706&quot; data-account-id=&quot;63e2a2771b13d42998e4e706&quot; accountid=&quot;63e2a2771b13d42998e4e706&quot; rel=&quot;noreferrer&quot;&gt;Marc Johnson&lt;/a&gt; We cannot avoid front-end work. We need at least this logic:&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
&lt;span class=&quot;code-keyword&quot;&gt;if&lt;/span&gt; totalRecordsEstimated is &lt;span class=&quot;code-keyword&quot;&gt;true&lt;/span&gt;
  print &lt;span class=&quot;code-quote&quot;&gt;&quot;about &quot;&lt;/span&gt; + totalRecordsRounded
&lt;span class=&quot;code-keyword&quot;&gt;else&lt;/span&gt; &lt;span class=&quot;code-keyword&quot;&gt;if&lt;/span&gt; totalRecordsEstimated is &lt;span class=&quot;code-keyword&quot;&gt;false&lt;/span&gt;
  print totalRecords
&lt;span class=&quot;code-comment&quot;&gt;// totalRecordsEstimated is undefined until all back-ends have upgraded RMB,
&lt;/span&gt;&lt;span class=&quot;code-comment&quot;&gt;// handle &lt;span class=&quot;code-keyword&quot;&gt;this&lt;/span&gt; gracefully &lt;span class=&quot;code-keyword&quot;&gt;for&lt;/span&gt; folio-testing:
&lt;/span&gt;&lt;span class=&quot;code-keyword&quot;&gt;else&lt;/span&gt; &lt;span class=&quot;code-keyword&quot;&gt;if&lt;/span&gt; totalRecords &amp;lt; 1000
  print totalRecords
&lt;span class=&quot;code-keyword&quot;&gt;else&lt;/span&gt;
  print &lt;span class=&quot;code-quote&quot;&gt;&quot;about &quot;&lt;/span&gt; + totalRecords + &lt;span class=&quot;code-quote&quot;&gt;&quot; (upgrade back-end &lt;span class=&quot;code-keyword&quot;&gt;for&lt;/span&gt; rounding)&quot;&lt;/span&gt;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</comment>
                                                            <comment id="14996" author="5af5ed55244bc90a106063c7" created="Wed, 29 Jul 2020 09:47:30 +0000"  >&lt;p&gt;Thanks guys!  It sounds like there will be several stories needed, so this one should probably be converted to a UXPROD feature, rather than a dev story.&lt;/p&gt;

&lt;p&gt;Are these the stories that would define the feature?  Who can tell me if it&apos;s possible to get the &quot;totalRecordsRounded&quot; done in Q3?&lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;&quot;totalRecordsEstimated&quot; flag 
    &lt;span class=&quot;jira-issue-macro&quot; data-jira-key=&quot;RMB-578&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/RMB-578&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Inform whether totalRecords is exact or an estimate&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10322?size=medium&quot; /&gt;
            RMB-578
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-complete jira-macro-single-issue-export-pdf&quot;&gt;Blocked&lt;/span&gt;
            &lt;/span&gt;
, Core Platform, Q3 2020&lt;/li&gt;
	&lt;li&gt;&quot;totalRecordsRounded&quot; value RMB-???, Core Platform, Q? 2020&lt;/li&gt;
	&lt;li&gt;Round estimated search result hit count, UIIN-???, Core Functional, Q? 2020 (dependent on previous story)&lt;/li&gt;
&lt;/ul&gt;
</comment>
                                                            <comment id="14998" author="5ee89462f7aa140abd82d11d" created="Wed, 29 Jul 2020 10:46:49 +0000"  >&lt;p&gt;Yes, Q3 2020 is possible, 
    &lt;span class=&quot;jira-issue-macro&quot; data-jira-key=&quot;RMB-578&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/RMB-578&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Inform whether totalRecords is exact or an estimate&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10322?size=medium&quot; /&gt;
            RMB-578
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-complete jira-macro-single-issue-export-pdf&quot;&gt;Blocked&lt;/span&gt;
            &lt;/span&gt;
 (totalRecordsEstimated) and 
    &lt;span class=&quot;jira-issue-macro&quot; data-jira-key=&quot;RMB-685&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/RMB-685&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;totalRecordsRounded&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10322?size=medium&quot; /&gt;
            RMB-685
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-complete jira-macro-single-issue-export-pdf&quot;&gt;Blocked&lt;/span&gt;
            &lt;/span&gt;
 (totalRecordsRounded) are scheduled for this or next core platform sprint.&lt;/p&gt;</comment>
                                                            <comment id="15000" author="63e2a2771b13d42998e4e706" created="Wed, 29 Jul 2020 10:49:04 +0000"  >&lt;blockquote&gt;&lt;p&gt;Yes, Q3 2020 is possible, 
    &lt;span class=&quot;jira-issue-macro&quot; data-jira-key=&quot;RMB-578&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/RMB-578&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Inform whether totalRecords is exact or an estimate&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10322?size=medium&quot; /&gt;
            RMB-578
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-complete jira-macro-single-issue-export-pdf&quot;&gt;Blocked&lt;/span&gt;
            &lt;/span&gt;
 (totalRecordsEstimated) and 
    &lt;span class=&quot;jira-issue-macro&quot; data-jira-key=&quot;RMB-685&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/RMB-685&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;totalRecordsRounded&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10322?size=medium&quot; /&gt;
            RMB-685
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-complete jira-macro-single-issue-export-pdf&quot;&gt;Blocked&lt;/span&gt;
            &lt;/span&gt;
 (totalRecordsRounded) are scheduled for this or next core platform sprint.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Does that mean that it has been decided that the rounding will be done by the back end?&lt;/p&gt;</comment>
                                                            <comment id="15002" author="5ee89462f7aa140abd82d11d" created="Wed, 29 Jul 2020 10:59:37 +0000"  >&lt;p&gt;No, but 
    &lt;span class=&quot;jira-issue-macro&quot; data-jira-key=&quot;RMB-578&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/RMB-578&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Inform whether totalRecords is exact or an estimate&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10322?size=medium&quot; /&gt;
            RMB-578
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-complete jira-macro-single-issue-export-pdf&quot;&gt;Blocked&lt;/span&gt;
            &lt;/span&gt;
 and 
    &lt;span class=&quot;jira-issue-macro&quot; data-jira-key=&quot;RMB-685&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/RMB-685&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;totalRecordsRounded&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10322?size=medium&quot; /&gt;
            RMB-685
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-complete jira-macro-single-issue-export-pdf&quot;&gt;Blocked&lt;/span&gt;
            &lt;/span&gt;
 should be worked on at the same time and we need the 
    &lt;span class=&quot;jira-issue-macro&quot; data-jira-key=&quot;RMB-685&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/RMB-685&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;totalRecordsRounded&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10322?size=medium&quot; /&gt;
            RMB-685
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-complete jira-macro-single-issue-export-pdf&quot;&gt;Blocked&lt;/span&gt;
            &lt;/span&gt;
 Jira for capacity planning.&lt;/p&gt;</comment>
                                                            <comment id="15004" author="63e2a2771b13d42998e4e706" created="Wed, 29 Jul 2020 11:23:30 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ee89462f7aa140abd82d11d&quot; class=&quot;user-hover&quot; rel=&quot;5ee89462f7aa140abd82d11d&quot; data-account-id=&quot;5ee89462f7aa140abd82d11d&quot; accountid=&quot;5ee89462f7aa140abd82d11d&quot; rel=&quot;noreferrer&quot;&gt;Julian Ladisch&lt;/a&gt;&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;No, but 
    &lt;span class=&quot;jira-issue-macro&quot; data-jira-key=&quot;RMB-578&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/RMB-578&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Inform whether totalRecords is exact or an estimate&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10322?size=medium&quot; /&gt;
            RMB-578
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-complete jira-macro-single-issue-export-pdf&quot;&gt;Blocked&lt;/span&gt;
            &lt;/span&gt;
 and 
    &lt;span class=&quot;jira-issue-macro&quot; data-jira-key=&quot;RMB-685&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/RMB-685&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;totalRecordsRounded&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10322?size=medium&quot; /&gt;
            RMB-685
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-complete jira-macro-single-issue-export-pdf&quot;&gt;Blocked&lt;/span&gt;
            &lt;/span&gt;
 should be worked on at the same time and we need the 
    &lt;span class=&quot;jira-issue-macro&quot; data-jira-key=&quot;RMB-685&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/RMB-685&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;totalRecordsRounded&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10322?size=medium&quot; /&gt;
            RMB-685
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-complete jira-macro-single-issue-export-pdf&quot;&gt;Blocked&lt;/span&gt;
            &lt;/span&gt;
 Jira for capacity planning.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;If they need to be worked on at the same time, does that mean that work on informing the client whether the total record count is an estimate or not is blocked upon a decision as to where to do the rounding?&lt;/p&gt;</comment>
                                                            <comment id="15006" author="5af5ed55244bc90a106063c7" created="Wed, 29 Jul 2020 13:16:51 +0000"  >&lt;blockquote&gt;&lt;p&gt;Does that mean that it has been decided that the rounding will be done by the back end?&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=63e2a2771b13d42998e4e706&quot; class=&quot;user-hover&quot; rel=&quot;63e2a2771b13d42998e4e706&quot; data-account-id=&quot;63e2a2771b13d42998e4e706&quot; accountid=&quot;63e2a2771b13d42998e4e706&quot; rel=&quot;noreferrer&quot;&gt;Marc Johnson&lt;/a&gt; do you have an objection to doing it on the back end?  If not, let&apos;s just do that since &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ee89462f7aa140abd82d11d&quot; class=&quot;user-hover&quot; rel=&quot;5ee89462f7aa140abd82d11d&quot; data-account-id=&quot;5ee89462f7aa140abd82d11d&quot; accountid=&quot;5ee89462f7aa140abd82d11d&quot; rel=&quot;noreferrer&quot;&gt;Julian Ladisch&lt;/a&gt; and &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ae08bd47b44642d39d323c4&quot; class=&quot;user-hover&quot; rel=&quot;5ae08bd47b44642d39d323c4&quot; data-account-id=&quot;5ae08bd47b44642d39d323c4&quot; accountid=&quot;5ae08bd47b44642d39d323c4&quot; rel=&quot;noreferrer&quot;&gt;Mike Gorrell&lt;/a&gt; prefer that approach.  &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=615afd1cd9820f0070a09ef0&quot; class=&quot;user-hover&quot; rel=&quot;615afd1cd9820f0070a09ef0&quot; data-account-id=&quot;615afd1cd9820f0070a09ef0&quot; accountid=&quot;615afd1cd9820f0070a09ef0&quot; rel=&quot;noreferrer&quot;&gt;Zak Burke&lt;/a&gt; has said it doesn&apos;t matter to him either way.  &lt;/p&gt;</comment>
                                                            <comment id="15008" author="63e2a2771b13d42998e4e706" created="Wed, 29 Jul 2020 14:45:52 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5ed55244bc90a106063c7&quot; class=&quot;user-hover&quot; rel=&quot;5af5ed55244bc90a106063c7&quot; data-account-id=&quot;5af5ed55244bc90a106063c7&quot; accountid=&quot;5af5ed55244bc90a106063c7&quot; rel=&quot;noreferrer&quot;&gt;Cate Boerema&lt;/a&gt;&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;do you have an objection to doing it on the back end? If not, let&apos;s just do that since &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ee89462f7aa140abd82d11d&quot; class=&quot;user-hover&quot; rel=&quot;5ee89462f7aa140abd82d11d&quot; data-account-id=&quot;5ee89462f7aa140abd82d11d&quot; accountid=&quot;5ee89462f7aa140abd82d11d&quot; rel=&quot;noreferrer&quot;&gt;Julian Ladisch&lt;/a&gt; and &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ae08bd47b44642d39d323c4&quot; class=&quot;user-hover&quot; rel=&quot;5ae08bd47b44642d39d323c4&quot; data-account-id=&quot;5ae08bd47b44642d39d323c4&quot; accountid=&quot;5ae08bd47b44642d39d323c4&quot; rel=&quot;noreferrer&quot;&gt;Mike Gorrell&lt;/a&gt; prefer that approach. &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=615afd1cd9820f0070a09ef0&quot; class=&quot;user-hover&quot; rel=&quot;615afd1cd9820f0070a09ef0&quot; data-account-id=&quot;615afd1cd9820f0070a09ef0&quot; accountid=&quot;615afd1cd9820f0070a09ef0&quot; rel=&quot;noreferrer&quot;&gt;Zak Burke&lt;/a&gt; has said it doesn&apos;t matter to him either way.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;I don&apos;t have any objections to this. I think it is important that we are confident about the need for consistency. If we choose to make this opaque to clients by using the same property (&lt;tt&gt;totalRecords&lt;/tt&gt;) then clients have no choice and so it will be consistent. If we choose to have separate properties for rounded and non-rounded values then the client may choose and so could be inconsistent.&lt;/p&gt;

&lt;p&gt;Does that make sense?&lt;/p&gt;</comment>
                                                            <comment id="15012" author="5ee89462f7aa140abd82d11d" created="Wed, 29 Jul 2020 15:02:34 +0000"  >&lt;p&gt;This cannot be opaque to the client because the client needs to check the &lt;tt&gt;totalRecordsEstimated&lt;/tt&gt; property to decide whether to add &quot;about &quot; or the translation of &quot;about &quot; to the number.&lt;/p&gt;</comment>
                                                            <comment id="15013" author="63e2a2771b13d42998e4e706" created="Wed, 29 Jul 2020 15:33:35 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ee89462f7aa140abd82d11d&quot; class=&quot;user-hover&quot; rel=&quot;5ee89462f7aa140abd82d11d&quot; data-account-id=&quot;5ee89462f7aa140abd82d11d&quot; accountid=&quot;5ee89462f7aa140abd82d11d&quot; rel=&quot;noreferrer&quot;&gt;Julian Ladisch&lt;/a&gt;&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;This cannot be opaque to the client because the client needs to check the totalRecordsEstimated property to decide whether to add &quot;about &quot; or the translation of &quot;about &quot; to the number.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Apologies for being vague with my scope, I was referring only to the rounding aspect of this, not whether the record count is estimated or not (which I believe is already being worked on and I consider somewhat separate)&lt;/p&gt;</comment>
                                                            <comment id="15016" author="63e2a2771b13d42998e4e706" created="Mon, 10 Aug 2020 13:50:17 +0000"  >&lt;p&gt;Has a decision been made about where FOLIO is going to round the record counts and what impact that has on clients?&lt;/p&gt;</comment>
                                                            <comment id="15018" author="63e2a2771b13d42998e4e706" created="Tue, 11 Aug 2020 14:07:32 +0000"  >&lt;blockquote&gt;&lt;p&gt;Consistency: The same query shows the same number everywhere (in internal and external software).&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;It has been expressed by folks that an important aspect of doing this work on the back end is consistency. I think we need to decide what we mean by consistency.&lt;/p&gt;

&lt;p&gt;The proposed API design for this rounding distinguishes between rounded and not rounded totals (by including two properties &lt;tt&gt;totalRecords&lt;/tt&gt; and &lt;tt&gt;totalRecordsRounded&lt;/tt&gt;).&lt;/p&gt;

&lt;p&gt;This means that it is transparent to the client and which value is used it at the discretion of the individual client. Some clients may choose to present the rounded number, others the unrounded and others may choose to apply their own rounding to the unrounded number.&lt;/p&gt;

&lt;p&gt;I had thought of consistency to mean that we expected the same value to be presented for the same question irrespective of the client. It is entirely possible I misunderstood the use in this context. &lt;/p&gt;

&lt;p&gt;What degree of consistency are folks wanting to achieve?&lt;/p&gt;</comment>
                                                            <comment id="15020" author="5ee89462f7aa140abd82d11d" created="Tue, 11 Aug 2020 15:00:48 +0000"  >&lt;p&gt;If the clients should do the rounding we need to duplicate the rounding code for each client. Some clients may implement a different rounding algorithm (see A, B, and C in this issue desciption), or may incorrectly implement the correct rounding algorithm; this results in different numbers for the same query = inconsisteny.&lt;/p&gt;

&lt;p&gt;Some clients may implement a minimal viable product without any rounding to avoid the rounding code. If the rounded value is provided by the back-end it is more likely that the developer uses it.&lt;/p&gt;

&lt;p&gt;Improving the rounding algorithm requires to update all clients if rounding is client-side, but does not require any client change if the rounded value is provided by the back-end.&lt;/p&gt;</comment>
                                                            <comment id="15022" author="63e2a2771b13d42998e4e706" created="Wed, 12 Aug 2020 15:01:20 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ee89462f7aa140abd82d11d&quot; class=&quot;user-hover&quot; rel=&quot;5ee89462f7aa140abd82d11d&quot; data-account-id=&quot;5ee89462f7aa140abd82d11d&quot; accountid=&quot;5ee89462f7aa140abd82d11d&quot; rel=&quot;noreferrer&quot;&gt;Julian Ladisch&lt;/a&gt;&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;If the rounded value is provided by the back-end it is more likely that the developer uses it&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;That way well be the case.&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;Improving the rounding algorithm requires to update all clients if rounding is client-side, but does not require any client change if the rounded value is provided by the back-end.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;An inherent part of the proposed design is that the clients can choose between the existing &lt;tt&gt;totalRecords&lt;/tt&gt; and the new &lt;tt&gt;totalRecordsRounded&lt;/tt&gt; that means that there is work for any existing client to support rounding. It also means that clients can choose to implement their own rounding algorithm at any point in the future.&lt;/p&gt;</comment>
                                                            <comment id="15024" author="5af5ed55244bc90a106063c7" created="Mon, 17 Aug 2020 10:52:49 +0000"  >&lt;p&gt;Hi guys.  Based on &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ee89462f7aa140abd82d11d&quot; class=&quot;user-hover&quot; rel=&quot;5ee89462f7aa140abd82d11d&quot; data-account-id=&quot;5ee89462f7aa140abd82d11d&quot; accountid=&quot;5ee89462f7aa140abd82d11d&quot; rel=&quot;noreferrer&quot;&gt;Julian Ladisch&lt;/a&gt;&apos;s comments, I converted this to a UXPROD feature and assigned it to Core Platform for Q3 2020.  I linked 3 RMB issues as defining this feature (this feature won&apos;t be done until all 3 of those issues are complete).&lt;/p&gt;

&lt;p&gt;Are there additional stories needed?  Do we need something for the front end to make use of this new data?&lt;/p&gt;

&lt;p&gt;Is Core Platform still tracking to have this done for Q3?&lt;/p&gt;


&lt;p&gt;Thanks much!&lt;/p&gt;

&lt;p&gt;FYI &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ab8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; class=&quot;user-hover&quot; rel=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; data-account-id=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; accountid=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; rel=&quot;noreferrer&quot;&gt;Jakub Skoczen&lt;/a&gt; and &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Af80403de-e149-421e-8750-af45c853402f&quot; class=&quot;user-hover&quot; rel=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; data-account-id=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; accountid=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; rel=&quot;noreferrer&quot;&gt;Charlotte Whitt&lt;/a&gt;&lt;/p&gt;</comment>
                                                            <comment id="15026" author="63e2a2771b13d42998e4e706" created="Mon, 17 Aug 2020 11:33:25 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5ed55244bc90a106063c7&quot; class=&quot;user-hover&quot; rel=&quot;5af5ed55244bc90a106063c7&quot; data-account-id=&quot;5af5ed55244bc90a106063c7&quot; accountid=&quot;5af5ed55244bc90a106063c7&quot; rel=&quot;noreferrer&quot;&gt;Cate Boerema&lt;/a&gt;&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;Are there additional stories needed? Do we need something for the front end to make use of this new data?&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Assuming we are going with the approach where the back-end introduces a new property (&lt;tt&gt;totalRecordsRounded&lt;/tt&gt;) then yes, we will need UI issues for using this property (at their discretion) rather than &lt;tt&gt;totalRecords&lt;/tt&gt;.&lt;/p&gt;

&lt;p&gt;As the rollout of this will likely be incremental across the various modules and API endpoints, I think we likely need input from &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=615afd1cd9820f0070a09ef0&quot; class=&quot;user-hover&quot; rel=&quot;615afd1cd9820f0070a09ef0&quot; data-account-id=&quot;615afd1cd9820f0070a09ef0&quot; accountid=&quot;615afd1cd9820f0070a09ef0&quot; rel=&quot;noreferrer&quot;&gt;Zak Burke&lt;/a&gt; or &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Aff6a9612-bb35-41b2-88a8-a5b66d0a41a0&quot; class=&quot;user-hover&quot; rel=&quot;557058:ff6a9612-bb35-41b2-88a8-a5b66d0a41a0&quot; data-account-id=&quot;557058:ff6a9612-bb35-41b2-88a8-a5b66d0a41a0&quot; accountid=&quot;557058:ff6a9612-bb35-41b2-88a8-a5b66d0a41a0&quot; rel=&quot;noreferrer&quot;&gt;Michal Kuklis&lt;/a&gt; to advise on whether this can be done in a centralised way in stripes (based upon the presence of properties) or whether it needs to be done for each record type in turn. It&apos;s worth keeping in mind that some endpoints may never provide &lt;tt&gt;totalRecordsRounded&lt;/tt&gt; when we think about how to do this.&lt;/p&gt;

&lt;p&gt;Depending upon how the change is done in RAML Module Builder, then we might also need issues in the various back end modules to expose this in the APIs.&lt;/p&gt;</comment>
                                                            <comment id="15029" author="615afd1cd9820f0070a09ef0" created="Mon, 17 Aug 2020 12:20:03 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5ed55244bc90a106063c7&quot; class=&quot;user-hover&quot; rel=&quot;5af5ed55244bc90a106063c7&quot; data-account-id=&quot;5af5ed55244bc90a106063c7&quot; accountid=&quot;5af5ed55244bc90a106063c7&quot; rel=&quot;noreferrer&quot;&gt;Cate Boerema&lt;/a&gt;, &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=63e2a2771b13d42998e4e706&quot; class=&quot;user-hover&quot; rel=&quot;63e2a2771b13d42998e4e706&quot; data-account-id=&quot;63e2a2771b13d42998e4e706&quot; accountid=&quot;63e2a2771b13d42998e4e706&quot; rel=&quot;noreferrer&quot;&gt;Marc Johnson&lt;/a&gt; is correct that we will need stories across most front-end app modules, as well as stripes-components and stripes-smart-components. &lt;/p&gt;

&lt;p&gt;There are ~70 occurrences that will need to be investigated in  &lt;span class=&quot;nobr&quot;&gt;&lt;a href=&quot;/rest/api/3/attachment/content/10846&quot; title=&quot;total-core.txt attached to UXPROD-2623&quot; data-attachment-type=&quot;file&quot; data-attachment-name=&quot;total-core.txt&quot; data-media-services-type=&quot;file&quot; data-media-services-id=&quot;a988912a-9934-4147-b765-561c7f20e033&quot; rel=&quot;noreferrer&quot;&gt;total-core.txt&lt;sup&gt;&lt;img class=&quot;rendericon&quot; src=&quot;/images/icons/link_attachment_7.gif&quot; height=&quot;7&quot; width=&quot;7&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt;&lt;/sup&gt;&lt;/a&gt;&lt;/span&gt;  and an additional ~40 in  &lt;span class=&quot;nobr&quot;&gt;&lt;a href=&quot;/rest/api/3/attachment/content/10845&quot; title=&quot;total-complete-only.txt attached to UXPROD-2623&quot; data-attachment-type=&quot;file&quot; data-attachment-name=&quot;total-complete-only.txt&quot; data-media-services-type=&quot;file&quot; data-media-services-id=&quot;2b50430b-d27c-4339-b41e-b20db2ea21dd&quot; rel=&quot;noreferrer&quot;&gt;total-complete-only.txt&lt;sup&gt;&lt;img class=&quot;rendericon&quot; src=&quot;/images/icons/link_attachment_7.gif&quot; height=&quot;7&quot; width=&quot;7&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt;&lt;/sup&gt;&lt;/a&gt;&lt;/span&gt; . &lt;/p&gt;</comment>
                                                            <comment id="15031" author="557058:f80403de-e149-421e-8750-af45c853402f" created="Mon, 17 Aug 2020 13:56:56 +0000"  >&lt;p&gt;As I understand it, then at the PC meeting last week (&lt;a href=&quot;https://docs.google.com/document/d/1MpDJGX5wPzJZtqf4bSOge1D9clLLhKIqhIqqTDD87gA/edit&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://docs.google.com/document/d/1MpDJGX5wPzJZtqf4bSOge1D9clLLhKIqhIqqTDD87gA/edit&lt;/a&gt;) Lucy Liu told that the Shanghai Library have come far with their investigation of Elastic Search, and they expect to be able to present the result in Q3 2020 - &lt;/p&gt;

&lt;p&gt;&lt;span class=&quot;image-wrap&quot; style=&quot;&quot;&gt;&lt;img src=&quot;/rest/api/3/attachment/content/10844&quot; height=&quot;183&quot; width=&quot;200&quot; style=&quot;border: 0px solid black&quot; /&gt;&lt;/span&gt;&lt;/p&gt;


&lt;p&gt;See more in: &lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-2592&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://folio-org.atlassian.net/browse/UXPROD-2592&lt;/a&gt;&lt;/p&gt;</comment>
                                                            <comment id="15033" author="5af5ed55244bc90a106063c7" created="Mon, 17 Aug 2020 14:56:01 +0000"  >&lt;blockquote&gt;&lt;p&gt;As I understand it, then at the PC meeting last week (&lt;a href=&quot;https://docs.google.com/document/d/1MpDJGX5wPzJZtqf4bSOge1D9clLLhKIqhIqqTDD87gA/edit&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://docs.google.com/document/d/1MpDJGX5wPzJZtqf4bSOge1D9clLLhKIqhIqqTDD87gA/edit&lt;/a&gt;) Lucy Liu told that the Shanghai Library have come far with their investigation of Elastic Search, and they expect to be able to present the result in Q3 2020 -&lt;/p&gt;

&lt;p&gt;See more in: &lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-2592&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://folio-org.atlassian.net/browse/UXPROD-2592&lt;/a&gt;&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Af80403de-e149-421e-8750-af45c853402f&quot; class=&quot;user-hover&quot; rel=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; data-account-id=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; accountid=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; rel=&quot;noreferrer&quot;&gt;Charlotte Whitt&lt;/a&gt;, I still think it&apos;s prudent for us to progress on this, as ES will take a while.  Shanghai is starting by just implementing infrastructure in Q3.  It will not be wired into actual FOLIO apps until Q4 at the soonest.&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;we will need stories across most front-end app modules, as well as stripes-components and stripes-smart-components.  There are ~70 occurrences that will need to be investigated in total-core.txt and an additional ~40 in total-complete-only.txt .&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=615afd1cd9820f0070a09ef0&quot; class=&quot;user-hover&quot; rel=&quot;615afd1cd9820f0070a09ef0&quot; data-account-id=&quot;615afd1cd9820f0070a09ef0&quot; accountid=&quot;615afd1cd9820f0070a09ef0&quot; rel=&quot;noreferrer&quot;&gt;Zak Burke&lt;/a&gt;, that&apos;s a lot.  I hope we can take a phased approach to this development, starting with Inventory.  What is the best way to plan this work?  Should we discuss in a Core Functional grooming meeting or schedule a discussion with a smaller group?&lt;/p&gt;</comment>
                                                            <comment id="15036" author="615afd1cd9820f0070a09ef0" created="Mon, 17 Aug 2020 15:54:57 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5ed55244bc90a106063c7&quot; class=&quot;user-hover&quot; rel=&quot;5af5ed55244bc90a106063c7&quot; data-account-id=&quot;5af5ed55244bc90a106063c7&quot; accountid=&quot;5af5ed55244bc90a106063c7&quot; rel=&quot;noreferrer&quot;&gt;Cate Boerema&lt;/a&gt;, I think we could start by grooming stories in &lt;tt&gt;stripes-connect&lt;/tt&gt; and &lt;tt&gt;stripes-smart-components&lt;/tt&gt;. That will address the search-and-sort component family, and thus take care of a big slice of the most important pieces of the UI across many apps. &lt;/p&gt;

&lt;p&gt;Looking at those lists in more detail, there are many &quot;if totalRecords &amp;gt; 0&quot; like statements, which mean there is no work to do there. So, my estimate may have been a vast-over-estimate, which would be nice. In any case, yes, let&apos;s do the remainder one app at a time and start with inventory.&lt;/p&gt;</comment>
                                                            <comment id="15037" author="5f8314dfbdef80006f6f572d" created="Wed, 19 Aug 2020 13:43:28 +0000"  >&lt;p&gt;I know what totalRecordsRounded is supposed to do.. Give some comfort! But really.. This is something the UI should do.. Not to mention that some rounded value gives some false sense of upper and lower bound.. Eg that something is within &amp;lt; 100 of of real hit or &amp;lt; 1000 within some hit count.. Eg if the value returned is 30000 it could be 47000 or if the value is 1700 it could be 17000.&lt;/p&gt;</comment>
                                                            <comment id="15039" author="5ee89462f7aa140abd82d11d" created="Wed, 19 Aug 2020 16:23:34 +0000"  >&lt;p&gt;Note that in the current proposal the back-end passes both the original estimation and the rounded estimation to the clients. The clients can decide whether to show the original estimation or the rounded estimation (they may even do some own rounding based on the original estimation).&lt;/p&gt;

&lt;p&gt;If the exact value is 47000 and the estimated value is 25088 or 34088 then showing the rounded value of 30000 is better then showing 25088 or 34088 because it doesn&apos;t give the false sense of precision.&lt;br/&gt;
Can you explain in more detail why we should not round?&lt;/p&gt;</comment>
                                                            <comment id="15042" author="5f8314dfbdef80006f6f572d" created="Wed, 19 Aug 2020 16:34:40 +0000"  >&lt;p&gt;I don&apos;t it&apos;s backend&apos;s business to return a rounded number when it is not based on lower and upper bound.&lt;/p&gt;

&lt;p&gt;If a UI wants to show &quot;thousands of hits&quot; for an estimated hit count &amp;gt; 1000 or whether to show 34000 is up to the UI team. We will continue to get bug reports about this even with a rounded number because it will give the impression that there&apos;s some reality to the value.. There&apos;s not at the moment.&lt;/p&gt;</comment>
                                                            <comment id="15044" author="5ee89462f7aa140abd82d11d" created="Thu, 20 Aug 2020 08:14:38 +0000"  >&lt;p&gt;Assume these number returned from the back-end:&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
totalRecords: 32351
totalRecordsRounded: 30000
totalRecordsEstimated: &lt;span class=&quot;code-keyword&quot;&gt;true&lt;/span&gt;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;This issue proposes to display it FOLIO as &quot;about 30,000 records found&quot;.&lt;br/&gt;
What is your suggestion?&lt;/p&gt;</comment>
                                                            <comment id="15046" author="5f8314dfbdef80006f6f572d" created="Thu, 20 Aug 2020 09:47:06 +0000"  >&lt;p&gt;I don&apos;t think the backend should return a totalRecordsRounded entity. I think that with the totalRecords and totalRecordsEstimated, the UI can do whatever it pleases.&lt;/p&gt;</comment>
                                                            <comment id="15048" author="5ee89462f7aa140abd82d11d" created="Thu, 20 Aug 2020 09:49:28 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5f8314dfbdef80006f6f572d&quot; class=&quot;user-hover&quot; rel=&quot;5f8314dfbdef80006f6f572d&quot; data-account-id=&quot;5f8314dfbdef80006f6f572d&quot; accountid=&quot;5f8314dfbdef80006f6f572d&quot; rel=&quot;noreferrer&quot;&gt;Adam Dickmeiss&lt;/a&gt; What should the UI display for this value?&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
totalRecords: 32351
totalRecordsEstimated: &lt;span class=&quot;code-keyword&quot;&gt;true&lt;/span&gt;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</comment>
                                                            <comment id="15050" author="5f8314dfbdef80006f6f572d" created="Thu, 20 Aug 2020 14:16:24 +0000"  >&lt;p&gt;The UI could show 30000. Another UI could leave it out.. Clients that are not UIs won&apos;t care. Things like this should not be coupled between modules. I don&apos;t care so much what the UI does. What I think is wrong is to leave it to the backend to do UI work.&lt;/p&gt;</comment>
                                                            <comment id="15052" author="5ee89462f7aa140abd82d11d" created="Thu, 20 Aug 2020 14:22:13 +0000"  >&lt;p&gt;If we change the sample size of a PostgreSQL table the accuracy of the estimation changes. The back-end can then switch to a more appropriate rounding type (A, B or C as presented in this issue&apos;s description, or some other). Do you have proposal how to indicate to the UI that the accuracy has changed?&lt;/p&gt;</comment>
                                                            <comment id="15054" author="5f8314dfbdef80006f6f572d" created="Thu, 20 Aug 2020 14:50:28 +0000"  >&lt;p&gt;What if we see that we can actually have a lower and upper bound later, what then? Bottomline is that at THIS stage the estimated number is the closest to reality that the backed can provide.&lt;/p&gt;</comment>
                                                            <comment id="15055" author="5f8314dfbdef80006f6f572d" created="Thu, 20 Aug 2020 14:56:57 +0000"  >&lt;p&gt;&lt;a href=&quot;https://lucene.apache.org/solr/guide/8_6/common-query-parameters.html&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://lucene.apache.org/solr/guide/8_6/common-query-parameters.html&lt;/a&gt;&lt;br/&gt;
for what some well-known search engine does.&lt;/p&gt;</comment>
                                                            <comment id="15057" author="5ee89462f7aa140abd82d11d" created="Mon, 31 Aug 2020 11:17:11 +0000"  >&lt;p&gt;Thank you for the link.&lt;br/&gt;
Comparing&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;&lt;a href=&quot;https://github.com/folio-org/raml-module-builder#estimated-totalrecords&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/raml-module-builder#estimated-totalrecords&lt;/a&gt;&lt;/li&gt;
	&lt;li&gt;&lt;a href=&quot;https://lucene.apache.org/solr/guide/8_6/common-query-parameters.html#minexactcount-parameter&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://lucene.apache.org/solr/guide/8_6/common-query-parameters.html#minexactcount-parameter&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;shows that our current FOLIO proposal works the same as Solr:&lt;/p&gt;

&lt;div class=&apos;table-wrap&apos;&gt;
&lt;table class=&apos;confluenceTable&apos;&gt;&lt;tbody&gt;
&lt;tr&gt;
&lt;th class=&apos;confluenceTh&apos;&gt; RAML Module Builder &lt;/th&gt;
&lt;th class=&apos;confluenceTh&apos;&gt; Apache Solr &lt;/th&gt;
&lt;th class=&apos;confluenceTh&apos;&gt; content &lt;/th&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td class=&apos;confluenceTd&apos;&gt; totalRecords &lt;/td&gt;
&lt;td class=&apos;confluenceTd&apos;&gt; numFound &lt;/td&gt;
&lt;td class=&apos;confluenceTd&apos;&gt; hit count, exact or estimated &lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td class=&apos;confluenceTd&apos;&gt; totalRecordsEstimated &lt;/td&gt;
&lt;td class=&apos;confluenceTd&apos;&gt; numFoundExact &lt;/td&gt;
&lt;td class=&apos;confluenceTd&apos;&gt; indicates whether the totalRecords/numFound is exact or estimated &lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td class=&apos;confluenceTd&apos;&gt; exactCount &lt;/td&gt;
&lt;td class=&apos;confluenceTd&apos;&gt; minExactCount &lt;/td&gt;
&lt;td class=&apos;confluenceTd&apos;&gt; for hit counts less than this value calculate the exact hit count &lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;&lt;/table&gt;
&lt;/div&gt;
</comment>
                                                            <comment id="15060" author="557058:1f093336-57f7-4359-9b28-6e72640645af" created="Mon, 21 Sep 2020 17:49:49 +0000"  >&lt;p&gt;If elastic search is implemented, this will not be as important. 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;UXPROD-2592&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-2592&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;ElasticSearch - APIs for search and data import&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10322?size=medium&quot; /&gt;
            UXPROD-2592
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
&lt;/p&gt;</comment>
                                                            <comment id="15062" author="5ee89462f7aa140abd82d11d" created="Fri, 2 Oct 2020 08:42:28 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5ed55244bc90a106063c7&quot; class=&quot;user-hover&quot; rel=&quot;5af5ed55244bc90a106063c7&quot; data-account-id=&quot;5af5ed55244bc90a106063c7&quot; accountid=&quot;5af5ed55244bc90a106063c7&quot; rel=&quot;noreferrer&quot;&gt;Cate Boerema&lt;/a&gt; This is the algorithm for the front-end:&lt;/p&gt;

&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
&lt;span class=&quot;code-keyword&quot;&gt;if&lt;/span&gt; totalRecordsEstimated is &lt;span class=&quot;code-keyword&quot;&gt;true&lt;/span&gt;
  print &lt;span class=&quot;code-quote&quot;&gt;&quot;about &quot;&lt;/span&gt; + totalRecordsRounded
&lt;span class=&quot;code-keyword&quot;&gt;else&lt;/span&gt; &lt;span class=&quot;code-keyword&quot;&gt;if&lt;/span&gt; totalRecordsEstimated is &lt;span class=&quot;code-keyword&quot;&gt;false&lt;/span&gt;
  print totalRecords
&lt;span class=&quot;code-comment&quot;&gt;// totalRecordsEstimated is undefined until all back-ends have upgraded RMB,
&lt;/span&gt;&lt;span class=&quot;code-comment&quot;&gt;// handle &lt;span class=&quot;code-keyword&quot;&gt;this&lt;/span&gt; gracefully &lt;span class=&quot;code-keyword&quot;&gt;for&lt;/span&gt; folio-testing:
&lt;/span&gt;&lt;span class=&quot;code-keyword&quot;&gt;else&lt;/span&gt; &lt;span class=&quot;code-keyword&quot;&gt;if&lt;/span&gt; totalRecords &amp;lt; 1000
  print totalRecords
&lt;span class=&quot;code-keyword&quot;&gt;else&lt;/span&gt;
  print &lt;span class=&quot;code-quote&quot;&gt;&quot;about &quot;&lt;/span&gt; + totalRecords + &lt;span class=&quot;code-quote&quot;&gt;&quot; (upgrade back-end &lt;span class=&quot;code-keyword&quot;&gt;for&lt;/span&gt; rounding)&quot;&lt;/span&gt;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Can you update the issue description of 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;UXPROD-2623&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-2623&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Wait for POC of Elastic Search - Round estimated search result hit count (totalRecords)&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10322?size=medium&quot; /&gt;
            UXPROD-2623
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
, 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;UXPROD-2695&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-2695&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Display Rounded Result Counts in Apps Using SearchAndSort (Inventory and Requests)&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10322?size=medium&quot; /&gt;
            UXPROD-2695
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
 and 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;UXPROD-2702&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-2702&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Display Rounded Result Counts in Apps Using SearchAndSortQuery (i.e. Users)&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10322?size=medium&quot; /&gt;
            UXPROD-2702
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
 accordingly?&lt;/p&gt;</comment>
                                                            <comment id="15064" author="5af5ed55244bc90a106063c7" created="Mon, 5 Oct 2020 08:51:42 +0000"  >&lt;p&gt;Yes, I will.  Thanks &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ee89462f7aa140abd82d11d&quot; class=&quot;user-hover&quot; rel=&quot;5ee89462f7aa140abd82d11d&quot; data-account-id=&quot;5ee89462f7aa140abd82d11d&quot; accountid=&quot;5ee89462f7aa140abd82d11d&quot; rel=&quot;noreferrer&quot;&gt;Julian Ladisch&lt;/a&gt;&lt;/p&gt;</comment>
                                                            <comment id="15066" author="5af5ed55244bc90a106063c7" created="Thu, 5 Nov 2020 10:10:51 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ab8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; class=&quot;user-hover&quot; rel=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; data-account-id=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; accountid=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; rel=&quot;noreferrer&quot;&gt;Jakub Skoczen&lt;/a&gt; I removed the R1 2021 fix version from this issue per our discussion in the platform roadmap meetings.  We haven&apos;t made it that far with this and it&apos;s best at this point to hold off and wait for Elastic search.&lt;/p&gt;</comment>
                                                            <comment id="15067" author="557058:f80403de-e149-421e-8750-af45c853402f" created="Fri, 26 Feb 2021 07:46:58 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ab8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; class=&quot;user-hover&quot; rel=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; data-account-id=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; accountid=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; rel=&quot;noreferrer&quot;&gt;Jakub Skoczen&lt;/a&gt;&#160;- The libraries are asked to do another round of feature ranking using 100 points. While this feature is in an undecided state, due to awaiting for the outcome of the POC of using Elastic Search in Inventory.&#160;I have therefore changed this feature to Draft, which I hope is okay by you?&#160;&lt;/p&gt;</comment>
                                                            <comment id="15068" author="557058:f80403de-e149-421e-8750-af45c853402f" created="Wed, 11 Aug 2021 20:11:19 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ab8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; class=&quot;user-hover&quot; rel=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; data-account-id=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; accountid=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; rel=&quot;noreferrer&quot;&gt;Jakub Skoczen&lt;/a&gt; - With the decision to move ahead and implement Elastic search (
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;UXPROD-3046&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-3046&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;NFR: Inventory. Swap from search tool PostgreSQL to Elasticsearch&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10322?size=medium&quot; /&gt;
            UXPROD-3046
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
), then I recommend that we close this feature as will not do. Do you agree?&lt;/p&gt;
</comment>
                                                            <comment id="15070" author="5ee89462f7aa140abd82d11d" created="Wed, 11 Aug 2021 21:06:50 +0000"  >&lt;p&gt;I don&apos;t agree because there are quite a few back-end processes that need &lt;tt&gt;totalRecords&lt;/tt&gt; and cannot use Elastic Search because of the delay changes are propagated from PostgreSQL to Elastic Search.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                            <outwardlinks description="blocks">
                                        <issuelink>
            <issuekey id="11677">UXPROD-2695</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="11653">UXPROD-2702</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="is blocked by">
                                        <issuelink>
            <issuekey id="11588">UXPROD-2806</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10008">
                    <name>Defines</name>
                                                                <inwardlinks description="is defined by ">
                                        <issuelink>
            <issuekey id="57225">RMB-695</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="56784">RMB-578</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="56786">RMB-685</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10002">
                    <name>Duplicate</name>
                                                                <inwardlinks description="is duplicated by">
                                        <issuelink>
            <issuekey id="45551">UIU-1741</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="56060">MODINVSTOR-468</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="11422">UXPROD-2369</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="10844" name="Ska&#776;rmavbild 2020-08-17 kl. 15.55.00.png" size="20936" author="557058:f80403de-e149-421e-8750-af45c853402f" created="Mon, 17 Aug 2020 13:55:29 +0000"/>
                            <attachment id="10845" name="total-complete-only.txt" size="4996" author="615afd1cd9820f0070a09ef0" created="Mon, 17 Aug 2020 12:18:44 +0000"/>
                            <attachment id="10846" name="total-core.txt" size="9868" author="615afd1cd9820f0070a09ef0" created="Mon, 17 Aug 2020 12:18:14 +0000"/>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10000" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummarycf">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10057" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Development Team</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10144"><![CDATA[Core: Platform]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_10064" key="com.atlassian.jira.plugin.system.customfieldtypes:textarea">
                        <customfieldname>PO Ranking Note</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>CW: This feature is in an undecided state, due to awaiting the outcome of the POC of using Elastic Search in Inventory. </customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                <customfield id="customfield_10019" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i01azz:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_10068" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: Chicago (MVP Sum 2020)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10209"><![CDATA[R2]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10069" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: Cornell (Full Sum 2021)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10213"><![CDATA[R1]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10070" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: Duke (Full Sum 2021)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10218"><![CDATA[R1]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10089" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: TAMU (MVP Jan 2021)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10315"><![CDATA[R2]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10020" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10024" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>[CHART] Date of First Response</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Thu, 18 Jun 2020 11:02:28 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10025" key="com.atlassian.jira.ext.charting:timeinstatus">
                        <customfieldname>[CHART] Time in Status</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                    </customfields>
    </item>
</channel>
</rss>