<!-- 
RSS generated by JIRA (1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d) at Fri Feb 09 00:34:24 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-3737] Title level request: Future enhancements</title>
                <link>https://folio-org.atlassian.net/browse/UXPROD-3737</link>
                <project id="10000" key="UXPROD">UX Product</project>
                    <description>&lt;p&gt;&lt;b&gt;Current situation or problem&lt;/b&gt;: Title level requests (complete) was implemented in R1 2022 Lotus and R2 2022 Morning Glory. This feature is to collect enhancement requests for future development.&lt;/p&gt;

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

&lt;ul&gt;
	&lt;li&gt;Item look-up by title (Title level requests offers title look-up tool. Folks want it for item level requests too)&lt;/li&gt;
	&lt;li&gt;Accordion heading &quot;Open - Not yet filled&quot; should be changed so that it does not match the request status, open - not yet filled&lt;/li&gt;
	&lt;li&gt;The publication field in Request details is populated by dateOfPublication. Because dateOfPublication allows for alphanumerics, if there is a date like &quot;c1964&quot;, it will not display and &quot;-&quot; will show instead. To fix this we should use publicationPeriod. For more details, see comments in 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;UIREQ-801&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UIREQ-801&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;TLR: Title information section does not pick up a publication date when it&amp;#39;s followed or preceded by another character&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10303?size=medium&quot; /&gt;
            UIREQ-801
        &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;/li&gt;
	&lt;li&gt;Identify orphaned requests - those that were submitted but are not able to be filled, either because no item records exist, or the associated patron is not eligible to request any of the items on the instance.
	&lt;ul&gt;
		&lt;li&gt;Identify TLR where the item status have changed since the TLR was placed that makes them ineligible for TLR.&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
	&lt;li&gt;&lt;del&gt;Only show the request type(s) that can be fulfilled in the request page drop down. At the moment, the User must choose from the dropdown.&lt;/del&gt; Included in previous release.&lt;/li&gt;
	&lt;li&gt;Improvment of the loans display.&lt;br/&gt;
When a user placed a TLR, that should be visible in the Open loans displays of all current borrowers. Right now, you don&apos;t find any indication about the TLR there. Only when you try to renew an item, you receive a message. In the Open loans display the Value in Column &#8220;Request&#8221; is &#8220;0&#8221; for the item, because there is no request on THE SPECIFIC ITEM. But the value for each borrowed item of the title should be &#8220;1&#8221;&#160; to improve useability.
	&lt;ul&gt;
		&lt;li&gt;Use case:&lt;br/&gt;
A user is asking a staff member, why she/he cannot renew items. The staff member wants to check in the loan display if a TLR is placed and causing the declined renewal. In case that the user has many open loans, and does not remember which item she/he could not renew, it is absolutely necessary, that the staff member finds some useful information there.&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
	&lt;li&gt;TLR: Move page request when item is not found.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Tested with page and hold allowed. You have two copies of a book, one checked out and one available (copy X). TLR results in page on copy X. When you look for the paged copy you can&#8217;t find it on the shelf. You mark copy X as missing/long missing/or something else.&lt;/p&gt;

&lt;p&gt;Expected result: Page is automatically transformed into a hold (or page on another copy if there would have been other available items). Alternatively, you can manually use &#8220;move the request&#8221; and change it to a hold when there are no items with status available.&lt;/p&gt;

&lt;p&gt;&lt;b&gt;In scope&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;&lt;b&gt;Out of scope&lt;/b&gt;&lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;&lt;del&gt;We need the item call number in the display of the result list of requests (middle pane). This would help us managing our requests workflow especially in the stacks. Could this be included or worked on?&lt;/del&gt; &lt;a href=&quot;https://folio-org.atlassian.net/browse/UIREQ-735&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;&lt;del&gt;https://folio-org.atlassian.net/browse/UIREQ-735&lt;/del&gt;&lt;/a&gt; &lt;del&gt;&quot;Include call number in display of result list of Requests App&quot;&lt;/del&gt; See&#160;
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;UXPROD-3761&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-3761&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Include call number in display of result list of Requests App&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-3761
        &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;/li&gt;
	&lt;li&gt;&lt;del&gt;The receiving app should display that the instance has unfulfilled requests, as it currently does. Now there is no indication that the received item should be handled with urgency. It must first be checked in, which we normally don&apos;t do with newly received items as we want them to keep status In process.&lt;/del&gt; See 
    &lt;span class=&quot;jira-issue-macro&quot; data-jira-key=&quot;UXPROD-3936&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-3936&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Show in receiving that there is a title level request on a receiving title&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-3936
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-complete jira-macro-single-issue-export-pdf&quot;&gt;Draft&lt;/span&gt;
            &lt;/span&gt;
