<!-- 
RSS generated by JIRA (1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d) at Fri Feb 09 00:12:20 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-1025] Ability to configure an ACQ specific list of Material Types used in Orders</title>
                <link>https://folio-org.atlassian.net/browse/UXPROD-1025</link>
                <project id="10000" key="UXPROD">UX Product</project>
                    <description>&lt;p&gt;Purpose: Libraries need the ability to customize their list of material types specific to orders and order lines.&lt;/p&gt;

&lt;p&gt;High Level Requirements:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Allow the user to add, edit and delete values from the list of material types in the Orders module settings&lt;/li&gt;
	&lt;li&gt;You should not be able to remove a value that is in use&lt;/li&gt;
&lt;/ul&gt;


</description>
                <environment></environment>
        <key id="10691">UXPROD-1025</key>
            <summary>Ability to configure an ACQ specific list of Material Types used in Orders</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="10311">UXPROD-1141</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="10000">Won&apos;t Do</resolution>
                                                        <assignee accountid="557058:2f7b6349-450b-419a-ba54-c181f51383ad">Dennis Bridges</assignee>
                                                                <reporter accountid="557058:2f7b6349-450b-419a-ba54-c181f51383ad">Dennis Bridges</reporter>
                                    <labels>
                            <label>Q2fromQ1</label>
                            <label>Q3fromQ2</label>
                            <label>acquisitions</label>
                            <label>orders</label>
                    </labels>
                <created>Thu, 9 Aug 2018 16:37:20 +0000</created>
                <updated>Wed, 16 Sep 2020 21:05:47 +0000</updated>
                            <resolved>Wed, 22 Jan 2020 22:01:44 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>5</watches>
                                                                <comments>
                                                            <comment id="12780" author="5af5ed55244bc90a106063c7" created="Wed, 12 Sep 2018 14:49:31 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A2f7b6349-450b-419a-ba54-c181f51383ad&quot; class=&quot;user-hover&quot; rel=&quot;557058:2f7b6349-450b-419a-ba54-c181f51383ad&quot; data-account-id=&quot;557058:2f7b6349-450b-419a-ba54-c181f51383ad&quot; accountid=&quot;557058:2f7b6349-450b-419a-ba54-c181f51383ad&quot; rel=&quot;noreferrer&quot;&gt;Dennis Bridges&lt;/a&gt;.  I noticed this feature didn&apos;t have an epic so I assigned Acquisitions.  Thx&lt;/p&gt;</comment>
                                                            <comment id="12782" author="557058:2f7b6349-450b-419a-ba54-c181f51383ad" created="Wed, 12 Sep 2018 16:28:39 +0000"  >&lt;p&gt;Thanks Cate!&lt;/p&gt;</comment>
                                                            <comment id="12785" author="5c7405f424a84d1307801d06" created="Mon, 6 May 2019 16:23:26 +0000"  >&lt;p&gt;Are the material types being discussed here tied to the material types being used in circulation rules/functions or are they tied to the formats being used in cataloging?&lt;/p&gt;

&lt;p&gt;It&apos;s already been determined that the circ material type must be locally configurable.&lt;br/&gt;
I believe that the cataloging version (format) is based on the &lt;a href=&quot;http://www.loc.gov/standards/valuelist/rdacarrier.html&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;RDA carrier codes&lt;/a&gt;&lt;/p&gt;

&lt;p&gt; I&apos;d think that the circ version is a better match and that there needs to be coordination between Acquisitions and Circulation functions.  Otherwise we&apos;ll end up with a disconnected sets of similar data.&lt;/p&gt;

