<!-- 
RSS generated by JIRA (1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d) at Fri Feb 09 00:12:38 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-1061] Title-Level Requests (Basic)</title>
                <link>https://folio-org.atlassian.net/browse/UXPROD-1061</link>
                <project id="10000" key="UXPROD">UX Product</project>
                    <description>&lt;p&gt;&lt;font color=&quot;#205081&quot;&gt;Current implementation of requests applies requests to items, but users (especially patrons) don&apos;t usually care which copy (item) they get - they just care about getting the title (instance).&lt;br/&gt;
&lt;br/&gt;
The scope of this feature is to implement what is needed to support title-level requesting.  &lt;br/&gt;
&lt;br/&gt;
&lt;font color=&quot;#14892c&quot;&gt;&lt;/font&gt;Baseline requirements: &lt;br/&gt;
0) Title-level requests assume that all circulation logic (business logic) will reside within FOLIO and the discovery/presentation layer will only have the conditionalities to request and display the response from FOLIO&apos;s API&apos;s.&lt;br/&gt;
1) Title level requests focus on a single bibliographic/instance record (or equivalent, as CODEX and methods of title/instance/manifestation-level grouping may be built out in the future).&lt;br/&gt;
2) Title level requests focus on multiple copies of the same work, not separate volumes in a continuing work.&lt;br/&gt;
3) Title level requests assume the library user does not care which copy of the intellectual work (to use the FRBR vocabulary) or the instance (to use the FOLIO terminology) attached to a single or multiple holdings record. The library patron cares about obtaining a physical copy of the intellectual work.&lt;br/&gt;
4) For journal/serial records of a continuing work, item-specific requests can allow for specific volumes/years/parts to be requested.&lt;br/&gt;
4a) For journal/serial/continuing works with any/sizeable volume/years/parts with no individual item record or barcode), the Hold/Request form can compensate with a free text or NOTE field to allow the library user to specify which volume(s) is/are being requested.&lt;br/&gt;
4b) For journal/serial/continuing works with any/sizeable volume/years/parts with no individual item record or barcode) due to a Summary Holdings statement (or equivalent), the Hold/Request form can compensate with a free text or NOTE field to allow the library user to specify which volume is being requested.&lt;/font&gt;&lt;font color=&quot;#14892c&quot;&gt;&lt;/font&gt;&lt;br/&gt;
5) Library can configure hold default at the tenant level.  Some libraries will want an actual hold issued and other will choose to always issue a recall instead of an actual hold.  In all cases below, when the discovery service issues a hold, this setting will determine of FOLIO actually issues a hold or a recall.&lt;br/&gt;
6) Follows all circulation policy as configured in circulation.&lt;/p&gt;

&lt;p&gt;Discovery to FOLIO workflow:&lt;br/&gt;
I. The Discovery user is able to login to the campus SSO authentication system to personalize, as in the Identity provider returns a Y/N authentication flag, PLUS the FOLIO user&apos;s ID number (as in, a potentially anonymous, non-PII identifier that correlates the institutional user with their record in FOLIO) &lt;br/&gt;
II. The successful authentication allows the Discovery user to select/submit a hold/request button/operator on a physical item record.&lt;br/&gt;
III. THE Discovery RTAC+ API&apos;s send the authentication session cookie to FOLIO and uses the FOLIO user ID to request patron if patron has the rights to issue a request.&lt;br/&gt;
IV. If the user has the rights to issue a request, the discovery RTAC+ API&apos;s send the create hold/request action to FOLIO&lt;br/&gt;
V. FOLIO checks if any copies exist where loanable is true and if requests can be placed (do they have circ rights, or only reference copies or no copies).  If no copies exist return reason why via API to Discovery service.&lt;br/&gt;
VI. If a copy is found that can circulate and it&apos;s not checked out, a page is issued on behalf of the patron on the 1st available copy.&lt;br/&gt;
VI. If all copies are out on loan, a hold/recall will be placed on the item with the fewest existing holds/recalls and the available date closest to today&lt;br/&gt;
VII. FOLIO returns status via API to Discovery service about success or failure of the request.&lt;/p&gt;