&lt;/li&gt;
	&lt;li&gt;&lt;del&gt;Disallowing title level requesting for items in certain locations (or libraries.) Use case: A single FOLIO institution has several general collection libraries and one library that has special collections. The general collection libraries want to have title-level requesting; the library with special collections does not.&lt;/del&gt;&#160; &#160;See&#160;
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;UXPROD-3980&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-3980&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;TLR: disallow requesting for titles/items in specific locations &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-3980
        &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;/li&gt;
	&lt;li&gt;&lt;del&gt;Implementation of circ rules (either existing or new) to allow for prevention of requests if patron is not eligible. E.g. if instance A has items X, Y and Z, and the patron is not eligible to place an item level request on X, Y or Z, than they should not be able to place a title-level request on instance A.&lt;/del&gt;
	&lt;ul&gt;
		&lt;li&gt;&lt;del&gt;Limit what items can be have a TLR placed on them based on a key in the Request policy.&lt;/del&gt; See&#160;
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;UXPROD-3981&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-3981&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;TLR: Circulation rules on items to be followed by title level request holds&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-3981
        &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;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;&lt;b&gt;Use case(s)&lt;/b&gt;&lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;
	&lt;ul&gt;
		&lt;li&gt;
		&lt;ul&gt;
			&lt;li&gt;Circ rules use cases*&lt;/li&gt;
		&lt;/ul&gt;
		&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;As a staff member I want to restrict what items can have a TLR placed on them. Examples:&lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;We want to allow requests on monographs but not serials or thesis.&lt;/li&gt;
	&lt;li&gt;We do not want to allow TLR on items in specific locations; such as new book shelf or new and note worth, but still allow TLR on copies in the regular stacks.&lt;/li&gt;
	&lt;li&gt;We may not want to allow undergraduates, or resident cards to place TLR requests but allow all other User groups.&lt;/li&gt;
	&lt;li&gt;If an instance record has a mix of item types, some allowing TLR and some ILR, this should be recognized by the system. If a patron is allowed via the policy to place a TLR it should be allowed, but only include those items that are TLR eligible.&#160;&lt;/li&gt;
	&lt;li&gt;If an items status changes to so that it is TLR eligible this should be recognized by outstanding TLRs for that instance record.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;&lt;b&gt;Proposed solution/stories&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;&lt;b&gt;Links to additional info&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;&lt;b&gt;Questions&lt;/b&gt;&lt;/p&gt;</description>
                <environment></environment>
        <key id="13303">UXPROD-3737</key>
            <summary>Title level request: Future enhancements</summary>
                <type id="10006" iconUrl="https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10307?size=medium">Umbrella</type>
                            <parent id="10049">UXPROD-790</parent>
                                    <priority id="10005" iconUrl="https://dev.folio.org/assets/jira-priority/tbd.svg">TBD</priority>
                        <status id="10000" iconUrl="https://folio-org.atlassian.net/images/icons/statuses/generic.png" description="(Migrated on 4 Feb 2024 13:41 UTC)">Draft</status>
                    <statusCategory id="2" key="new" colorName="blue-gray"/>
                                    <resolution id="-1">Unresolved</resolution>
                                                        <assignee accountid="5d794c218ce6b60c3810eb8a">Stephanie Buck</assignee>
                                                                <reporter accountid="5d794c218ce6b60c3810eb8a">Stephanie Buck</reporter>
                                    <labels>
                            <label>loc</label>
                            <label>resourceaccess</label>
                    </labels>
                <created>Fri, 1 Jul 2022 13:54:14 +0000</created>
                <updated>Mon, 29 Jan 2024 20:16:36 +0000</updated>
                                                                                <due></due>
                            <votes>0</votes>
                                    <watches>9</watches>
                                                                <comments>
                                                            <comment id="18363" author="557058:eb198214-3032-45c9-9781-9967c26deb3f" created="Wed, 11 Jan 2023 14:56:18 +0000"  >&lt;p&gt;I added a few use cases for TLR and circ rules. IMO it may be useful to pull this feature out of this Jira into a separate one and discuss with RA-SIG. I also think this point:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;&lt;em&gt;Disallowing title level requesting for items in certain locations (or libraries.) Use case: A single FOLIO institution has several general collection libraries and one library that has special collections. The general collection libraries want to have title-level requesting; the library with special collections does not.&lt;/em&gt;&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;can be address via a requests policy and circ rules, since circulation rules criteria can include location data.&lt;/p&gt;</comment>
                                                            <comment id="18364" author="5d794c218ce6b60c3810eb8a" created="Wed, 18 Jan 2023 21:18:22 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Aeb198214-3032-45c9-9781-9967c26deb3f&quot; class=&quot;user-hover&quot; rel=&quot;557058:eb198214-3032-45c9-9781-9967c26deb3f&quot; data-account-id=&quot;557058:eb198214-3032-45c9-9781-9967c26deb3f&quot; accountid=&quot;557058:eb198214-3032-45c9-9781-9967c26deb3f&quot; rel=&quot;noreferrer&quot;&gt;Thomas Trutt&lt;/a&gt;, thank you. We&apos;re currently troubleshooting 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;CIRC-1693&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/CIRC-1693&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Item level circulation policies not being followed by title level requests&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10303?size=medium&quot; /&gt;
            CIRC-1693
        &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;