&lt;p&gt;Happy to be of help on this if I can.&lt;/p&gt;</comment>
                                                            <comment id="12788" author="70121:a31d4ba3-9798-45a5-86bc-fc2d931698b8" created="Tue, 5 Nov 2019 17:53:44 +0000"  >&lt;p&gt;SHould be coordinated with Inventory/item material type&lt;/p&gt;</comment>
                                                            <comment id="12790" author="5c7405f424a84d1307801d06" created="Tue, 5 Nov 2019 19:19:55 +0000"  >&lt;p&gt;Agreed Steven!  I actually think this should be assigned to RA rather than Acq.  Material type exists to be a component of the circulation rules.&lt;/p&gt;</comment>
                                                            <comment id="12792" author="5c48911b54e1e6466b11f38c" created="Tue, 5 Nov 2019 19:23:04 +0000"  >&lt;p&gt;I&apos;d like to understand more as to why there would be separate lists for acq and cataloging. I know in Aleph there are separate lists, but I don&apos;t understand why.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5c7405f424a84d1307801d06&quot; class=&quot;user-hover&quot; rel=&quot;5c7405f424a84d1307801d06&quot; data-account-id=&quot;5c7405f424a84d1307801d06&quot; accountid=&quot;5c7405f424a84d1307801d06&quot; rel=&quot;noreferrer&quot;&gt;Andrea Loigman&lt;/a&gt; isn&apos;t material type a cataloging thing though? It exists in Aleph right now. You are correct that it&apos;s part of circulation rules.&lt;/p&gt;</comment>
                                                            <comment id="12795" author="557058:2f7b6349-450b-419a-ba54-c181f51383ad" created="Wed, 6 Nov 2019 17:07:53 +0000"  >&lt;p&gt;This came about after discussion in the RM SIG. Essentially it was proposed that reporting requirements and categorization of spending may differ from the perspective of orders. Thus, it would be valuable to have a unique list of material types in the orders app that could describe the general material type of the order. Currently the order material types are pulled from the inventory item material types controlled vocabulary that can be edited in inventory settings.&lt;/p&gt;</comment>
                                                            <comment id="12797" author="5c48911b54e1e6466b11f38c" created="Wed, 6 Nov 2019 17:58:58 +0000"  >&lt;p&gt;I guess I&apos;m thinking, from a definition stand point, why would an item&apos;s material type change in an order versus when it&apos;s catalogued. It&apos;s not like it&apos;s a different thing you&apos;re ordering.&lt;/p&gt;

&lt;p&gt;If it&apos;s categorization of spending, maybe that&apos;s a field that&apos;s not called material type, but something else.&lt;/p&gt;

&lt;p&gt;I just know that when non-acquisitions and non-catalogers were looking at this here at Duke in Aleph, our current ILS, (me and &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5c48911acc3a1d3d8a2bbdf9&quot; class=&quot;user-hover&quot; rel=&quot;5c48911acc3a1d3d8a2bbdf9&quot; data-account-id=&quot;5c48911acc3a1d3d8a2bbdf9&quot; accountid=&quot;5c48911acc3a1d3d8a2bbdf9&quot; rel=&quot;noreferrer&quot;&gt;Julie Brannon&lt;/a&gt;) we were very confused about two lists that were labeled as material types but had very different values. I&apos;d advocate for not replicating that kind of structure in FOLIO unless it is really, really necessary.&lt;/p&gt;</comment>
                                                            <comment id="12802" author="5c7405f424a84d1307801d06" created="Wed, 6 Nov 2019 19:09:26 +0000"  >&lt;p&gt;There was joint RA/MM small group a while back,  MM felt that they needed to use the RDA carrier types and RA found that list too restrictive (e.g. is a videodisc a DVD, Blu-ray or laserdisc).  So two types were created a format type (restricted to RDA) and a locally configurable material type that would allow RA to control circulation and allow libraries to create rules for all of the odd things they circulate (bicycles, backpacks, umbrellas and various types of tech were all on that list).&lt;/p&gt;

&lt;p&gt;I&apos;m going to guess that RM will need to use both material and format.  The format list is at &lt;a href=&quot;http://www.loc.gov/standards/valuelist/rdacarrier.html&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;http://www.loc.gov/standards/valuelist/rdacarrier.html&lt;/a&gt;.  The material type list will need to be generated and agreed on at each institution and should probably start in Access Services.&lt;/p&gt;

&lt;p&gt;If you&apos;re seeing to different lists of material types, my guess is that something is mislabeled.&lt;/p&gt;

&lt;p&gt;Does that make sense?&lt;/p&gt;</comment>
                                                            <comment id="12804" author="5c48911b54e1e6466b11f38c" created="Wed, 6 Nov 2019 19:13:48 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5c7405f424a84d1307801d06&quot; class=&quot;user-hover&quot; rel=&quot;5c7405f424a84d1307801d06&quot; data-account-id=&quot;5c7405f424a84d1307801d06&quot; accountid=&quot;5c7405f424a84d1307801d06&quot; rel=&quot;noreferrer&quot;&gt;Andrea Loigman&lt;/a&gt; I was referring to the fact that there are separate material type lists in Aleph, one for Acquisitions and one for Cataloging. Sorry, I&apos;ll edit to make that clear.&lt;/p&gt;