&lt;p&gt;Acceptance criteria:&lt;br/&gt;
1. EDS or any other discovery service can issue holds successfully by patron while not adding functionality to issue pages or holds by item &lt;br/&gt;
2. EDS or any other discovery service can request and display holds (that represent FOLIO holds and/pages by item) successfully by patron while not adding functionality to issue pages or holds by item &lt;br/&gt;
3. EDS or any other discovery service can cancel/delete holds (that represent FOLIO holds and/pages by item) successfully by patron while not adding functionality to issue pages or holds by item &lt;br/&gt;
4. Get, Post &amp;amp; Delete in mod-circulation will modified with a new request type that operates on a title basis but internally to FOLIO as by item basis.&lt;br/&gt;
5. Greater than 80% test coverage&lt;br/&gt;
6. Deployed and merged into GIT with the FOLIO quarterly release.&lt;br/&gt;
7. For testing to be complete, and external discovery service will need to be configured.  May require core platform team tasks.&lt;/p&gt;

&lt;p&gt;Next Steps: &lt;br/&gt;
1. Further define/refine stories for breakdown&lt;br/&gt;
2. Define dependencies on core platform team&lt;br/&gt;
3. Make sure existing pattern set by renewals can accommodate this feature.&lt;/p&gt;



</description>
                <environment></environment>
        <key id="10660">UXPROD-1061</key>
            <summary>Title-Level Requests (Basic)</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="10049">UXPROD-790</parent>
                                    <priority id="10000" iconUrl="https://dev.folio.org/assets/jira-priority/jira-p1.svg">P1</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:8629b273-56f1-466d-b7c7-5cbac0c3379b">Magda Zacharska</assignee>
                                                                <reporter accountid="5af5ed55244bc90a106063c7">Cate Boerema</reporter>
                                    <labels>
                            <label>q1-2019-spillover</label>
                            <label>q2.2-2019</label>
                            <label>requests</label>
                    </labels>
                <created>Wed, 29 Aug 2018 14:45:37 +0000</created>
                <updated>Wed, 3 Jan 2024 16:57:37 +0000</updated>
                            <resolved>Wed, 26 Jun 2019 14:09:07 +0000</resolved>
                                                    <fixVersion>Q2 2019</fixVersion>
                                        <due></due>
                            <votes>0</votes>
                                    <watches>14</watches>
                                                                <comments>
                                                            <comment id="13044" author="5af5ed55244bc90a106063c7" created="Wed, 29 Aug 2018 14:51:13 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=712020%3Aa7c22549-b241-4b0e-9f9e-8643d2c55826&quot; class=&quot;user-hover&quot; rel=&quot;712020:a7c22549-b241-4b0e-9f9e-8643d2c55826&quot; data-account-id=&quot;712020:a7c22549-b241-4b0e-9f9e-8643d2c55826&quot; accountid=&quot;712020:a7c22549-b241-4b0e-9f9e-8643d2c55826&quot; rel=&quot;noreferrer&quot;&gt;Tania Fersenheim&lt;/a&gt;, has this come up in your discussions?   &lt;/p&gt;

