<!-- 
RSS generated by JIRA (1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d) at Thu Feb 08 23:10:03 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>[FOLIO-996] Codex: Use totalRecords from resultInfo</title>
                <link>https://folio-org.atlassian.net/browse/FOLIO-996</link>
                <project id="10290" key="FOLIO">FOLIO</project>
                    <description>&lt;p&gt;At the same time remove totalRecords from instanceCollection.json&lt;/p&gt;

&lt;p&gt;This is a breaking change to the shared raml&lt;/p&gt;</description>
                <environment></environment>
        <key id="80452">FOLIO-996</key>
            <summary>Codex: Use totalRecords from resultInfo</summary>
                <type id="10003" iconUrl="https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium">Task</type>
                                            <priority id="10002" iconUrl="https://dev.folio.org/assets/jira-priority/jira-p3.svg">P3</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="10003">Done</resolution>
                                                        <assignee accountid="557058:4f6bed01-40a6-48d5-8471-7ef21f5ea97c">Hongwei Ji</assignee>
                                                                <reporter accountid="5f8314dfbdef80006f6f572d">Adam Dickmeiss</reporter>
                                    <labels>
                            <label>alpha</label>
                            <label>core</label>
                            <label>sprint29</label>
                    </labels>
                <created>Thu, 21 Dec 2017 14:55:07 +0000</created>
                <updated>Mon, 12 Nov 2018 14:23:54 +0000</updated>
                            <resolved>Fri, 5 Jan 2018 18:04:00 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>8</watches>
                                            <timeestimate seconds="7200">2 hours</timeestimate>
                            <timespent seconds="13500">3 hours, 45 minutes</timespent>
                                <comments>
                                                            <comment id="189230" author="5f8314dfbdef80006f6f572d" created="Thu, 21 Dec 2017 14:57:26 +0000"  >&lt;p&gt;This is depending on 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;MODCXMUX-7&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/MODCXMUX-7&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Return diagnostics in resultInfo&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;
            MODCXMUX-7
        &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;
 which as makes codex includes resultInfo .&lt;/p&gt;</comment>
                                                            <comment id="189232" author="5f8314dfbdef80006f6f572d" created="Thu, 21 Dec 2017 15:01:08 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5bffed52a1b46046f530c8f7&quot; class=&quot;user-hover&quot; rel=&quot;5bffed52a1b46046f530c8f7&quot; data-account-id=&quot;5bffed52a1b46046f530c8f7&quot; accountid=&quot;5bffed52a1b46046f530c8f7&quot; rel=&quot;noreferrer&quot;&gt;Mike Taylor&lt;/a&gt; .. would it be a big deal to change ui-search to use totalRecords from resultInfo/totalRecords rather than totalRecords (top-level). The latter which would be removed by this change.&lt;/p&gt;</comment>
                                                            <comment id="189235" author="5bffed52a1b46046f530c8f7" created="Thu, 21 Dec 2017 17:09:12 +0000"  >&lt;p&gt;We can do it; but do we want to? There is a standard that all our searchable backend modules adhere to. Making the mod-codex-mux diverge from this standard seems like something we should do only if absolutely necessary.&lt;/p&gt;</comment>
                                                            <comment id="189236" author="557058:4f6bed01-40a6-48d5-8471-7ef21f5ea97c" created="Thu, 21 Dec 2017 17:23:06 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5bffed52a1b46046f530c8f7&quot; class=&quot;user-hover&quot; rel=&quot;5bffed52a1b46046f530c8f7&quot; data-account-id=&quot;5bffed52a1b46046f530c8f7&quot; accountid=&quot;5bffed52a1b46046f530c8f7&quot; rel=&quot;noreferrer&quot;&gt;Mike Taylor&lt;/a&gt; and &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; Below messages are from Codex slack discussion. Can we confirm which one (totalRecords or resultInfo.totalRecords) is the long term goal? &lt;/p&gt;

&lt;p&gt;From Marc Johnson&lt;br/&gt;
@dickmeiss I believe the intention was that the `totalRecords` properties in each collection schema would eventually be replaced by an object property that used resultInfo&lt;br/&gt;
Posted in #codexToday at 9:22 AM&lt;/p&gt;

&lt;p&gt;From Adam Dickmeiss&lt;br/&gt;
ok.. If that is the intention the &quot;move&quot; is a breaking change (ie remove a required totalRecords field from top-level).&lt;br/&gt;
Posted in #codexToday at 9:25 AM&lt;/p&gt;