&lt;p&gt;So are you saying that you don&apos;t envision that cataloging folks would care about material type at all on the item record, because they have the format type? It&apos;s not derived from any part of a MARC record?&lt;/p&gt;</comment>
                                                            <comment id="12807" author="5c7405f424a84d1307801d06" created="Wed, 6 Nov 2019 19:30:56 +0000"  >&lt;p&gt;That was certainly the impression that I took away from the small group.  MM or RM might assign the material type as part of their processing though, so they&apos;d need to be aware of/familiar with them.&lt;/p&gt;

&lt;p&gt;BTW - there might be times that a material type would change, but the format type never would (unless the RDA carrier list changes).&lt;/p&gt;</comment>
                                                            <comment id="12810" author="5c48911b54e1e6466b11f38c" created="Wed, 6 Nov 2019 19:32:10 +0000"  >&lt;p&gt;You mean like when something goes to binding? I&apos;m not sure I understand that.&lt;/p&gt;</comment>
                                                            <comment id="12811" author="5c7405f424a84d1307801d06" created="Fri, 8 Nov 2019 14:01:03 +0000"  >&lt;p&gt;More like when something goes on or off of reserve, need to change the way loan work for various types of equipment or technology or start collecting additional types of media.&lt;/p&gt;</comment>
                                                            <comment id="12814" author="5c48911b54e1e6466b11f38c" created="Fri, 8 Nov 2019 14:22:53 +0000"  >&lt;p&gt;Right - but in that scenario it could be that the loan type is course reserves, not the material type. That would let us write policies for reserves that are equally applied regardless of whether it&apos;s books, CDs, etc.&lt;/p&gt;</comment>
                                                            <comment id="12816" author="5c7405f424a84d1307801d06" created="Mon, 6 Jan 2020 22:27:06 +0000"  >&lt;p&gt;If RM has the ability to create new material types, they will end up creating items that have no circ rule or at the least wouldn&apos;t fall under the expected circ rule.&lt;br/&gt;
I think that there needs to be a VERY serious conversation about permissions for this and/or that there should *not *be a way to create  new material types in orders at all.&lt;/p&gt;</comment>
                                                            <comment id="12819" author="557058:2f7b6349-450b-419a-ba54-c181f51383ad" created="Tue, 7 Jan 2020 17:42:27 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5c7405f424a84d1307801d06&quot; class=&quot;user-hover&quot; rel=&quot;5c7405f424a84d1307801d06&quot; data-account-id=&quot;5c7405f424a84d1307801d06&quot; accountid=&quot;5c7405f424a84d1307801d06&quot; rel=&quot;noreferrer&quot;&gt;Andrea Loigman&lt;/a&gt; currently material types are pulled from the list of material types that users can control in inventory settings. If you see issues with adjusting that we could make some time for discussion in the next RM SIG meeting. This would be a challenge for a few reasons, but it is also currently a relatively high priority for the group. Do you think perhaps that is a misrepresentation?&lt;/p&gt;</comment>
                                                            <comment id="12822" author="5c48911b54e1e6466b11f38c" created="Tue, 7 Jan 2020 17:47:30 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A2f7b6349-450b-419a-ba54-c181f51383ad&quot; class=&quot;user-hover&quot; rel=&quot;557058:2f7b6349-450b-419a-ba54-c181f51383ad&quot; data-account-id=&quot;557058:2f7b6349-450b-419a-ba54-c181f51383ad&quot; accountid=&quot;557058:2f7b6349-450b-419a-ba54-c181f51383ad&quot; rel=&quot;noreferrer&quot;&gt;Dennis Bridges&lt;/a&gt; I think it depends on whether the material type used in Orders is being pushed to inventory when the item is created on the order. If that&apos;s the case, it needs to be one central list since the circulation rules will use the material type on the item. Whether that central list is maintained in orders or inventory, I don&apos;t know that that part matters as much. &lt;/p&gt;