&lt;p&gt;IIRC (and I did go digging around in &lt;a href=&quot;https://folio-org.atlassian.net/wiki/display/RA/2017-06-19+Resource+Access+Meeting+Notes&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;old RA SIG notes&lt;/a&gt;), both item and title-level requesting were desired, but the thought was that, fundamentally, requests need to be associated with items for the proper functioning of the system.  The notes from the discussion are pretty vague, but I seem to recall that title-level requests were thought of as kind of an extension of item-level requesting.  That business logic (perhaps configurable) would need to be added to determine which item to put the request on when only title is specified by the requester.  The determination would be made based on things like which item is due back soonest, which has the longest request queue etc.  Does that sound right?  Would you please raise this with the sub-group and update this feature with your learnings?&lt;/p&gt;</comment>
                                                            <comment id="13047" author="5af5ecdb772036612ff61cf1" created="Wed, 29 Aug 2018 15:11:39 +0000"  >&lt;p&gt;If FOLIO moves forward with item level requests only, what happens when a student (through an OPAC or Discovery service) requests an item and that particular item or copy is currently on loan to a professor on campus?  Who manages what happens? &lt;/p&gt;</comment>
                                                            <comment id="13052" author="712020:a7c22549-b241-4b0e-9f9e-8643d2c55826" created="Wed, 29 Aug 2018 15:24:21 +0000"  >&lt;p&gt;The decision to do item-level first predates my tenure on the RA SIG, but I do know that item-level requests are required for several critical functions, e.g. NCIP RequestItem which will be needed for integration with resource sharing systems such as Relais.&lt;/p&gt;</comment>
                                                            <comment id="13055" author="712020:a7c22549-b241-4b0e-9f9e-8643d2c55826" created="Wed, 29 Aug 2018 15:46:16 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5ecdb772036612ff61cf1&quot; class=&quot;user-hover&quot; rel=&quot;5af5ecdb772036612ff61cf1&quot; data-account-id=&quot;5af5ecdb772036612ff61cf1&quot; accountid=&quot;5af5ecdb772036612ff61cf1&quot; rel=&quot;noreferrer&quot;&gt;Hkaplanian&lt;/a&gt; - If the item is on loan, and the patron has made a Recall request, the item will be recalled from the patron who has it on loan, according to the criteria that the institution sets up in FOLIO request policies.&lt;br/&gt;
If the item is on loan, and the patron has made a Hold request, when the item is eventually returned to the library it will be held for the patron who requested it.&lt;br/&gt;
FOLIO manages that behind the scenes.  No staff intervention is needed, unless staff wish to manually alter the standard process for some reason.&lt;/p&gt;</comment>
                                                            <comment id="13059" author="5af5ed55244bc90a106063c7" created="Fri, 28 Sep 2018 12:29:35 +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; and &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A63e17413-51f9-4a7c-910b-544728833e0f&quot; class=&quot;user-hover&quot; rel=&quot;557058:63e17413-51f9-4a7c-910b-544728833e0f&quot; data-account-id=&quot;557058:63e17413-51f9-4a7c-910b-544728833e0f&quot; accountid=&quot;557058:63e17413-51f9-4a7c-910b-544728833e0f&quot; rel=&quot;noreferrer&quot;&gt;Matt Connolly&lt;/a&gt;, this new feature needs to be estimated.  &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=712020%3Aa7c22549-b241-4b0e-9f9e-8643d2c55826&quot; class=&quot;user-hover&quot; rel=&quot;712020:a7c22549-b241-4b0e-9f9e-8643d2c55826&quot; data-account-id=&quot;712020:a7c22549-b241-4b0e-9f9e-8643d2c55826&quot; accountid=&quot;712020:a7c22549-b241-4b0e-9f9e-8643d2c55826&quot; rel=&quot;noreferrer&quot;&gt;Tania Fersenheim&lt;/a&gt; will add more details but she thinks it probably warrants a meeting/discussion.  Please reach out to her for more info.&lt;/p&gt;
</comment>
                                                            <comment id="13063" author="5af9cc2a5f0d5b06c28aa731" created="Mon, 5 Nov 2018 19:00:39 +0000"  >&lt;p&gt;Marc Keepper adding detail to this Feature in order to add User Stories and build out the Title-Level Request development for FOLIO-EDS patron empowerment integration.&lt;/p&gt;</comment>
                                                            <comment id="13065" author="5af5ecdb772036612ff61cf1" created="Tue, 6 Nov 2018 19:31:01 +0000"  >&lt;p&gt;Added some stories that I believe support RTAC functionality&lt;/p&gt;</comment>
                                                            <comment id="13067" author="5af5ed55244bc90a106063c7" created="Tue, 15 Jan 2019 08:35:35 +0000"  >&lt;p&gt;Due to reduced Core team capacity, this needs to be removed from Q1 2019 release.&lt;/p&gt;</comment>
                                                            <comment id="13069" author="5d6eeadef989e00d8c7e897b" created="Fri, 29 Mar 2019 22:15:59 +0000"  >&lt;p&gt;Comment from the March Meeting : NEEDED would love to test it soon&lt;/p&gt;</comment>
                                                            <comment id="13071" author="557058:5ceb2fe3-7fa0-4074-babb-a5941cdcf312" created="Wed, 21 Aug 2019 15:01:02 +0000"  >&lt;p&gt;This is really not clear.  Under baseline requirements part 2) says &quot;Title level requests focus on multiple copies of the same work, not separate volumes in a continuing work.&quot;  Then part 4) goes on to discuss continuing works.  I don&apos;t know what this means.&lt;/p&gt;</comment>
                                                            <comment id="13073" author="557058:5ceb2fe3-7fa0-4074-babb-a5941cdcf312" created="Wed, 21 Aug 2019 15:09:59 +0000"  >&lt;p&gt;The Estimation Notes and Assumptions says &quot;I am assuming a solution where the title (instance)-level request is immediately (at creation time) converted to a regular item-level request,&lt;br/&gt;
based on some simple logic, like take the first available item and if nothing is available the first one where the due date is soonest.&quot; &lt;/p&gt;