&lt;p&gt;From Marc Johnson&lt;br/&gt;
I believe so, it might be worth checking with @jakub that is still the plan for interfaces going forward&lt;br/&gt;
Posted in #codexToday at 9:26 AM&lt;/p&gt;</comment>
                                                            <comment id="189238" author="5f8314dfbdef80006f6f572d" created="Thu, 21 Dec 2017 18:17:25 +0000"  >&lt;p&gt;Can we at least agree that having two places for totalRecords is misleading?&lt;/p&gt;

&lt;p&gt;I don&apos;t care where we put it.&lt;/p&gt;</comment>
                                                            <comment id="189240" author="712020:32bb56ac-50e7-4787-b4af-ed3089d9401c" created="Thu, 21 Dec 2017 20:54:40 +0000"  >&lt;p&gt;what marc stated is correct, the only reason the original totalRecords has remained is because module developers were given time to introduce this breaking change at an appropriate time - however, it seems like no one has made this change - the intention is to remove this, and this code will be depreciated in rmb at one point at right now there is support for both and this will not be maintained forever&lt;/p&gt;</comment>
                                                            <comment id="189242" author="5bffed52a1b46046f530c8f7" created="Fri, 22 Dec 2017 00:58:02 +0000"  >&lt;p&gt;OK, I misunderstood what&apos;s going on here. You&apos;re not wanting to change mod-codex-mux to behave different from other RMB modules; you&apos;re &lt;em&gt;using&lt;/em&gt; the RMB support to do the standard thing, which at present is to put the count in both places. Somehow I missed this change when it was made.&lt;/p&gt;

&lt;p&gt;I guess we should file issues to update ui-inventory, ui-items, ui-requests and &lt;tt&gt;&amp;lt;SearchAndSort&amp;gt;&lt;/tt&gt; to get the count from the new location; then, after they&apos;re fixed, we can go ahead and remove it from the old location.&lt;/p&gt;

&lt;p&gt;This feels like an annoying waste of time, especially as the name of the field has already changed once (from &lt;tt&gt;total_records&lt;/tt&gt;), with attendant dancing around keeping the UI modules compatible.&lt;/p&gt;</comment>
                                                            <comment id="189244" author="557058:4f6bed01-40a6-48d5-8471-7ef21f5ea97c" created="Wed, 3 Jan 2018 20:20:11 +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; I updated your branch &lt;a href=&quot;https://github.com/folio-org/raml/tree/modcxmux-7&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/raml/tree/modcxmux-7&lt;/a&gt; to remove totalRecords and only use resultInfo.totalRecords. I also have codex-ekb ready locally for this breaking change. Let me know when do you want to merge to RAML master.&lt;/p&gt;</comment>
                                                            <comment id="189246" author="712020:38d1a08f-86a8-4df2-9191-239b16b0a81a" created="Fri, 5 Jan 2018 12:45:33 +0000"  >&lt;p&gt;I think removing totalRecords at this point is risky, it is a breaking change that affects many modules. I think we should just deprecate it for a few versions, and remove it completely when alpha is out.&lt;/p&gt;</comment>
                                                            <comment id="189248" author="5bffed52a1b46046f530c8f7" created="Fri, 5 Jan 2018 12:50:05 +0000"  >&lt;p&gt;And predictably enough, it &lt;em&gt;has&lt;/em&gt; broken the UI module. &lt;b&gt;sigh&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;Not to worry. I&apos;ll fix the UI Codex Search module to work around the breakage.&lt;/p&gt;</comment>
                                                            <comment id="189249" author="5f8314dfbdef80006f6f572d" created="Fri, 5 Jan 2018 13:14:35 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5bffed52a1b46046f530c8f7&quot; class=&quot;user-hover&quot; rel=&quot;5bffed52a1b46046f530c8f7&quot; data-account-id=&quot;5bffed52a1b46046f530c8f7&quot; accountid=&quot;5bffed52a1b46046f530c8f7&quot; rel=&quot;noreferrer&quot;&gt;Mike Taylor&lt;/a&gt; ?? How is that possible? Neither mod-codex-mux nor mod-codex-inventory is using that new raml-utils .&lt;/p&gt;</comment>
                                                            <comment id="189251" author="5bffed52a1b46046f530c8f7" created="Fri, 5 Jan 2018 13:17:41 +0000"  >&lt;p&gt;I don&apos;t know &amp;#8211; Just know that ui-search is failing with &quot;Cannot read property &apos;totalRecords&apos; of undefined&quot;&lt;/p&gt;