. It is specific to circulation rules being checked upon item check in. It would be helpful to have a conversation about when and how other circulation rules should be followed. It&apos;s tempting to create more tickets for that, but this is reminding me that it&apos;s feature level work, not bug work.&#160;&lt;/p&gt;</comment>
                                                            <comment id="18365" author="5d794c218ce6b60c3810eb8a" created="Tue, 24 Jan 2023 20:21:22 +0000"  >&lt;p&gt;Some enhancements are being split into smaller features as of January 2023 and have been moved to the &quot;out of scope&quot; section.&lt;/p&gt;</comment>
                                                            <comment id="18366" author="712020:9ea92d9e-67f8-4e10-806c-113e0f71994d" created="Wed, 25 Jan 2023 13:31:22 +0000"  >&lt;p&gt;Improvment of the loans display.&lt;br/&gt;
When a user placed a TLR, that should be visible in the Open loans displays of all current borrowers. Right now, you don t find any indication about the TLR there. Only when you try to renew an item, you receive a message. In the Open loans display the Value in Column &#8220;Request&#8221; is &#8220;0&#8221; for the item, because there is no request on THE SPECIFIC ITEM. But the value for each borrowed item of the title should be &#8220;1&#8221;&#160; to improve userbility.&lt;/p&gt;


&lt;p&gt;Use case:&lt;br/&gt;
A user is asking a staff member, why she/he cannot renew items. The staff member wants to check in the loan display if a TLR is placed and causing the declined renewal. In case that the user has many open loans, and does not remember which item she/he could not renew, it is absolutely necessary, that the staff member finds some&#160; useful information there.&lt;/p&gt;</comment>
                                                            <comment id="18367" author="5d794c218ce6b60c3810eb8a" created="Tue, 31 Jan 2023 22:33:12 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=62a96ae7192edb006f9f1bf9&quot; class=&quot;user-hover&quot; rel=&quot;62a96ae7192edb006f9f1bf9&quot; data-account-id=&quot;62a96ae7192edb006f9f1bf9&quot; accountid=&quot;62a96ae7192edb006f9f1bf9&quot; rel=&quot;noreferrer&quot;&gt;Khalilah Gambrell&lt;/a&gt;, this is a &quot;bucket&quot; feature to collect future enhancements. It should not be sized/scoped for development as a whole.&#160;&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10008">
                    <name>Defines</name>
                                                                <inwardlinks description="is defined by ">
                                        <issuelink>
            <issuekey id="26232">UIREQ-793</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="13404">UXPROD-3936</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="13328">UXPROD-3458</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="13296">UXPROD-3528</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </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_10057" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Development Team</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10187"><![CDATA[Vega]]></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)">Requests</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10063" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>PO Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                    <customfield id="customfield_10106" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>RCA Group</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10367"><![CDATA[TBD]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10019" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i06ow8:</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="10203"><![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="10214"><![CDATA[R2]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10046" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Release</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10020"><![CDATA[Not Scheduled]]></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>Wed, 11 Jan 2023 14:56:18 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                </customfields>
    </item>
</channel>
</rss>