&lt;p&gt;This would not be good.  We would want a hold queue that does not assign the request to an item until the item is actually available.  The one due soonest my not be the one returned first.  It may never come back at all.  Then the request is stuck on a lost item that may not be fixed for a long time.&lt;/p&gt;</comment>
                                                            <comment id="13077" author="5af9cc2a5f0d5b06c28aa731" created="Wed, 21 Aug 2019 22:44:48 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A5ceb2fe3-7fa0-4074-babb-a5941cdcf312&quot; class=&quot;user-hover&quot; rel=&quot;557058:5ceb2fe3-7fa0-4074-babb-a5941cdcf312&quot; data-account-id=&quot;557058:5ceb2fe3-7fa0-4074-babb-a5941cdcf312&quot; accountid=&quot;557058:5ceb2fe3-7fa0-4074-babb-a5941cdcf312&quot; rel=&quot;noreferrer&quot;&gt;Lloyd Chittenden&lt;/a&gt;l You wrote: This is really not clear. Under baseline requirements part 2) says &quot;Title level requests focus on multiple copies of the same work, not separate volumes in a continuing work.&quot; Then part 4) goes on to discuss continuing works. I don&apos;t know what this means.&quot;&lt;/p&gt;

&lt;p&gt;Let me add an example to see if it helps.&lt;/p&gt;

&lt;p&gt;Title level requests focus on multiple copies of the same work, not separate volumes in a continuing work.&quot;&lt;/p&gt;

&lt;p&gt;&lt;b&gt;Easiest example&lt;/b&gt;:&lt;br/&gt;
Single instance record, &lt;br/&gt;
Single Holdings record with &lt;br/&gt;
3 Item Records attached/linked to the Single Holdings Record with copies 1, 2 &amp;amp; 3 of the same book. &lt;br/&gt;
3 different copies to 3 different Item Records: copy 1, copy 2, copy 3. &lt;br/&gt;
With this use case, the patron/user does not really care which of these 3 copies she receives in response to a request (or hold or page)&lt;/p&gt;

&lt;p&gt;&lt;b&gt;Continuing work with much of the scenario adds a bit of complexity:&lt;/b&gt;&lt;br/&gt;
Single instance record, &lt;br/&gt;
Single Holdings record with &lt;br/&gt;
3 Item Records attached/linked to the Single Holdings Record with volumes 1, 2 &amp;amp; 3 of the same multi-volume work &lt;br/&gt;
3 different volumes in 3 different Item Records: volume 1, volume 2, volume 3. (All copies are copy 1, but different volumes) &lt;br/&gt;
With this scenario, the patron/user intent is not yet clear. &lt;br/&gt;
&lt;b&gt;&lt;em&gt;User Intent Options:&lt;/em&gt;&lt;/b&gt; &lt;br/&gt;
Does the user want all 3 volumes of the work?&lt;br/&gt;
A single volume? If yes, which one? &lt;br/&gt;
Two volumes, but not all three? If yes, which yes &amp;amp; which no?&lt;/p&gt;

&lt;p&gt;&lt;b&gt;Request: Does that help at all?&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;If yes or not, please let me know either way. If yes, but more detail about continuing works, please let me know!&lt;/p&gt;</comment>
                                                            <comment id="13081" author="557058:5ceb2fe3-7fa0-4074-babb-a5941cdcf312" created="Wed, 21 Aug 2019 23:01:45 +0000"  >&lt;p&gt;I am concerned about the scenario where there are multiple holdings records with multiple items attached and they are all checked out in a consortium.  Such as a DVD of a TV series like Game of Thrones.  Let&apos;s say the user wants season 6.  A title level request is bad because they could get any season.  An item level request is bad because we don&apos;t know which item will come back first, or at all.  Then some other user could get the next available one even if they put in a later request, or this request could get stuck for a long time if it is not returned.  I want to see a request queue at the holdings level that will give the first item attached to that holding anywhere in the consortium to the next person in the queue.  This is a very common situation for a public library consortium.&lt;/p&gt;</comment>
                                                            <comment id="13084" author="5af5ecdb772036612ff61cf1" created="Thu, 22 Aug 2019 12:14:17 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A5ceb2fe3-7fa0-4074-babb-a5941cdcf312&quot; class=&quot;user-hover&quot; rel=&quot;557058:5ceb2fe3-7fa0-4074-babb-a5941cdcf312&quot; data-account-id=&quot;557058:5ceb2fe3-7fa0-4074-babb-a5941cdcf312&quot; accountid=&quot;557058:5ceb2fe3-7fa0-4074-babb-a5941cdcf312&quot; rel=&quot;noreferrer&quot;&gt;Lloyd Chittenden&lt;/a&gt;, Right now FOLIO lacks consortia functionality.  Those features are currently being defined in the FOLIO Consortia SIG.  This would be a great topic to bring up with that group.  Also, this feature as defined is a bit of a stop gap measure until some other aspects of FOLIO are built.  We do expect this functionality to change and greatly improve in later FOLIO releases.  &lt;/p&gt;</comment>
                                                            <comment id="13088" author="5af9cc2a5f0d5b06c28aa731" created="Thu, 22 Aug 2019 12:21:01 +0000"  >&lt;p&gt;Lloyd, agreed this is very common. The scenario is also very true when academic libraries have backfile runs of continuing works like journals/serials.&lt;/p&gt;