&lt;p&gt;Will investigate more after lunch.&lt;/p&gt;</comment>
                                                            <comment id="189253" author="557058:4f6bed01-40a6-48d5-8471-7ef21f5ea97c" created="Fri, 5 Jan 2018 13:52:32 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=712020%3A38d1a08f-86a8-4df2-9191-239b16b0a81a&quot; class=&quot;user-hover&quot; rel=&quot;712020:38d1a08f-86a8-4df2-9191-239b16b0a81a&quot; data-account-id=&quot;712020:38d1a08f-86a8-4df2-9191-239b16b0a81a&quot; accountid=&quot;712020:38d1a08f-86a8-4df2-9191-239b16b0a81a&quot; rel=&quot;noreferrer&quot;&gt;Heikki Levanto&lt;/a&gt; I believe we only focus the change within Codex modules (codex-mux, codex-mock, codex-ekb, codex-inventory, and of course ui-search), so the risk is relatively low and contained.&lt;/p&gt;</comment>
                                                            <comment id="189254" author="5bffed52a1b46046f530c8f7" created="Fri, 5 Jan 2018 14:48:35 +0000"  >&lt;p&gt;OK, my problem seems to be caused by something even weirder:&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;
GET http:&lt;span class=&quot;code-comment&quot;&gt;//localhost:9130/codex-instances?limit=30&amp;amp;query=cql.allRecords%3D1%20sortby%20title
&lt;/span&gt;
500 Internal Server Error
Module mod-codex-inventory-0.0.4-SNAPSHOT.17 500
Unknown index: cql.allRecords
Module mod-codex-mock-1.0.4-SNAPSHOT.24 200
{
  &lt;span class=&quot;code-quote&quot;&gt;&quot;instances&quot;&lt;/span&gt; : [ {
    &lt;span class=&quot;code-quote&quot;&gt;&quot;id&quot;&lt;/span&gt; : &lt;span class=&quot;code-quote&quot;&gt;&quot;77777777-7777-7777-7777-000000002016&quot;&lt;/span&gt;,
    &lt;span class=&quot;code-quote&quot;&gt;&quot;title&quot;&lt;/span&gt; : &lt;span class=&quot;code-quote&quot;&gt;&quot;1, 2, 3&quot;&lt;/span&gt;,
    &lt;span class=&quot;code-quote&quot;&gt;&quot;contributor&quot;&lt;/span&gt; : [ ],
    &lt;span class=&quot;code-quote&quot;&gt;&quot;publisher&quot;&lt;/span&gt; : &lt;span class=&quot;code-quote&quot;&gt;&quot;Dorling Kindersley, 2000&quot;&lt;/span&gt;,
    &lt;span class=&quot;code-quote&quot;&gt;&quot;type&quot;&lt;/span&gt; : &lt;span class=&quot;code-quote&quot;&gt;&quot;books&quot;&lt;/span&gt;,
    &lt;span class=&quot;code-quote&quot;&gt;&quot;identifier&quot;&lt;/span&gt; : [ {
      &lt;span class=&quot;code-quote&quot;&gt;&quot;value&quot;&lt;/span&gt; : &lt;span class=&quot;code-quote&quot;&gt;&quot;0751362484&quot;&lt;/span&gt;,
      &lt;span class=&quot;code-quote&quot;&gt;&quot;type&quot;&lt;/span&gt; : &lt;span class=&quot;code-quote&quot;&gt;&quot;isbn&quot;&lt;/span&gt;
    } ],
    &lt;span class=&quot;code-quote&quot;&gt;&quot;source&quot;&lt;/span&gt; : &lt;span class=&quot;code-quote&quot;&gt;&quot;kb&quot;&lt;/span&gt;,
    &lt;span class=&quot;code-quote&quot;&gt;&quot;language&quot;&lt;/span&gt; : [ ]
  }, 
  ...
  ],
  &lt;span class=&quot;code-quote&quot;&gt;&quot;totalRecords&quot;&lt;/span&gt; : 204
}
Module mod-codex-ekb-0.0.2-SNAPSHOT.52 500
Configuration data is invalid
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;So it seems that a bunch of instances are being correctly returned, &lt;em&gt;but&lt;/em&gt; I am also getting a bunch of error messages preceding and following the data. Surely that can&apos;t be right.&lt;/p&gt;

&lt;p&gt;Also: the specific error reported here (&quot;Unknown index: cql.allRecords&quot;) makes no sense, as the query &lt;tt&gt;cql.allRecords=1 sortby title&lt;/tt&gt; does not use that index.&lt;/p&gt;

&lt;p&gt;Please advise.&lt;/p&gt;</comment>
                                                            <comment id="189256" author="5bffed52a1b46046f530c8f7" created="Fri, 5 Jan 2018 16:29:16 +0000"  >&lt;p&gt;When I change the parameters to do a title search (&lt;tt&gt;title=&quot;a*&quot; sortby title&lt;/tt&gt;), I get something similar:&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;