&lt;p&gt;If the material type is not being pushed then to the item record, I don&apos;t know that it matters as much. The item record is what the circ rules will read. If it&apos;s not being pushed, I&apos;d advocate for it being labeled slightly differently just to make sure there&apos;s an understanding as to what the orders list is versus what the inventory list is.&lt;/p&gt;
</comment>
                                                            <comment id="12825" author="5c48911b54e1e6466b11f38c" created="Tue, 7 Jan 2020 17:48:35 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A2f7b6349-450b-419a-ba54-c181f51383ad&quot; class=&quot;user-hover&quot; rel=&quot;557058:2f7b6349-450b-419a-ba54-c181f51383ad&quot; data-account-id=&quot;557058:2f7b6349-450b-419a-ba54-c181f51383ad&quot; accountid=&quot;557058:2f7b6349-450b-419a-ba54-c181f51383ad&quot; rel=&quot;noreferrer&quot;&gt;Dennis Bridges&lt;/a&gt; I think it would also be helpful to articulate the reason separate lists are needed. I know that our current ILS at Duke has separate lists for material type for orders and cataloging, but it&apos;s never been clear to me as a non-tech services person &lt;b&gt;why&lt;/b&gt; two lists are needed.&lt;/p&gt;</comment>
                                                            <comment id="12828" author="5c7405f424a84d1307801d06" created="Tue, 7 Jan 2020 19:25:50 +0000"  >&lt;p&gt;If there was a way to create an agreement between acq and circ that let us use a singe list it would certainly save everyone a lot of work, but I can&apos;t begin to imagine how we&apos;d make it work,  especially in a large institution or consortia.  There&apos;s just isn&apos;t a good enough communication model at most institutions.&lt;/p&gt;

&lt;p&gt;I guess that I just don&apos;t understand why acquisitions needs a material type when format also exists?   Having a third list of Material (RA), Formats (MM) and something else (RM) seems like a lot of repetition and potential for conflict.  I must be missing something since it seems to me that acq should be able to use the same regulated list of formats as cataloging.&lt;/p&gt;


</comment>
                                                            <comment id="12831" author="557058:2f7b6349-450b-419a-ba54-c181f51383ad" created="Tue, 7 Jan 2020 19:44:09 +0000"  >&lt;p&gt;Thanks &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 &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5c7405f424a84d1307801d06&quot; class=&quot;user-hover&quot; rel=&quot;5c7405f424a84d1307801d06&quot; data-account-id=&quot;5c7405f424a84d1307801d06&quot; accountid=&quot;5c7405f424a84d1307801d06&quot; rel=&quot;noreferrer&quot;&gt;Andrea Loigman&lt;/a&gt; The good news is that we are currently pulling the list of material types from inventory &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; and for that exact reason. We use material type to create item records on behalf of the user/order and it is a required field in inventory. So currently one list that is maintained in inventory settings. This feature would cover having a separate list that is not shared with inventory. &lt;/p&gt;

&lt;p&gt;FYI I have made some updates to the description in an effort to clarify what this aims to accomplish. I think we failed to capture here that a decision was made to use material types from inventory in the short term.&lt;/p&gt;</comment>
                                                            <comment id="12833" author="557058:2f7b6349-450b-419a-ba54-c181f51383ad" created="Wed, 22 Jan 2020 22:01:28 +0000"  >&lt;p&gt;Summary from discussion: After discussing this issue at Wolfcon. In the following session &lt;a href=&quot;https://wolfcon2020a.sched.com/event/YzF4/material-type-needs-from-orders-to-shelf&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://wolfcon2020a.sched.com/event/YzF4/material-type-needs-from-orders-to-shelf&lt;/a&gt; (Material type needs from orders to shelf). It was decided by the group that having a second list would not be necessary as this is already required by inventory to create an item record. The material type in the resulting item record could be changed post order and this would not be reflected in the order record. &lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10001">
                    <name>Cloners</name>
                                                                <inwardlinks description="is cloned by">
                                        <issuelink>
            <issuekey id="13155">UXPROD-2455</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="10311">UXPROD-1141</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10053" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Back End Estimate</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10120"><![CDATA[Small < 3 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="10185"><![CDATA[Thunderjet]]></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)">Create, close, cancel, Purchase Orders</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10050" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Front End Estimate</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10096"><![CDATA[Small < 3 days]]></customfieldvalue>

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

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10063" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>PO Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>61.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_10019" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|hzyrqv:</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="10206"><![CDATA[R4]]></customfieldvalue>

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

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10069" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: Cornell (Full Sum 2021)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="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="10241"><![CDATA[R4]]></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="10260"><![CDATA[R3]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10079" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: Leipzig (Full TBD)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10264"><![CDATA[R2]]></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="10327"><![CDATA[R4]]></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, 12 Sep 2018 14:49:31 +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>