&lt;p&gt;The use case you provided is very common for public libraries, namely: &quot;there are multiple holdings records with multiple items attached and they are all checked out in a consortium. Such as a DVD of a TV series like Game of Thrones. Let&apos;s say the user wants season 6. A title level request is bad because they could get any season. An item level request is bad because we don&apos;t know which item will come back first, or at all. Then some other user could get the next available one even if they put in a later request, or this request could get stuck for a long time if it is not returned. I want to see a request queue at the holdings level that will give the first item attached to that holding anywhere in the consortium to the next person in the queue. This is a very common situation for a public library consortium.&quot;&lt;/p&gt;

&lt;p&gt;In response to this use case, I believe that the existing title level Holding/Request queue in EDS and participating library systems (like OCLC WMS, and FOLIO) has always allowed the first available copy to become available to the first/earliest patron in the Hold/Request queue. That works well without the extra layers of complexity of multiple holdings/items/copies corresponding to multiple libraries (members of a consortium) and each items record may not be a copy number but a specific volume, issue, part, season (or other content/organizational unit).&lt;/p&gt;

&lt;p&gt;Question: Have you talked with Harry Kaplanian and/or Martin Tran about this scenario yet?&lt;/p&gt;

&lt;p&gt;I would add the academic use case of a journal run volumes 1- volume 50. There might be 4 copies, 3 holdings, and only 50 item records.&lt;/p&gt;

&lt;p&gt;Single Instance Record&lt;br/&gt;
3 Holdings Records&lt;br/&gt;
50 Item Records with this scenario.&lt;/p&gt;

&lt;p&gt;Holdings Record 1: Main Library, Copy 1, No Item Records&lt;br/&gt;
Holdings Record 1: Main Library, Copy 2, No Item Records&lt;br/&gt;
Holdings Record 2: Law Library, Copy 1, No Item Records&lt;br/&gt;
Holdings Record 3: Remote Storage, Copy 1, Each of the 50 volumes has a single Item Record with Barcode&lt;/p&gt;

&lt;p&gt;In this scenario, the user may not care which copy she receives in response to her request. hold or page. However, she will care about which specific volumes she receives. &lt;/p&gt;

&lt;p&gt;In the existing/older RTAC+ functionality availability for patron empowerment, all of the requests/holds/pages were title level and there was a free text field added to the user display painted on the EDS screen. This free text field allowed the patron to request specific volume(s).&lt;/p&gt;

&lt;p&gt;You may already know this, but just to confirm. The 2 holdings &amp;amp; 3 copies without any item records have a summary holding statement with MARC 21 data like this in the source record storage:&lt;/p&gt;

&lt;p&gt;866	31$80$a1-86 (1941-1987)$xbound in 2 v. per year$zSome issues missing&lt;/p&gt;

&lt;p&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;Added info worth confirming: The 866 field replaces both 863 fields. The library records actual detailed holdings in the 863 fields, but the display shows summary holdings with non-public and public notes.&amp;#93;&lt;/span&gt;&lt;/p&gt;

&lt;p&gt;Again, I&apos;d check in with &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5ecdb772036612ff61cf1&quot; class=&quot;user-hover&quot; rel=&quot;5af5ecdb772036612ff61cf1&quot; data-account-id=&quot;5af5ecdb772036612ff61cf1&quot; accountid=&quot;5af5ecdb772036612ff61cf1&quot; rel=&quot;noreferrer&quot;&gt;Hkaplanian&lt;/a&gt;, &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A8629b273-56f1-466d-b7c7-5cbac0c3379b&quot; class=&quot;user-hover&quot; rel=&quot;557058:8629b273-56f1-466d-b7c7-5cbac0c3379b&quot; data-account-id=&quot;557058:8629b273-56f1-466d-b7c7-5cbac0c3379b&quot; accountid=&quot;557058:8629b273-56f1-466d-b7c7-5cbac0c3379b&quot; rel=&quot;noreferrer&quot;&gt;Magda Zacharska&lt;/a&gt; and/or &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ab45447b0-4142-447e-9ac7-b2b97eeb90bc&quot; class=&quot;user-hover&quot; rel=&quot;557058:b45447b0-4142-447e-9ac7-b2b97eeb90bc&quot; data-account-id=&quot;557058:b45447b0-4142-447e-9ac7-b2b97eeb90bc&quot; accountid=&quot;557058:b45447b0-4142-447e-9ac7-b2b97eeb90bc&quot; rel=&quot;noreferrer&quot;&gt;Martin Tran&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Hope this is somewhat helpful.&lt;/p&gt;