GET /codex-instances?limit=30&amp;amp;query=title%3D%22a%2A%22%20sortby%20title

500 Internal Server Error
Module mod-codex-mock-1.0.4-SNAPSHOT.24 200
{ &lt;span class=&quot;code-comment&quot;&gt;/* list of records from mock */&lt;/span&gt; }
Module mod-codex-ekb-0.0.2-SNAPSHOT.52 500
Configuration data is invalid
Module mod-codex-inventory-0.0.4-SNAPSHOT.17 200
{ &lt;span class=&quot;code-comment&quot;&gt;/* list of records from inventory */&lt;/span&gt; }
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;My interpretation: when an error occurs in any back-end, mux generates a response that includes, for each provider:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;the name of the provider module&lt;/li&gt;
	&lt;li&gt;&lt;em&gt;either&lt;/em&gt; the data it returned &lt;em&gt;or&lt;/em&gt; the errors it reported&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;(And if any of the back-end modules yielded an error, it yields an error status: not sure if it&apos;s always 500, or if it uses the error status from the back-end module.)&lt;/p&gt;

&lt;p&gt;If I am right, then the good news is that we are successfully multiplexing the mock and inventory codex modules; the bad news is that an error in mod-codex-ekb is making it impossible to get a good response.&lt;/p&gt;

&lt;p&gt;Are there any queries that we know &lt;em&gt;do&lt;/em&gt; work in mod-codex-ekb?&lt;/p&gt;</comment>
                                                            <comment id="189258" author="557058:4f6bed01-40a6-48d5-8471-7ef21f5ea97c" created="Fri, 5 Jan 2018 16:37:25 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5bffed52a1b46046f530c8f7&quot; class=&quot;user-hover&quot; rel=&quot;5bffed52a1b46046f530c8f7&quot; data-account-id=&quot;5bffed52a1b46046f530c8f7&quot; accountid=&quot;5bffed52a1b46046f530c8f7&quot; rel=&quot;noreferrer&quot;&gt;Mike Taylor&lt;/a&gt; the ekb error says &quot;Configuration data is invalid&quot;, so probably not a query issue.&lt;/p&gt;</comment>
                                                            <comment id="189260" author="5bffed52a1b46046f530c8f7" created="Fri, 5 Jan 2018 16:39:11 +0000"  >&lt;p&gt;Thanks, &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A4f6bed01-40a6-48d5-8471-7ef21f5ea97c&quot; class=&quot;user-hover&quot; rel=&quot;557058:4f6bed01-40a6-48d5-8471-7ef21f5ea97c&quot; data-account-id=&quot;557058:4f6bed01-40a6-48d5-8471-7ef21f5ea97c&quot; accountid=&quot;557058:4f6bed01-40a6-48d5-8471-7ef21f5ea97c&quot; rel=&quot;noreferrer&quot;&gt;Hongwei Ji&lt;/a&gt;. I&apos;ll meet you on Slack to discuss.&lt;/p&gt;</comment>
                                                            <comment id="189261" author="5bffed52a1b46046f530c8f7" created="Fri, 5 Jan 2018 16:48:18 +0000"  >&lt;p&gt;Clarification on what&apos;s going on, then. Two separate back-end probems.&lt;br/&gt;
1. &quot;Configuration data is invalid&quot; in mod-codex-ekb, which I am discussing on Slack with &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A4f6bed01-40a6-48d5-8471-7ef21f5ea97c&quot; class=&quot;user-hover&quot; rel=&quot;557058:4f6bed01-40a6-48d5-8471-7ef21f5ea97c&quot; data-account-id=&quot;557058:4f6bed01-40a6-48d5-8471-7ef21f5ea97c&quot; accountid=&quot;557058:4f6bed01-40a6-48d5-8471-7ef21f5ea97c&quot; rel=&quot;noreferrer&quot;&gt;Hongwei Ji&lt;/a&gt;&lt;br/&gt;
2. &lt;tt&gt;cql.allRecords=1&lt;/tt&gt; not supported in mod-codex-inventory. I added it to the Codex CQL schema in &lt;a href=&quot;https://github.com/folio-org/raml/pull/61&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/raml/pull/61&lt;/a&gt; and Adam is planning to implement it.&lt;/p&gt;</comment>
                                                            <comment id="189262" author="5bffed52a1b46046f530c8f7" created="Fri, 5 Jan 2018 16:55:43 +0000"  >&lt;p&gt;Based on discussion on the FOLIO Slack&apos;s #codex channel, we are &lt;em&gt;not&lt;/em&gt; making the change in #2 after all &amp;#8211; it would be difficult for the EBSCO KB. Instead, I will file a new issue on myself to have the Codex not include a query at all, initially.&lt;/p&gt;</comment>
                                                            <comment id="189264" author="5bffed52a1b46046f530c8f7" created="Fri, 5 Jan 2018 17:00:50 +0000"  >&lt;p&gt;And #1 is probably due to the module not having been given credentials for accessing the EBSCO KB. So I will file a new issue to get that working, and I &lt;em&gt;think&lt;/em&gt; that means all the problems I reported have &quot;resolutions&quot; now ... by which I mean I will fix them in the two new issues &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;

