<!-- 
RSS generated by JIRA (1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d) at Fri Feb 09 00:17:22 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-1655] Inventory. Search call number (Core functional) - thin thread</title>
                <link>https://folio-org.atlassian.net/browse/UXPROD-1655</link>
                <project id="10000" key="UXPROD">UX Product</project>
                    <description>&lt;p&gt;&lt;font color=&quot;orange&quot;&gt;&lt;b&gt;This feature capture the work planned for the Core functional team&lt;/b&gt;&lt;/font&gt;&lt;/p&gt;

&lt;p&gt;The elements Call number, and Call number type are implemented in the Holdings and Item records as of Q4 2018. &lt;/p&gt;

&lt;p&gt;Use cases: &lt;br/&gt;
Multiple times daily catalogers and other library staff need to search by call number; system needs to search normalized version, not exact text string.&lt;/p&gt;

&lt;p&gt;Several libraries have expressed a requirement on being able to search by normalized call number - besides search on call number as an exact string, we&apos;d also need search where we handle removing of misc. qualifiers, and more. &lt;/p&gt;

&lt;p&gt;&lt;b&gt;Summary of requirements discussed with SMEs:&lt;/b&gt;&lt;br/&gt;
So this would be the best solution for the searching of call numbers:&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;String/phrase index for prefix and call number (no keyword index)&lt;/li&gt;
	&lt;li&gt;Searching must be possible without spaces and/or special characters&lt;/li&gt;
	&lt;li&gt;Additionally: exact search (with spaces and special characters)
	&lt;ul&gt;
		&lt;li&gt;could be customized (per tenant) with a selection list of special characters to be taken into account in a search.&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
	&lt;li&gt;No automatically truncation
	&lt;ul&gt;
		&lt;li&gt;Wildcards&lt;/li&gt;
		&lt;li&gt;Wildcard for explicitely right truncation, e.g. &#8220;*&#8221;&lt;/li&gt;
		&lt;li&gt;Wildcard for exact one character, e.g. &#8220;!&#8221;&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
	&lt;li&gt;Call numbers
	&lt;ul&gt;
		&lt;li&gt;geo 11&lt;/li&gt;
		&lt;li&gt;geo 12&lt;/li&gt;
		&lt;li&gt;geo 100&lt;/li&gt;
		&lt;li&gt;geo 123&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
	&lt;li&gt;Search variants
	&lt;ul&gt;
		&lt;li&gt;geo 1!  &#8594;  geo 11 and geo 12&lt;/li&gt;
		&lt;li&gt;geo 1!! &#8594;  geo 100 and geo 123&lt;/li&gt;
		&lt;li&gt;geo 1* &#8594;  geo 11 and geo 12 and geo 100 and geo 123&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
	&lt;li&gt;Wildcard for 0-n characters, e.g. &#8220;#&#8221;&lt;/li&gt;
	&lt;li&gt;Character classes
	&lt;ul&gt;
		&lt;li&gt;germ 3&lt;span class=&quot;error&quot;&gt;&amp;#91;567&amp;#93;&lt;/span&gt;0* = germ 350* | germ 360* | germ 370*&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
	&lt;li&gt;Boolean operators, also to combine different search criteria
	&lt;ul&gt;
		&lt;li&gt;AND&lt;/li&gt;
		&lt;li&gt;OR&lt;/li&gt;
		&lt;li&gt;NOT&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;&lt;b&gt;Documentation:&lt;/b&gt;&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Notes on call number search (p.13-17) in &lt;a href=&quot;https://docs.google.com/document/d/1FMl-_oNR6k-wVDQrZeMT_V9-ZDDaZBzdiipx0OQii9E/edit#&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://docs.google.com/document/d/1FMl-_oNR6k-wVDQrZeMT_V9-ZDDaZBzdiipx0OQii9E/edit#&lt;/a&gt;&lt;/li&gt;
	&lt;li&gt;Discuss post: &lt;a href=&quot;https://discuss.folio.org/t/call-number-normalization-sort/2570&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://discuss.folio.org/t/call-number-normalization-sort/2570&lt;/a&gt;&lt;/li&gt;
	&lt;li&gt;uChicago&#8217;s OLE solution - &lt;a href=&quot;https://catalog.lib.uchicago.edu/vufind/Alphabrowse/Home?from=A&amp;amp;source=lcc&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://catalog.lib.uchicago.edu/vufind/Alphabrowse/Home?from=A&amp;amp;source=lcc&lt;/a&gt;
	&lt;ul&gt;
		&lt;li&gt;the solution differentiates between several common schemes, defines the ordering behavior for each, and defaults to alpha-numeric for anything else. It is extensible&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
	&lt;li&gt;uChicago&apos;s code (developed by Tod Olson): &lt;a href=&quot;https://github.com/solrmarc&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/solrmarc&lt;/a&gt;&lt;/li&gt;