&lt;p&gt;Marc&lt;/p&gt;</comment>
                                                            <comment id="13095" author="557058:5ceb2fe3-7fa0-4074-babb-a5941cdcf312" created="Thu, 22 Aug 2019 16:32:31 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5ecdb772036612ff61cf1&quot; class=&quot;user-hover&quot; rel=&quot;5af5ecdb772036612ff61cf1&quot; data-account-id=&quot;5af5ecdb772036612ff61cf1&quot; accountid=&quot;5af5ecdb772036612ff61cf1&quot; rel=&quot;noreferrer&quot;&gt;Hkaplanian&lt;/a&gt; I started in the Consortia SIG.  They suggested I look at this UXPROD to see if it was the solution to this issue.  I have put this in as a user story over there.  I&apos;m clarifying that this does not fix the problem, so I can continue to press the issue in the Consortia SIG.&lt;/p&gt;</comment>
                                                            <comment id="13097" author="5af5ecdb772036612ff61cf1" created="Thu, 22 Aug 2019 16:56:34 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A5ceb2fe3-7fa0-4074-babb-a5941cdcf312&quot; class=&quot;user-hover&quot; rel=&quot;557058:5ceb2fe3-7fa0-4074-babb-a5941cdcf312&quot; data-account-id=&quot;557058:5ceb2fe3-7fa0-4074-babb-a5941cdcf312&quot; accountid=&quot;557058:5ceb2fe3-7fa0-4074-babb-a5941cdcf312&quot; rel=&quot;noreferrer&quot;&gt;Lloyd Chittenden&lt;/a&gt; - Got it.  Make sense.  Let me know if I can help.&lt;/p&gt;

</comment>
                                                            <comment id="13099" author="557058:5ceb2fe3-7fa0-4074-babb-a5941cdcf312" created="Thu, 22 Aug 2019 18:52:02 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af9cc2a5f0d5b06c28aa731&quot; class=&quot;user-hover&quot; rel=&quot;5af9cc2a5f0d5b06c28aa731&quot; data-account-id=&quot;5af9cc2a5f0d5b06c28aa731&quot; accountid=&quot;5af9cc2a5f0d5b06c28aa731&quot; rel=&quot;noreferrer&quot;&gt;Marc Keepper&lt;/a&gt; It sounds like you are talking about a multi-tenant consortium.  This would indeed be very messy in that scenario, however our consortium is set up with a single server where everyone is sharing the same bib records.  If we had holdings records we would share those as well, primarily because it would facilitate exactly this sort of resource sharing.  &lt;/p&gt;

&lt;p&gt;So we would be talking about a single MARC record for the TV series, with a single holdings record for each season.  Then every library would have it&apos;s copies of each season attached to that single holdings record.  Then it is not complicated.  I&apos;m suggesting that the requests should exist on the holdings record rather than the title level or the item level.  If you had holdings level requests, then you would not need title level requests at all because if there is only one holdings record, then they are the same thing.  And item level requests could be added, but it would be a lower priority because the need to request a particular copy of a volume is rare.&lt;/p&gt;