&lt;p&gt;BTW., none of this was really much to do with the ostensible purpose of 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-996&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-996&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Codex: Use totalRecords from resultInfo&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            FOLIO-996
        &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;
, so sorry for hijacking the thread. I&apos;ll leave now &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="189266" author="557058:4f6bed01-40a6-48d5-8471-7ef21f5ea97c" created="Fri, 5 Jan 2018 17:41:21 +0000"  >&lt;p&gt;That&apos;s great. &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5bffed52a1b46046f530c8f7&quot; class=&quot;user-hover&quot; rel=&quot;5bffed52a1b46046f530c8f7&quot; data-account-id=&quot;5bffed52a1b46046f530c8f7&quot; accountid=&quot;5bffed52a1b46046f530c8f7&quot; rel=&quot;noreferrer&quot;&gt;Mike Taylor&lt;/a&gt; I will mark this ticket as closed now.&lt;/p&gt;</comment>
                                                            <comment id="189268" author="557058:4f6bed01-40a6-48d5-8471-7ef21f5ea97c" created="Fri, 5 Jan 2018 18:04:00 +0000"  >&lt;p&gt;&lt;a href=&quot;https://github.com/folio-org/raml/pull/60&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/raml/pull/60&lt;/a&gt;&lt;/p&gt;</comment>
                                                            <comment id="189270" author="5bffed52a1b46046f530c8f7" created="Mon, 8 Jan 2018 16:34:40 +0000"  >&lt;p&gt;So aside from my digression (for which, my apologies) was the outcome of this issue that we now have two redundant copies of the &lt;tt&gt;totalRecords&lt;/tt&gt; count in search responses?&lt;/p&gt;</comment>
                                                            <comment id="189271" author="557058:4f6bed01-40a6-48d5-8471-7ef21f5ea97c" created="Mon, 8 Jan 2018 16:40:01 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5bffed52a1b46046f530c8f7&quot; class=&quot;user-hover&quot; rel=&quot;5bffed52a1b46046f530c8f7&quot; data-account-id=&quot;5bffed52a1b46046f530c8f7&quot; accountid=&quot;5bffed52a1b46046f530c8f7&quot; rel=&quot;noreferrer&quot;&gt;Mike Taylor&lt;/a&gt; Just one and it is resultInfo.totalRecords. &lt;/p&gt;</comment>
                                                            <comment id="189272" author="5bffed52a1b46046f530c8f7" created="Mon, 8 Jan 2018 16:58:54 +0000"  >&lt;p&gt;Hmm. Then I am surprised my UI code is still working. Maybe someone fixed stripes-connect to deal with this while I wasn&apos;t looking.&lt;/p&gt;</comment>
                                                            <comment id="189274" author="5bffed52a1b46046f530c8f7" created="Mon, 8 Jan 2018 17:03:20 +0000"  >&lt;p&gt;Nope ... the code is the same as it always was:&lt;br/&gt;
&lt;a href=&quot;https://github.com/folio-org/stripes-connect/blob/master/RESTResource/RESTResource.js#L499-L500&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/stripes-connect/blob/master/RESTResource/RESTResource.js#L499-L500&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Oh, and I see now that my UI is saying &quot;NaN Records found&quot; &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="189276" author="5bffed52a1b46046f530c8f7" created="Mon, 8 Jan 2018 17:08:14 +0000"  >&lt;p&gt;I&apos;ll fix this in 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;STCON-55&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/STCON-55&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Enable RESTResource to get totalRecords from alternative location&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;
            STCON-55
        &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>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                            <outwardlinks description="blocks">
                                        <issuelink>
            <issuekey id="74503">STCON-55</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="75411">MODCXEKB-54</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="79086">MODCXMOCK-14</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                    </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_10019" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|hzy5pz:</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, 21 Dec 2017 17:09:12 +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>