&lt;/ul&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;Examples:&lt;/b&gt;&lt;br/&gt;
tit=letters per=goethe,*       	&lt;br/&gt;
(Title must contain &#8220;letters&#8221;, author is Goethe,* &#8209; standard operator is AND)&lt;br/&gt;
per=bach,j* NOT sgn=mus*       	&lt;br/&gt;
(Author is bach,j*, call number does not start with &#8220;mus&#8221;)&lt;br/&gt;
tit cookbook AND (sgn=math* OR sgn=comp*)        	&lt;br/&gt;
(the cookbook series from O&#8217;Reilly)&lt;/p&gt;

&lt;p&gt;Some more complex examples from GBV libraries *before *normalization (added by &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;
&lt;ul&gt;
	&lt;li&gt;8 G.B.439 :6&lt;/li&gt;
	&lt;li&gt;JUR:R III:54:(1):Schm:1850&lt;/li&gt;
	&lt;li&gt;94 NF 14/1:3792-3835&lt;/li&gt;
	&lt;li&gt;1990/146 4&#176;&lt;/li&gt;
	&lt;li&gt;426/083 4&#176; SH 34&lt;/li&gt;
	&lt;li&gt;Z 557: 54.1961/62,7-12&lt;/li&gt;
	&lt;li&gt;Y 43839 (2017/18)&lt;/li&gt;
&lt;/ul&gt;


</description>
                <environment></environment>
        <key id="11005">UXPROD-1655</key>
            <summary>Inventory. Search call number (Core functional) - thin thread</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>
                            <parent id="13656">UXPROD-785</parent>
                                    <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:f80403de-e149-421e-8750-af45c853402f">Charlotte Whitt</assignee>
                                                                <reporter accountid="557058:f80403de-e149-421e-8750-af45c853402f">Charlotte Whitt</reporter>
                                    <labels>
                            <label>call_number</label>
                            <label>cap-mvp</label>
                            <label>inventory</label>
                            <label>metadatamanagement</label>
                            <label>po-mvp</label>
                            <label>q1-2020-at-risk</label>
                            <label>q4-2019-at-risk</label>
                            <label>split</label>
                    </labels>
                <created>Wed, 17 Apr 2019 08:41:20 +0000</created>
                <updated>Wed, 16 Sep 2020 21:13:12 +0000</updated>
                            <resolved>Mon, 16 Mar 2020 10:07:00 +0000</resolved>
                                                    <fixVersion>Q1 2020</fixVersion>
                                        <due></due>
                            <votes>0</votes>
                                    <watches>13</watches>
                                                                <comments>
                                                            <comment id="11741" author="5c48911b54e1e6466b11f38c" created="Mon, 22 Apr 2019 16:34:04 +0000"  >&lt;p&gt;Yes, this is a requirement for Duke (go-live). We&apos;d also want the call number to display on the search results screen (which we assume is the inventory pane sorted down.)&lt;/p&gt;

&lt;p&gt;We also want to be clear about the specific issue of searching by &lt;b&gt;normalized&lt;/b&gt; call number - staff need to be able to search by the call number that they see on the book, or on the web catalog entry, or from a bib record. In other words, if normalization is changing the call number formatting, staff can still search by the call number &lt;b&gt;before it is normalized&lt;/b&gt; to have it return the result as expected.&lt;/p&gt;

&lt;p&gt;We would be glad to discuss this need further. &lt;/p&gt;</comment>
                                                            <comment id="11745" author="712020:363234f4-7171-418a-92d6-83fbb9f543fc" created="Mon, 13 May 2019 08:25:41 +0000"  >&lt;p&gt;Some more complex examples from GBV libraries &lt;b&gt;before&lt;/b&gt; normalization:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;8 G.B.439 :6&lt;/li&gt;
	&lt;li&gt;JUR:R III:54:(1):Schm:1850&lt;/li&gt;
	&lt;li&gt;94 NF 14/1:3792-3835&lt;/li&gt;
	&lt;li&gt;1990/146 4&#176;&lt;/li&gt;
	&lt;li&gt;426/083 4&#176; SH 34&lt;/li&gt;
	&lt;li&gt;Z 557: 54.1961/62,7-12&lt;/li&gt;
	&lt;li&gt;Y 43839 (2017/18)&lt;/li&gt;
&lt;/ul&gt;
</comment>
                                                            <comment id="11751" author="712020:363234f4-7171-418a-92d6-83fbb9f543fc" created="Tue, 14 May 2019 07:41:10 +0000"  >&lt;p&gt;Outcome of a conversation with &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5e8c99cbf135980b7bd6d120&quot; class=&quot;user-hover&quot; rel=&quot;5e8c99cbf135980b7bd6d120&quot; data-account-id=&quot;5e8c99cbf135980b7bd6d120&quot; accountid=&quot;5e8c99cbf135980b7bd6d120&quot; rel=&quot;noreferrer&quot;&gt;Uschi Klute&lt;/a&gt;:&lt;br/&gt;
It will be necessary to remove one or the other character for creating an index entry. Therefore, only one search option will probably not accommodate all FOLIO libraries. It would be optimal to be able to define at least per tenant the characters themselves which are ignored during the search. For some the slash is elementary, for others the plus sign. And for others, both should be ignored. This is an example for multiple indices for the call no &quot;Z 557: 54.1961/62,7-12&quot; from our current ILS:&lt;br/&gt;
Call number with blanks, dot, comma, dash: z 557: 54.1961/62,7-12 &lt;b&gt;OR&lt;/b&gt; z 557 54.1961 62,7-12&lt;br/&gt;
Call number without blanks and special characters: z55754196162712&lt;/p&gt;</comment>
                                                            <comment id="11757" author="70121:be36acda-040d-4925-b3df-ebd7e16d4b5b" created="Thu, 6 Jun 2019 15:19:14 +0000"  >&lt;p&gt;There is a need for normalized call numbers for reporting as well. &lt;br/&gt;
&lt;a href=&quot;https://folio-org.atlassian.net/wiki/display/RPT/Shelf+List+Location+Report+Prototype&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://folio-org.atlassian.net/wiki/display/RPT/Shelf+List+Location+Report+Prototype&lt;/a&gt;&lt;/p&gt;</comment>
                                                            <comment id="11761" author="557058:f80403de-e149-421e-8750-af45c853402f" created="Thu, 6 Jun 2019 15:22:29 +0000"  >&lt;p&gt;Yes &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;, that&apos;s correct. I can add &apos;Reporting&apos; in the description.&lt;/p&gt;</comment>
                                                            <comment id="11766" author="5af5ed55244bc90a106063c7" created="Thu, 8 Aug 2019 07:34:20 +0000"  >&lt;p&gt;Marking this Open, as Draft suggests that stories are actively being written.  &lt;/p&gt;</comment>
                                                            <comment id="11770" author="5af5ed55244bc90a106063c7" created="Mon, 23 Sep 2019 09:29:41 +0000"  >&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;, &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; et al.  Do we have a decision on whether call number searching should happen on the &quot;normalized&quot; version as stated in the story description or on the human-readable version as suggested in the comments here from &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5c48911b54e1e6466b11f38c&quot; class=&quot;user-hover&quot; rel=&quot;5c48911b54e1e6466b11f38c&quot; data-account-id=&quot;5c48911b54e1e6466b11f38c&quot; accountid=&quot;5c48911b54e1e6466b11f38c&quot; rel=&quot;noreferrer&quot;&gt;Erin Nettifee&lt;/a&gt; and, if I&apos;m understanding correctly, &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;?  Or maybe we should have a combined search index which allows searching both at once?&lt;/p&gt;
</comment>
                                                            <comment id="11776" author="70121:be36acda-040d-4925-b3df-ebd7e16d4b5b" created="Mon, 23 Sep 2019 15:22:05 +0000"  >&lt;p&gt;Based on our discussion in the call number notes document about the definition of normalized, I think we want the search to be on the human readable call number. But we do need to be able, as Felix notes above, to define search behavior around spaces and punctuation. If we need to search the normalized call number in order to accomplish this, then I think we would need both at once. &lt;/p&gt;</comment>
                                                            <comment id="11780" author="63e2a2771b13d42998e4e706" created="Tue, 22 Oct 2019 14:47:07 +0000"  >&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; &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 the intention that in this feature it will be possible to sort the instance search results by the sortable normalised call number (of items)?&lt;/p&gt;</comment>
                                                            <comment id="11785" author="5af5ed55244bc90a106063c7" created="Tue, 22 Oct 2019 16:03:43 +0000"  >&lt;blockquote&gt;&lt;p&gt;Based on our discussion in the call number notes document about the definition of normalized, I think we want the search to be on the human readable call number. &lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Thanks &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;, what elements of the human readable call number?  Options: &amp;lt;EffectiveCallNumberPrefix&amp;gt; &amp;lt;EffectiveCallNumber&amp;gt; &amp;lt;EffectiveCallNumberSuffix&amp;gt; &amp;lt;Volume&amp;gt; &amp;lt;Enumeration&amp;gt; &amp;lt;Chronology&amp;gt; &amp;lt;EffectiveCopy&amp;gt;&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;But we do need to be able, as Felix notes above, to define search behavior around spaces and punctuation. If we need to search the normalized call number in order to accomplish this, then I think we would need both at once.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;It&apos;s a bit confusing because the term &quot;normalized call number&quot; seems to be used to refer to two different things: (1) the sortable call number (which will be developed using Tod&apos;s code) and (2) the searchable call number (which, as I understand it, is the human-readable call number and can be searched in ways that, for example, ignore punctuation).  I would be surprised if #1 is equal to #2.  I think we should assume for now that they are not.&lt;/p&gt;</comment>
                                                            <comment id="11792" author="5af5ed55244bc90a106063c7" created="Tue, 22 Oct 2019 16:32:42 +0000"  >&lt;p&gt;I just reviewed the discussion on Slack &lt;a href=&quot;https://folio-project.slack.com/archives/GMAPRTZ6V/p1569232347019600&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://folio-project.slack.com/archives/GMAPRTZ6V/p1569232347019600&lt;/a&gt; and I am still not sure where we landed on this &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;  Tod had the last comment and he suggested we search on &amp;lt;EffectiveCallNumber&amp;gt;.&lt;/p&gt;

&lt;p&gt;I think we might want to call a meeting to discuss call number searching with the sub-group and include &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; and maybe a frontend developer, as well.  I see there is tons of good info in the Notes document (this section: &lt;a href=&quot;https://docs.google.com/document/d/1FMl-_oNR6k-wVDQrZeMT_V9-ZDDaZBzdiipx0OQii9E/edit#heading=h.6cxl044jh93x&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://docs.google.com/document/d/1FMl-_oNR6k-wVDQrZeMT_V9-ZDDaZBzdiipx0OQii9E/edit#heading=h.6cxl044jh93x&lt;/a&gt;).  &lt;/p&gt;</comment>
                                                            <comment id="11798" author="5af5ed55244bc90a106063c7" created="Fri, 25 Oct 2019 11:51:12 +0000"  >&lt;p&gt;Given we only have 2.5 sprints left and this isn&apos;t started (or dev-ready) I think we should label it as at-risk&lt;/p&gt;</comment>
                                                            <comment id="11801" author="557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d" created="Mon, 2 Dec 2019 13:49:18 +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;&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 discussed this ticket and concluded that while this is similar to 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;UIIN-647&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UIIN-647&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Normalize ISBNs for ISBN searching in Instance, holdings, item segments. New search option: ISBN, normalized&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10309?size=medium&quot; /&gt;
            UIIN-647
        &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;
 there doesn&apos;t seem to be a simple. backend-only solution here.&lt;/p&gt;

&lt;p&gt;The reason is that a search for a call number like &quot;a bc&quot; may mean &quot;a callnumber bc with a prefix a&quot; or &quot;a call number &apos;a bc&apos;&quot;. This ambiguity requires more advanced normalization in the backend OR a combination of a front-end and backend solution. &lt;/p&gt;</comment>
                                                            <comment id="11807" author="557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d" created="Mon, 2 Dec 2019 14:00:26 +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; &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=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;&lt;/p&gt;

&lt;p&gt;One potentially solution could be:&lt;/p&gt;

&lt;p&gt;1. add a new normalisation function in RMB called &lt;tt&gt;stripPunctuation&lt;/tt&gt;. This function would remove all punctuation and whitespace from a given field before creating an index, e.g a callNumber like &quot;a/b/c 123-3&quot; would result in &quot;abc1233&quot;. When enabled for a field, this function would also apply during search.&lt;/p&gt;

&lt;p&gt;2. Have the UI expand the search into an OR expression across three fields: callNumberPrefix, callNumber, callNumberSuffix like so:&lt;/p&gt;

&lt;p&gt;given a search for &quot;a bc d&quot; the UI would generate a query &lt;tt&gt;callNumberPrefix=a AND callNumber=bc AND callNumberSuffix=d OR callNumberPrefix=a AND callNumber=&quot;bc d&quot; OR callNumber=&quot;a bc&quot; and callNumberSuffix=d OR callNumber=&quot;a bc d&quot;&lt;/tt&gt;&lt;/p&gt;

&lt;p&gt;Ugliness of the solution noted. Ideas for something less ugly welcome.&lt;/p&gt;</comment>
                                                            <comment id="11813" author="63e2a2771b13d42998e4e706" created="Tue, 3 Dec 2019 12:45:45 +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;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Have the UI expand the search into an OR expression across three fields: callNumberPrefix, callNumber, callNumberSuffix like so:&lt;/p&gt;

&lt;p&gt;given a search for &quot;a bc d&quot; the UI would generate a query callNumberPrefix=a AND callNumber=bc AND callNumberSuffix=d OR callNumberPrefix=a AND callNumber=&quot;bc d&quot; OR callNumber=&quot;a bc&quot; and callNumberSuffix=d OR callNumber=&quot;a bc d&quot;&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;My understanding is that we are trying to move away from this kind of query construction in the UI and the goal of this feature is to provide a simple (from a clients perspective) way of doing this.&lt;/p&gt;</comment>
                                                            <comment id="11818" author="557058:f80403de-e149-421e-8750-af45c853402f" created="Tue, 3 Dec 2019 13:15:10 +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; - please see a more complete list of misc. call number searches listed in 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;UIIN-857&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UIIN-857&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Normalize Call numbers for Call number searching in  record&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;
            UIIN-857
        &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;
 (umbrella issue)&lt;/p&gt;</comment>
                                                            <comment id="11822" author="63e2a2771b13d42998e4e706" created="Tue, 3 Dec 2019 13:25:44 +0000"  >&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;&lt;/p&gt;

&lt;p&gt;Thanks for the reference. I&apos;m not actively investigating this issue, as I thought that &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; was exploring a solution with &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; within the core platform team.&lt;/p&gt;</comment>
                                                            <comment id="11827" author="557058:f80403de-e149-421e-8750-af45c853402f" created="Tue, 3 Dec 2019 16:36:59 +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; - &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; and I just talked about your proposal, and also discussed your suggestion using &lt;span class=&quot;error&quot;&gt;&amp;#91;spaces&amp;#93;&lt;/span&gt; between call number prefix, call number, and call number suffix, like in your example: given a search for &quot;a bc d&quot;. &lt;/p&gt;

&lt;p&gt;The problem is that e.g. the examples in 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;UIIN-857&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UIIN-857&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Normalize Call numbers for Call number searching in  record&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;
            UIIN-857
        &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;
, there are spaces in the call number itself - e.g.: &lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;H Germ 350/35: 1&lt;/li&gt;
	&lt;li&gt;H Germ 350/35: 2&lt;/li&gt;
	&lt;li&gt;F Germ 350/1&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Then H is a call number prefix in &lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;H Germ 350/35: 1&lt;/li&gt;
	&lt;li&gt;H Germ 350/35: 2&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;And F is a call number prefix in &lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;F Germ 350/1&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;But there is also two expected spaces in the call number e.g. Germ 350/35: 1&lt;/p&gt;

&lt;p&gt;So Laura and I was talking about if we in the search could use e.g. | &lt;span class=&quot;error&quot;&gt;&amp;#91;pipe&amp;#93;&lt;/span&gt; or _ &lt;span class=&quot;error&quot;&gt;&amp;#91;under score&amp;#93;&lt;/span&gt; as delimiter to indicate what is call number prefix, what is call number, what is call number suffix, e.g. H!Germ 350/35: 2, where H is the prefix, and Germ 350/35: 2 is the call number.&lt;/p&gt;

&lt;p&gt;And then what to do if we only have a call number and a call number suffix (which is typical use for Chalmers, as I have understood it). Maybe: |Germ 350/35: 1|Z (a made up example)?&lt;/p&gt;</comment>
                                                            <comment id="11833" author="557058:b787c0f1-34df-41c2-8585-c4aed346caec" created="Wed, 4 Dec 2019 09:18:08 +0000"  >&lt;p&gt;What kind of search are we talking about, an ordered browse or something closer to a keyword result set? I can&apos;t quite tell from the comments so far, and it&apos;s important.&lt;/p&gt;

&lt;p&gt;From the examples, it seems like the US libraries coming from Aleph and OLE expect an ordered browse, but the GBV libraries coming from LBS expect something more like a string search or relevance ranking. Is there agreement on the kind of result set?&lt;/p&gt;

&lt;p&gt;If we are talking about an ordered browse search, or even if there is a need to sort by call number, then there&apos;s a real need for a sort key. And the sort key algorithm might not be the same for all sites.&lt;/p&gt;

&lt;p&gt;But back to the inventory call number search, what kind of result set is expected? It&apos;s not entirely clear from what I have read.&lt;/p&gt;</comment>
                                                            <comment id="11838" author="557058:f80403de-e149-421e-8750-af45c853402f" created="Wed, 4 Dec 2019 12:19:25 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ab787c0f1-34df-41c2-8585-c4aed346caec&quot; class=&quot;user-hover&quot; rel=&quot;557058:b787c0f1-34df-41c2-8585-c4aed346caec&quot; data-account-id=&quot;557058:b787c0f1-34df-41c2-8585-c4aed346caec&quot; accountid=&quot;557058:b787c0f1-34df-41c2-8585-c4aed346caec&quot; rel=&quot;noreferrer&quot;&gt;Tod Olson&lt;/a&gt; - we are planning to implement following search options: &lt;/p&gt;

&lt;p&gt;Call number, keyword&lt;/p&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;Call number, eye readable&lt;/li&gt;
	&lt;li&gt;Call number, normalized&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Search for Call number are to be implemented as a search option in the drop down menu in both the Holdings segment and the Item segment:&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;Search options Holdings record&lt;/th&gt;
&lt;th class=&apos;confluenceTh&apos;&gt;Search options Item record&lt;/th&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;  &lt;span class=&quot;image-wrap&quot; style=&quot;&quot;&gt;&lt;a id=&quot;10629_thumb&quot; href=&quot;/rest/api/3/attachment/content/10629&quot; title=&quot;Ska&#776;rmavbild 2019-12-04 kl. 14.48.42.png&quot; file-preview-type=&quot;image&quot; file-preview-id=&quot;10629&quot; file-preview-title=&quot;Ska&#776;rmavbild 2019-12-04 kl. 14.48.42.png&quot;&gt;&lt;jira-attachment-thumbnail url=&quot;https://folio-org.atlassian.net/rest/api/3/attachment/thumbnail/10629?default=false&quot; jira-url=&quot;https://folio-org.atlassian.net/rest/api/3/attachment/thumbnail/10629&quot; filename=&quot;Ska&#776;rmavbild 2019-12-04 kl. 14.48.42.png&quot;&gt;&lt;img src=&quot;https://folio-org.atlassian.net/rest/api/3/attachment/thumbnail/10629&quot; data-attachment-name=&quot;Ska&#776;rmavbild 2019-12-04 kl. 14.48.42.png&quot; data-attachment-type=&quot;thumbnail&quot; data-media-services-id=&quot;fda14522-739f-4467-9433-b7400364675b&quot; data-media-services-type=&quot;file&quot; style=&quot;border: 0px solid black&quot; /&gt;&lt;/jira-attachment-thumbnail&gt;&lt;/a&gt;&lt;/span&gt;   &lt;/td&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;    &lt;span class=&quot;image-wrap&quot; style=&quot;&quot;&gt;&lt;a id=&quot;10628_thumb&quot; href=&quot;/rest/api/3/attachment/content/10628&quot; title=&quot;Ska&#776;rmavbild 2019-12-04 kl. 14.46.11.png&quot; file-preview-type=&quot;image&quot; file-preview-id=&quot;10628&quot; file-preview-title=&quot;Ska&#776;rmavbild 2019-12-04 kl. 14.46.11.png&quot;&gt;&lt;jira-attachment-thumbnail url=&quot;https://folio-org.atlassian.net/rest/api/3/attachment/thumbnail/10628?default=false&quot; jira-url=&quot;https://folio-org.atlassian.net/rest/api/3/attachment/thumbnail/10628&quot; filename=&quot;Ska&#776;rmavbild 2019-12-04 kl. 14.46.11.png&quot;&gt;&lt;img src=&quot;https://folio-org.atlassian.net/rest/api/3/attachment/thumbnail/10628&quot; data-attachment-name=&quot;Ska&#776;rmavbild 2019-12-04 kl. 14.46.11.png&quot; data-attachment-type=&quot;thumbnail&quot; data-media-services-id=&quot;293cf07b-6a4d-4be7-a711-8930dbaa5eb1&quot; data-media-services-type=&quot;file&quot; style=&quot;border: 0px solid black&quot; /&gt;&lt;/jira-attachment-thumbnail&gt;&lt;/a&gt;&lt;/span&gt;   &lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;&lt;/table&gt;
&lt;/div&gt;


&lt;p&gt;See list of examples on call number search: 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;UIIN-857&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UIIN-857&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Normalize Call numbers for Call number searching in  record&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;
            UIIN-857
        &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;

&lt;p&gt;And story for implementation: 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;UIIN-858&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UIIN-858&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Search. Holdings. Search option for Call numbers, eye readable (thin thread) &quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10309?size=medium&quot; /&gt;
            UIIN-858
        &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="11843" author="5af5ed55244bc90a106063c7" created="Tue, 10 Dec 2019 13:21:27 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ab787c0f1-34df-41c2-8585-c4aed346caec&quot; class=&quot;user-hover&quot; rel=&quot;557058:b787c0f1-34df-41c2-8585-c4aed346caec&quot; data-account-id=&quot;557058:b787c0f1-34df-41c2-8585-c4aed346caec&quot; accountid=&quot;557058:b787c0f1-34df-41c2-8585-c4aed346caec&quot; rel=&quot;noreferrer&quot;&gt;Tod Olson&lt;/a&gt; call number sort is covered in a separate feature: 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;UXPROD-2002&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-2002&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Implement Normalized Call Number for Sorting (LoC Parsing Only)&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-2002
        &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="11848" author="5af5ed55244bc90a106063c7" created="Thu, 30 Jan 2020 08:45:14 +0000"  >&lt;p&gt;This is  blocked awaiting the Core Platform work.  Marking blocked&lt;/p&gt;</comment>
                                                            <comment id="11852" author="5af5ed55244bc90a106063c7" created="Fri, 28 Feb 2020 11:45:27 +0000"  >&lt;p&gt;Hi &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 think a couple of the stories defining this feature don&apos;t belong here anymore (
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;UIIN-857&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UIIN-857&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Normalize Call numbers for Call number searching in  record&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;
            UIIN-857
        &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;UIIN-990&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UIIN-990&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Search. Item. Search option for Call numbers, eye readable (thin thread)&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10309?size=medium&quot; /&gt;
            UIIN-990
        &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;
).  Could you please split those off into another feature for Q2 and rename this one so that it&apos;s clear what we decided to do for Q1?  That will help us better track when this feature is complete.  Thanks!&lt;/p&gt;</comment>
                                                            <comment id="11856" author="5af5ed55244bc90a106063c7" created="Mon, 2 Mar 2020 15:11:14 +0000"  >&lt;p&gt;Hi &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 think, if we remove the two stories that are out of scope for Q1, this feature could be moved into In review.  &lt;/p&gt;</comment>
                                                            <comment id="11860" author="5af5ed55244bc90a106063c7" created="Mon, 16 Mar 2020 10:00:57 +0000"  >&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; can you please remove the two extraneous stories and mark this closed?&lt;/p&gt;</comment>
                                                            <comment id="11865" author="557058:f80403de-e149-421e-8750-af45c853402f" created="Mon, 16 Mar 2020 10:06:20 +0000"  >&lt;p&gt;Okay &lt;img class=&quot;emoticon&quot; src=&quot;/images/icons/emoticons/check.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt;. Done.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                                                <inwardlinks description="is blocked by">
                                        <issuelink>
            <issuekey id="11004">UXPROD-1626</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10008">
                    <name>Defines</name>
                                                                <inwardlinks description="is defined by ">
                                        <issuelink>
            <issuekey id="56083">MODINVSTOR-444</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="48010">UIIN-858</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="48303">UIIN-990</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="47758">UIIN-721</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="47759">UIIN-722</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10006">
                    <name>Gantt End to Start</name>
                                            <outwardlinks description="has to be done before">
                                        <issuelink>
            <issuekey id="10212">UXPROD-1714</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="11291">UXPROD-2002</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="10628" name="Ska&#776;rmavbild 2019-12-04 kl. 14.46.11.png" size="106565" author="557058:f80403de-e149-421e-8750-af45c853402f" created="Wed, 4 Dec 2019 13:50:41 +0000"/>
                            <attachment id="10629" name="Ska&#776;rmavbild 2019-12-04 kl. 14.48.42.png" size="94954" author="557058:f80403de-e149-421e-8750-af45c853402f" created="Wed, 4 Dec 2019 13:50:41 +0000"/>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                    <customfield id="customfield_10048" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Analysis Estimate</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10087"><![CDATA[Small < 3 days]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10049" key="com.atlassian.jira.plugin.system.customfieldtypes:userpicker">
                        <customfieldname>Analysis Estimator</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>557058:f80403de-e149-421e-8750-af45c853402f</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                            <customfield id="customfield_10053" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Back End Estimate</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10121"><![CDATA[Medium < 5 days]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10054" key="com.atlassian.jira.plugin.system.customfieldtypes:userpicker">
                        <customfieldname>Back End Estimator</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>5bffed5e2434bf3a1a91d37a</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <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="10171"><![CDATA[Prokopovych]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10014" key="com.pyxis.greenhopper.jira:gh-epic-link">
                        <customfieldname>Epic Link</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue key="$xmlutils.escape($text)">Inventory</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10056" key="com.atlassian.jira.plugin.system.customfieldtypes:textarea">
                        <customfieldname>Estimation Notes and Assumptions</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Outstanding questions: &lt;br/&gt;
* Implemented as a search index or as a persisted field containing the normalized version of the call number?&lt;br/&gt;
* Hard-code normalization rules or configurable?</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10050" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Front End Estimate</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10097"><![CDATA[Medium < 5 days]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10051" key="com.atlassian.jira.plugin.system.customfieldtypes:userpicker">
                        <customfieldname>Front End Estimator</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>5bffed5e2434bf3a1a91d37a</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10052" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Front-End Confidence factor</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10107"><![CDATA[Low]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10063" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>PO Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>125.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10064" key="com.atlassian.jira.plugin.system.customfieldtypes:textarea">
                        <customfieldname>PO Ranking Note</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>CW: Aligned PO rank with Calculated Total rank</customfieldvalue>

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

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10071" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: 5Colleges (Full Jul 2021)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10223"><![CDATA[R1]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10067" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: Chalmers (Impl Aut 2019)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10204"><![CDATA[R2]]></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="10208"><![CDATA[R1]]></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_10073" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: FLO (MVP Sum 2020)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10233"><![CDATA[R1]]></customfieldvalue>

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

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                    <customfield id="customfield_10077" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: Hungary (MVP End 2020)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10253"><![CDATA[R1]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10078" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: Lehigh (MVP Summer 2020)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10258"><![CDATA[R1]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_10085" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: MO State (MVP June 2020)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10294"><![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="10314"><![CDATA[R1]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10091" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: U of AL (MVP Oct 2020)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10324"><![CDATA[R1]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                    <customfield id="customfield_10076" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: hbz (TBD)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10248"><![CDATA[R1]]></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>Mon, 22 Apr 2019 16:34:04 +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>