&lt;p&gt;I will continue to pursue this in the Consortia SIG, but the people developing this function here should know that this is wanted.  I don&apos;t know that it would be so much harder to start out with a system of requests at the holdings level rather than title level.  If that&apos;s where we want to be in the end, it might be easier to set it up that way now rather than build title level requesting and have to add holdings level requesting later.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5ecdb772036612ff61cf1&quot; class=&quot;user-hover&quot; rel=&quot;5af5ecdb772036612ff61cf1&quot; data-account-id=&quot;5af5ecdb772036612ff61cf1&quot; accountid=&quot;5af5ecdb772036612ff61cf1&quot; rel=&quot;noreferrer&quot;&gt;Hkaplanian&lt;/a&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A8629b273-56f1-466d-b7c7-5cbac0c3379b&quot; class=&quot;user-hover&quot; rel=&quot;557058:8629b273-56f1-466d-b7c7-5cbac0c3379b&quot; data-account-id=&quot;557058:8629b273-56f1-466d-b7c7-5cbac0c3379b&quot; accountid=&quot;557058:8629b273-56f1-466d-b7c7-5cbac0c3379b&quot; rel=&quot;noreferrer&quot;&gt;Magda Zacharska&lt;/a&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ab45447b0-4142-447e-9ac7-b2b97eeb90bc&quot; class=&quot;user-hover&quot; rel=&quot;557058:b45447b0-4142-447e-9ac7-b2b97eeb90bc&quot; data-account-id=&quot;557058:b45447b0-4142-447e-9ac7-b2b97eeb90bc&quot; accountid=&quot;557058:b45447b0-4142-447e-9ac7-b2b97eeb90bc&quot; rel=&quot;noreferrer&quot;&gt;Martin Tran&lt;/a&gt;&lt;/p&gt;</comment>
                                                            <comment id="13102" author="557058:8629b273-56f1-466d-b7c7-5cbac0c3379b" created="Fri, 23 Aug 2019 13:13:02 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A5ceb2fe3-7fa0-4074-babb-a5941cdcf312&quot; class=&quot;user-hover&quot; rel=&quot;557058:5ceb2fe3-7fa0-4074-babb-a5941cdcf312&quot; data-account-id=&quot;557058:5ceb2fe3-7fa0-4074-babb-a5941cdcf312&quot; accountid=&quot;557058:5ceb2fe3-7fa0-4074-babb-a5941cdcf312&quot; rel=&quot;noreferrer&quot;&gt;Lloyd Chittenden&lt;/a&gt; The functionality you are concerned about is outside the scope of this feature (basic title level request) but we have solution that could handle the situation that on one occasion a patron doesn&apos;t care which copy their will get (identical copies for the same bib rec) and on the other (like different seasons of the TV series).   This is being handled by the discovery service that is integrated with FOLIO through edge modules.  We have it working with EDS integration.  Here is an example of the modal that is displayed to the patron when creating a request for multi-volume publication: &lt;br/&gt;
&lt;span class=&quot;image-wrap&quot; style=&quot;&quot;&gt;&lt;a id=&quot;10507_thumb&quot; href=&quot;/rest/api/3/attachment/content/10507&quot; title=&quot;screenshot-1.png&quot; file-preview-type=&quot;image&quot; file-preview-id=&quot;10507&quot; file-preview-title=&quot;screenshot-1.png&quot;&gt;&lt;jira-attachment-thumbnail url=&quot;https://folio-org.atlassian.net/rest/api/3/attachment/thumbnail/10507?default=false&quot; jira-url=&quot;https://folio-org.atlassian.net/rest/api/3/attachment/thumbnail/10507&quot; filename=&quot;screenshot-1.png&quot;&gt;&lt;img src=&quot;https://folio-org.atlassian.net/rest/api/3/attachment/thumbnail/10507&quot; data-attachment-name=&quot;screenshot-1.png&quot; data-attachment-type=&quot;thumbnail&quot; data-media-services-id=&quot;23afcf98-596d-4be3-96c5-d6e651005162&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;/p&gt;
</comment>
                                                            <comment id="13106" author="557058:5ceb2fe3-7fa0-4074-babb-a5941cdcf312" created="Fri, 23 Aug 2019 15:50:50 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A8629b273-56f1-466d-b7c7-5cbac0c3379b&quot; class=&quot;user-hover&quot; rel=&quot;557058:8629b273-56f1-466d-b7c7-5cbac0c3379b&quot; data-account-id=&quot;557058:8629b273-56f1-466d-b7c7-5cbac0c3379b&quot; accountid=&quot;557058:8629b273-56f1-466d-b7c7-5cbac0c3379b&quot; rel=&quot;noreferrer&quot;&gt;Magda Zacharska&lt;/a&gt;Thank you.  That is very interesting.  Where do I find that part of the project on Jira?  I&apos;m new to this and it is not so easy to navigate.&lt;/p&gt;</comment>
                                                            <comment id="13109" author="557058:8629b273-56f1-466d-b7c7-5cbac0c3379b" created="Sat, 24 Aug 2019 07:04:26 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A5ceb2fe3-7fa0-4074-babb-a5941cdcf312&quot; class=&quot;user-hover&quot; rel=&quot;557058:5ceb2fe3-7fa0-4074-babb-a5941cdcf312&quot; data-account-id=&quot;557058:5ceb2fe3-7fa0-4074-babb-a5941cdcf312&quot; accountid=&quot;557058:5ceb2fe3-7fa0-4074-babb-a5941cdcf312&quot; rel=&quot;noreferrer&quot;&gt;Lloyd Chittenden&lt;/a&gt;  You might want to take a look at &lt;a href=&quot;https://github.com/folio-org/edge-rtac&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/edge-rtac&lt;/a&gt;, &lt;a href=&quot;https://github.com/folio-org/edge-patron&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/edge-patron&lt;/a&gt;, &lt;a href=&quot;https://github.com/folio-org/mod-patron&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/mod-patron&lt;/a&gt; and &lt;a href=&quot;https://github.com/folio-org/mod-rtac&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/mod-rtac&lt;/a&gt;.  If you have technical questions &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=70121%3Ae70f578f-dc5a-4a30-8836-fc2418025d21&quot; class=&quot;user-hover&quot; rel=&quot;70121:e70f578f-dc5a-4a30-8836-fc2418025d21&quot; data-account-id=&quot;70121:e70f578f-dc5a-4a30-8836-fc2418025d21&quot; accountid=&quot;70121:e70f578f-dc5a-4a30-8836-fc2418025d21&quot; rel=&quot;noreferrer&quot;&gt;Matt Reno&lt;/a&gt; or &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ab45447b0-4142-447e-9ac7-b2b97eeb90bc&quot; class=&quot;user-hover&quot; rel=&quot;557058:b45447b0-4142-447e-9ac7-b2b97eeb90bc&quot; data-account-id=&quot;557058:b45447b0-4142-447e-9ac7-b2b97eeb90bc&quot; accountid=&quot;557058:b45447b0-4142-447e-9ac7-b2b97eeb90bc&quot; rel=&quot;noreferrer&quot;&gt;Martin Tran&lt;/a&gt; would be the best to contact.  If you have questions regarding the functional side - please let me know.&lt;/p&gt;</comment>
                                                            <comment id="13111" author="557058:5ceb2fe3-7fa0-4074-babb-a5941cdcf312" created="Mon, 26 Aug 2019 14:52:36 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A8629b273-56f1-466d-b7c7-5cbac0c3379b&quot; class=&quot;user-hover&quot; rel=&quot;557058:8629b273-56f1-466d-b7c7-5cbac0c3379b&quot; data-account-id=&quot;557058:8629b273-56f1-466d-b7c7-5cbac0c3379b&quot; accountid=&quot;557058:8629b273-56f1-466d-b7c7-5cbac0c3379b&quot; rel=&quot;noreferrer&quot;&gt;Magda Zacharska&lt;/a&gt; Is there a sandbox version of this functionality that I could try out?&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10008">
                    <name>Defines</name>
                                                                <inwardlinks description="is defined by ">
                                        <issuelink>
            <issuekey id="47865">CIRC-271</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="47738">CIRC-245</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="47919">CIRC-264</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="47921">CIRC-265</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="47920">CIRC-267</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="75023">MODPATRON-2</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="75026">MODPATRON-5</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="75082">MODPATRON-8</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="75090">MODPATRON-12</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="10816">UXPROD-1217</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="11191">UXPROD-1796</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="11143">UXPROD-1982</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="49107">CIRC-1164</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="49218">CIRC-1212</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="11223">UXPROD-2198</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="11378">UXPROD-2311</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="11086">UXPROD-1809</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="11087">UXPROD-1810</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="10252">UXPROD-351</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="10506" name="SimpleTLR.pdf" size="104487" author="557058:8629b273-56f1-466d-b7c7-5cbac0c3379b" created="Fri, 15 Nov 2019 22:09:45 +0000"/>
                            <attachment id="10507" name="screenshot-1.png" size="33107" author="557058:8629b273-56f1-466d-b7c7-5cbac0c3379b" created="Fri, 23 Aug 2019 13:04:47 +0000"/>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10053" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Back End Estimate</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10122"><![CDATA[Large < 10 days]]></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)">Requests</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10056" key="com.atlassian.jira.plugin.system.customfieldtypes:textarea">
                        <customfieldname>Estimation Notes and Assumptions</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>I am assuming a solution where the title (instance)-level request is immediately (at creation time) converted to a regular item-level request,&lt;br/&gt;
based on some simple logic, like take the first available item and if nothing is available the first one where the due date is soonest. This could be build as a new endpoint in mod-circulation or directly in mod-patron, if the usage is limited to discovery services.</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10019" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|hzytfr:</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="10203"><![CDATA[R1]]></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="10212"><![CDATA[R5]]></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_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_10078" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: Lehigh (MVP Summer 2020)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10262"><![CDATA[R5]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10079" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: Leipzig (Full TBD)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10263"><![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="10315"><![CDATA[R2]]></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="10249"><![CDATA[R2]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10020" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10024" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>[CHART] Date of First Response</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Wed, 29 Aug 2018 15:11:39 +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>