<!-- 
RSS generated by JIRA (1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d) at Fri Feb 09 00:22:04 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-2211] Custom Fields in Inventory</title>
                <link>https://folio-org.atlassian.net/browse/UXPROD-2211</link>
                <project id="10000" key="UXPROD">UX Product</project>
                    <description>&lt;p&gt;Ability to add custom fields to records in Inventory (Instance, Holdings, Item). Custom fields has been developed to the Users app. This is highly sought after by the SMEs and early implementer libraries. &lt;/p&gt;

&lt;h4&gt;&lt;a name=&quot;Inventoryrequirescustomfieldstosupport&quot;&gt;&lt;/a&gt;Inventory requires custom fields to support &lt;/h4&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;Data Migration: Given each ILS provider has unique fields it is critical we support custom fields to ensure that all valuable data is migrated to Folio.&lt;/li&gt;
	&lt;li&gt;Affiliation/Statistical groupings&lt;/li&gt;
	&lt;li&gt;Workflow&lt;/li&gt;
	&lt;li&gt;Interaction with locally used 3rd party systems&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Slidedeck: &lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Custum fields tech solution: &lt;a href=&quot;https://docs.google.com/presentation/d/16rHWdIy5-BbREcTlMH2omV2CMtbfIUvjN3KGkxg-Zko/edit#slide=id.p&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://docs.google.com/presentation/d/16rHWdIy5-BbREcTlMH2omV2CMtbfIUvjN3KGkxg-Zko/edit#slide=id.p&lt;/a&gt;&lt;/li&gt;
	&lt;li&gt;Draft Requirements: &lt;a href=&quot;https://docs.google.com/presentation/d/1zXvDSw-zJ36dKWv1C-W3-x8yOmKNu01c3LV0prJh1F8/edit#slide=id.p&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://docs.google.com/presentation/d/1zXvDSw-zJ36dKWv1C-W3-x8yOmKNu01c3LV0prJh1F8/edit#slide=id.p&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
                <environment></environment>
        <key id="13173">UXPROD-2211</key>
            <summary>Custom Fields in Inventory</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="13688">UXPROD-396</parent>
                                    <priority id="10002" iconUrl="https://dev.folio.org/assets/jira-priority/jira-p3.svg">P3</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="5af5ecdd29e02a573e5f1c10">Ryan Taylor</assignee>
                                                                <reporter accountid="557058:f80403de-e149-421e-8750-af45c853402f">Charlotte Whitt</reporter>
                                    <labels>
                            <label>delegate_candidate</label>
                            <label>loc</label>
                            <label>round_iv</label>
                    </labels>
                <created>Wed, 18 Dec 2019 15:28:13 +0000</created>
                <updated>Thu, 28 Dec 2023 19:42:45 +0000</updated>
                                                            <fixVersion>TBD</fixVersion>
                                        <due></due>
                            <votes>0</votes>
                                    <watches>15</watches>
                                                                <comments>
                                                            <comment id="14740" author="557058:a957226f-df85-4fc8-97f4-8b27a26029ed" created="Wed, 17 Jun 2020 21:15:07 +0000"  >&lt;p&gt;Chicago comment from Round IV Outliers spreadsheet: Inventory instance notes are not available for editing if there is an underlying MARC record. We are trying to get away from managing data in MARC 9XX fields.Currently we have good flexibility in holdings and items.We de-prioritized the tags and notes apps because we thought we could add custom fields at the instance level, but if there is underlying MARC we are locked into maintaining that data in the MARC record, not in the instance or in even the inventory app.This means instances with underlying MARC will need to be treated differently than instances without underlying MARC, which greatly complicates workflows and procedures.	-Tod Olson&lt;/p&gt;</comment>
                                                            <comment id="14743" author="5c48911d87530c43d3a188ac" created="Tue, 15 Sep 2020 20:59:44 +0000"  >&lt;p&gt;Reason Duke has determined this is a go-live/R1 for us is because we need the &apos;previous/former&apos; call number (call number 2) to be searchable in inventory and a custom field may be the only feasible way to support this requirement. &lt;/p&gt;</comment>
                                                            <comment id="14746" author="63e2a2771b13d42998e4e706" created="Fri, 18 Sep 2020 15:50:14 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Af80403de-e149-421e-8750-af45c853402f&quot; class=&quot;user-hover&quot; rel=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; data-account-id=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; accountid=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; rel=&quot;noreferrer&quot;&gt;Charlotte Whitt&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5c48911d87530c43d3a188ac&quot; class=&quot;user-hover&quot; rel=&quot;5c48911d87530c43d3a188ac&quot; data-account-id=&quot;5c48911d87530c43d3a188ac&quot; accountid=&quot;5c48911d87530c43d3a188ac&quot; rel=&quot;noreferrer&quot;&gt;jackie.gottlieb@duke.edu&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5ed55244bc90a106063c7&quot; class=&quot;user-hover&quot; rel=&quot;5af5ed55244bc90a106063c7&quot; data-account-id=&quot;5af5ed55244bc90a106063c7&quot; accountid=&quot;5af5ed55244bc90a106063c7&quot; rel=&quot;noreferrer&quot;&gt;Cate Boerema&lt;/a&gt;&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;Reason Duke has determined this is a go-live/R1 for us is because we need the &apos;previous/former&apos; call number (call number 2) to be searchable in inventory and a custom field may be the only feasible way to support this requirement.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Is &lt;tt&gt;previous/former call number&lt;/tt&gt; intended to be a custom field? And does that mean that folks are expecting custom fields to be searchable?&lt;/p&gt;</comment>
                                                            <comment id="14748" author="5af5e627525ba96b58654f12" created="Fri, 18 Sep 2020 16:30:34 +0000"  >&lt;p&gt;Maybe a stupid question from me - in lieu of a custom field, why couldn&apos;t there be a call number type for previous call number, and the previous call number goes there? I realize that call number/call number type is not repeatable on the holdings or item, but it is repeatable (classification) on the instance.&lt;/p&gt;</comment>
                                                            <comment id="14751" author="5c48911d87530c43d3a188ac" created="Fri, 18 Sep 2020 17:23:16 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=63e2a2771b13d42998e4e706&quot; class=&quot;user-hover&quot; rel=&quot;63e2a2771b13d42998e4e706&quot; data-account-id=&quot;63e2a2771b13d42998e4e706&quot; accountid=&quot;63e2a2771b13d42998e4e706&quot; rel=&quot;noreferrer&quot;&gt;Marc Johnson&lt;/a&gt;&lt;br/&gt;
&quot;Is previous/former call number intended to be a custom field? And does that mean that folks are expecting custom fields to be searchable?&quot;&lt;br/&gt;
We are not expecting FOLIO to have additional call number fields and so have assumed we will need to support this with a custom field. Yes, we expect custom fields to be searchable. &lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5e627525ba96b58654f12&quot; class=&quot;user-hover&quot; rel=&quot;5af5e627525ba96b58654f12&quot; data-account-id=&quot;5af5e627525ba96b58654f12&quot; accountid=&quot;5af5e627525ba96b58654f12&quot; rel=&quot;noreferrer&quot;&gt;Ann-Marie Breaux&lt;/a&gt;, I am not clear how a previous call number can be supported by using a call number type. We do need the previous call number to be on the item record. (further detail: we do anticipate storing our previous call number in Marc 583 and using that to have is appear in our discovery layer.) &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5f0e3e66e5efc1001ba6a7a9&quot; class=&quot;user-hover&quot; rel=&quot;5f0e3e66e5efc1001ba6a7a9&quot; data-account-id=&quot;5f0e3e66e5efc1001ba6a7a9&quot; accountid=&quot;5f0e3e66e5efc1001ba6a7a9&quot; rel=&quot;noreferrer&quot;&gt;Jessica Janecki&lt;/a&gt;, can you envision how this might work?&lt;/p&gt;</comment>
                                                            <comment id="14753" author="5f0e3e66e5efc1001ba6a7a9" created="Fri, 18 Sep 2020 17:50:30 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5e627525ba96b58654f12&quot; class=&quot;user-hover&quot; rel=&quot;5af5e627525ba96b58654f12&quot; data-account-id=&quot;5af5e627525ba96b58654f12&quot; accountid=&quot;5af5e627525ba96b58654f12&quot; rel=&quot;noreferrer&quot;&gt;Ann-Marie Breaux&lt;/a&gt; we need this information at the item level. &lt;br/&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; we need custom fields to be searchable&lt;/p&gt;</comment>
                                                            <comment id="14754" author="63e2a2771b13d42998e4e706" created="Mon, 21 Sep 2020 13:29:52 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5f0e3e66e5efc1001ba6a7a9&quot; class=&quot;user-hover&quot; rel=&quot;5f0e3e66e5efc1001ba6a7a9&quot; data-account-id=&quot;5f0e3e66e5efc1001ba6a7a9&quot; accountid=&quot;5f0e3e66e5efc1001ba6a7a9&quot; rel=&quot;noreferrer&quot;&gt;Jessica Janecki&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5c48911d87530c43d3a188ac&quot; class=&quot;user-hover&quot; rel=&quot;5c48911d87530c43d3a188ac&quot; data-account-id=&quot;5c48911d87530c43d3a188ac&quot; accountid=&quot;5c48911d87530c43d3a188ac&quot; rel=&quot;noreferrer&quot;&gt;jackie.gottlieb@duke.edu&lt;/a&gt;&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;we need this information at the item level.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Given that inventory searches for instances, would this be something like &lt;tt&gt;find the instances where an item exists with a previous call number of ABC&lt;/tt&gt;?&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;We are not expecting FOLIO to have additional call number fields and so have assumed we will need to support this with a custom field. Yes, we expect custom fields to be searchable.&lt;/p&gt;&lt;/blockquote&gt;
&lt;blockquote&gt;&lt;p&gt;we need custom fields to be searchable&lt;/p&gt;&lt;/blockquote&gt;

&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; I believe you were involved in the original custom fields work. Was searching custom fields something that was discussed / designed in the scope of that work?&lt;/p&gt;</comment>
                                                            <comment id="14758" author="62a96ae7192edb006f9f1bf9" created="Mon, 21 Sep 2020 13:37:38 +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;, I believe the design accounts for these fields to be searchable. The work to make fields searchable needs to be done by the app team. &lt;/p&gt;</comment>
                                                            <comment id="14760" author="63e2a2771b13d42998e4e706" created="Mon, 21 Sep 2020 13:47:03 +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;&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;I believe the design accounts for these fields to be searchable&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Thanks for your quick response.&lt;/p&gt;

&lt;p&gt;I&apos;m curious about this because our current tooling (RAML Module Builder) defines databases indexes during design / coding, which effectively makes them static to every tenant. As I understand it, specific custom fields on the other hand, as designed to be defined on a per tenant basis and are not known during the design / coding part of the work.&lt;/p&gt;

&lt;p&gt;Did part of that design involve discussions about how database indexing could be done for custom fields? If so, please could you refer me to documentation or to someone who could help me understand that better.&lt;/p&gt;

&lt;p&gt;Is there an example implemented in users, which I believe was the first place custom fields were built, that can be used for reference?&lt;/p&gt;</comment>
                                                            <comment id="14764" author="5c48911d87530c43d3a188ac" created="Mon, 21 Sep 2020 16:04:02 +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; RE: Given that inventory searches for instances, would this be something like find the instances where an item exists with a previous call number of ABC?&lt;/p&gt;

&lt;p&gt;The answer is yes. I understand that the search capabilities don&apos;t take you directly to an item, they take you to an instance, but that is fine for now.&lt;/p&gt;</comment>
                                                            <comment id="14767" author="557058:2002428d-c11e-48c4-98e0-a5b1104bd0b6" created="Tue, 22 Sep 2020 11:22:13 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=63e2a2771b13d42998e4e706&quot; class=&quot;user-hover&quot; rel=&quot;63e2a2771b13d42998e4e706&quot; data-account-id=&quot;63e2a2771b13d42998e4e706&quot; accountid=&quot;63e2a2771b13d42998e4e706&quot; rel=&quot;noreferrer&quot;&gt;Marc Johnson&lt;/a&gt;&lt;br/&gt;
Custom fields assigned to a record (like users) are searchable as any other fields, because they look inside Json as regular attributes. &lt;br/&gt;
Sample user record with custom fields (&quot;customFields&quot; attribute in Json):&lt;/p&gt;

&lt;p&gt; &lt;span class=&quot;image-wrap&quot; style=&quot;&quot;&gt;&lt;a id=&quot;11280_thumb&quot; href=&quot;/rest/api/3/attachment/content/11280&quot; title=&quot;screenshot-1.png&quot; file-preview-type=&quot;image&quot; file-preview-id=&quot;11280&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/11280?default=false&quot; jira-url=&quot;https://folio-org.atlassian.net/rest/api/3/attachment/thumbnail/11280&quot; filename=&quot;screenshot-1.png&quot;&gt;&lt;img src=&quot;https://folio-org.atlassian.net/rest/api/3/attachment/thumbnail/11280&quot; data-attachment-name=&quot;screenshot-1.png&quot; data-attachment-type=&quot;thumbnail&quot; data-media-services-id=&quot;61b93a30-8a2f-4aa7-a05d-6e225ef456c7&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;

&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
{
  &lt;span class=&quot;code-quote&quot;&gt;&quot;username&quot;&lt;/span&gt; : &lt;span class=&quot;code-quote&quot;&gt;&quot;fred&quot;&lt;/span&gt;,
  &lt;span class=&quot;code-quote&quot;&gt;&quot;id&quot;&lt;/span&gt; : &lt;span class=&quot;code-quote&quot;&gt;&quot;956f39c5-92e3-4c26-bcdc-1827674710cf&quot;&lt;/span&gt;,
  &lt;span class=&quot;code-quote&quot;&gt;&quot;barcode&quot;&lt;/span&gt; : &lt;span class=&quot;code-quote&quot;&gt;&quot;890127749735764&quot;&lt;/span&gt;,
  &lt;span class=&quot;code-quote&quot;&gt;&quot;active&quot;&lt;/span&gt; : &lt;span class=&quot;code-keyword&quot;&gt;true&lt;/span&gt;,
  &lt;span class=&quot;code-quote&quot;&gt;&quot;type&quot;&lt;/span&gt; : &lt;span class=&quot;code-quote&quot;&gt;&quot;patron&quot;&lt;/span&gt;,
  &lt;span class=&quot;code-quote&quot;&gt;&quot;patronGroup&quot;&lt;/span&gt; : &lt;span class=&quot;code-quote&quot;&gt;&quot;bdc2b6d4-5ceb-4a12-ab46-249b9a68473e&quot;&lt;/span&gt;,
  &lt;span class=&quot;code-quote&quot;&gt;&quot;departments&quot;&lt;/span&gt; : [ ],
  &lt;span class=&quot;code-quote&quot;&gt;&quot;proxyFor&quot;&lt;/span&gt; : [ ],
  &lt;span class=&quot;code-quote&quot;&gt;&quot;personal&quot;&lt;/span&gt; : {
    &lt;span class=&quot;code-quote&quot;&gt;&quot;lastName&quot;&lt;/span&gt; : &lt;span class=&quot;code-quote&quot;&gt;&quot;Hilll&quot;&lt;/span&gt;,
    &lt;span class=&quot;code-quote&quot;&gt;&quot;firstName&quot;&lt;/span&gt; : &lt;span class=&quot;code-quote&quot;&gt;&quot;Santino&quot;&lt;/span&gt;,
    &lt;span class=&quot;code-quote&quot;&gt;&quot;middleName&quot;&lt;/span&gt; : &lt;span class=&quot;code-quote&quot;&gt;&quot;Travon&quot;&lt;/span&gt;,
    &lt;span class=&quot;code-quote&quot;&gt;&quot;email&quot;&lt;/span&gt; : &lt;span class=&quot;code-quote&quot;&gt;&quot;kariane@douglas-hoeger-and-stokes.py&quot;&lt;/span&gt;,
    &lt;span class=&quot;code-quote&quot;&gt;&quot;phone&quot;&lt;/span&gt; : &lt;span class=&quot;code-quote&quot;&gt;&quot;(234)617-6257 x0630&quot;&lt;/span&gt;,
    &lt;span class=&quot;code-quote&quot;&gt;&quot;mobilePhone&quot;&lt;/span&gt; : &lt;span class=&quot;code-quote&quot;&gt;&quot;1-363-752-3867 x6224&quot;&lt;/span&gt;,
    &lt;span class=&quot;code-quote&quot;&gt;&quot;dateOfBirth&quot;&lt;/span&gt; : &lt;span class=&quot;code-quote&quot;&gt;&quot;1995-04-02T00:00:00.000+0000&quot;&lt;/span&gt;,
    &lt;span class=&quot;code-quote&quot;&gt;&quot;addresses&quot;&lt;/span&gt; : [ {
      &lt;span class=&quot;code-quote&quot;&gt;&quot;countryId&quot;&lt;/span&gt; : &lt;span class=&quot;code-quote&quot;&gt;&quot;US&quot;&lt;/span&gt;,
      &lt;span class=&quot;code-quote&quot;&gt;&quot;addressLine1&quot;&lt;/span&gt; : &lt;span class=&quot;code-quote&quot;&gt;&quot;12402 Leon Passage&quot;&lt;/span&gt;,
      &lt;span class=&quot;code-quote&quot;&gt;&quot;city&quot;&lt;/span&gt; : &lt;span class=&quot;code-quote&quot;&gt;&quot;Rolling Hills Estates&quot;&lt;/span&gt;,
      &lt;span class=&quot;code-quote&quot;&gt;&quot;region&quot;&lt;/span&gt; : &lt;span class=&quot;code-quote&quot;&gt;&quot;MI&quot;&lt;/span&gt;,
      &lt;span class=&quot;code-quote&quot;&gt;&quot;postalCode&quot;&lt;/span&gt; : &lt;span class=&quot;code-quote&quot;&gt;&quot;98879-8861&quot;&lt;/span&gt;,
      &lt;span class=&quot;code-quote&quot;&gt;&quot;addressTypeId&quot;&lt;/span&gt; : &lt;span class=&quot;code-quote&quot;&gt;&quot;93d3d88d-499b-45d0-9bc7-ac73c3a19880&quot;&lt;/span&gt;,
      &lt;span class=&quot;code-quote&quot;&gt;&quot;primaryAddress&quot;&lt;/span&gt; : &lt;span class=&quot;code-keyword&quot;&gt;true&lt;/span&gt;
    } ],
    &lt;span class=&quot;code-quote&quot;&gt;&quot;preferredContactTypeId&quot;&lt;/span&gt; : &lt;span class=&quot;code-quote&quot;&gt;&quot;002&quot;&lt;/span&gt;
  },
  &lt;span class=&quot;code-quote&quot;&gt;&quot;enrollmentDate&quot;&lt;/span&gt; : &lt;span class=&quot;code-quote&quot;&gt;&quot;2017-06-05T00:00:00.000+0000&quot;&lt;/span&gt;,
  &lt;span class=&quot;code-quote&quot;&gt;&quot;expirationDate&quot;&lt;/span&gt; : &lt;span class=&quot;code-quote&quot;&gt;&quot;2020-09-28T00:00:00.000+0000&quot;&lt;/span&gt;,
  &lt;span class=&quot;code-quote&quot;&gt;&quot;createdDate&quot;&lt;/span&gt; : &lt;span class=&quot;code-quote&quot;&gt;&quot;2020-09-22T11:04:36.825+0000&quot;&lt;/span&gt;,
  &lt;span class=&quot;code-quote&quot;&gt;&quot;updatedDate&quot;&lt;/span&gt; : &lt;span class=&quot;code-quote&quot;&gt;&quot;2020-09-22T11:04:36.825+0000&quot;&lt;/span&gt;,
  &lt;span class=&quot;code-quote&quot;&gt;&quot;metadata&quot;&lt;/span&gt; : {
    &lt;span class=&quot;code-quote&quot;&gt;&quot;createdDate&quot;&lt;/span&gt; : &lt;span class=&quot;code-quote&quot;&gt;&quot;2020-09-22T01:41:26.447+0000&quot;&lt;/span&gt;,
    &lt;span class=&quot;code-quote&quot;&gt;&quot;updatedDate&quot;&lt;/span&gt; : &lt;span class=&quot;code-quote&quot;&gt;&quot;2020-09-22T11:04:36.815+0000&quot;&lt;/span&gt;,
    &lt;span class=&quot;code-quote&quot;&gt;&quot;updatedByUserId&quot;&lt;/span&gt; : &lt;span class=&quot;code-quote&quot;&gt;&quot;016bdad7-0959-5e33-af02-84a45a108e29&quot;&lt;/span&gt;
  },
  &lt;span class=&quot;code-quote&quot;&gt;&quot;customFields&quot;&lt;/span&gt; : {
    &lt;span class=&quot;code-quote&quot;&gt;&quot;phone&quot;&lt;/span&gt; : &lt;span class=&quot;code-quote&quot;&gt;&quot;602-265-5968&quot;&lt;/span&gt;,
    &lt;span class=&quot;code-quote&quot;&gt;&quot;graduated&quot;&lt;/span&gt; : &lt;span class=&quot;code-keyword&quot;&gt;true&lt;/span&gt;
  }
}
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;As you can see the user user has 2 CFs with attribute names &quot;phone&quot; and &quot;graduated&quot;. These names are defined in CF section of user settings:&lt;br/&gt;
 &lt;span class=&quot;image-wrap&quot; style=&quot;&quot;&gt;&lt;a id=&quot;11281_thumb&quot; href=&quot;/rest/api/3/attachment/content/11281&quot; title=&quot;screenshot-2.png&quot; file-preview-type=&quot;image&quot; file-preview-id=&quot;11281&quot; file-preview-title=&quot;screenshot-2.png&quot;&gt;&lt;jira-attachment-thumbnail url=&quot;https://folio-org.atlassian.net/rest/api/3/attachment/thumbnail/11281?default=false&quot; jira-url=&quot;https://folio-org.atlassian.net/rest/api/3/attachment/thumbnail/11281&quot; filename=&quot;screenshot-2.png&quot;&gt;&lt;img src=&quot;https://folio-org.atlassian.net/rest/api/3/attachment/thumbnail/11281&quot; data-attachment-name=&quot;screenshot-2.png&quot; data-attachment-type=&quot;thumbnail&quot; data-media-services-id=&quot;b79bee17-b76f-4522-825d-c83f221acc97&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;

&lt;p&gt;You can take a look at &lt;tt&gt;mod-users&lt;/tt&gt; code to see how CFs integrated into Users.There is also a recording related to CFs overview conducted by Spitfire team. Please ask &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; for a link&lt;/p&gt;

&lt;p&gt;Regarding the indexes, there are no predefined indexes but you can add some in schema.json as you do in other cases &lt;/p&gt;</comment>
                                                            <comment id="14771" author="5c48911d87530c43d3a188ac" created="Tue, 22 Sep 2020 14:04:12 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A2002428d-c11e-48c4-98e0-a5b1104bd0b6&quot; class=&quot;user-hover&quot; rel=&quot;557058:2002428d-c11e-48c4-98e0-a5b1104bd0b6&quot; data-account-id=&quot;557058:2002428d-c11e-48c4-98e0-a5b1104bd0b6&quot; accountid=&quot;557058:2002428d-c11e-48c4-98e0-a5b1104bd0b6&quot; rel=&quot;noreferrer&quot;&gt;Dima Tkachenko&lt;/a&gt;, Thank you! This is very helpful information. &lt;/p&gt;</comment>
                                                            <comment id="14774" author="63e2a2771b13d42998e4e706" created="Tue, 22 Sep 2020 15:29:44 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A2002428d-c11e-48c4-98e0-a5b1104bd0b6&quot; class=&quot;user-hover&quot; rel=&quot;557058:2002428d-c11e-48c4-98e0-a5b1104bd0b6&quot; data-account-id=&quot;557058:2002428d-c11e-48c4-98e0-a5b1104bd0b6&quot; accountid=&quot;557058:2002428d-c11e-48c4-98e0-a5b1104bd0b6&quot; rel=&quot;noreferrer&quot;&gt;Dima Tkachenko&lt;/a&gt; Thank you for your response.&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;Custom fields assigned to a record (like users) are searchable as any other fields, because they look inside Json as regular attributes.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;In inventory, due to the quantity of records, we typically do not support searching without an underlying database index, as that results in very poor performance. There is an ongoing debate about whether this should always be the case on 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-2573&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-2573&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Paused due to POC of Elastic Search. All Search Options Should be Supported by a Database Index&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            FOLIO-2573
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
.&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;Regarding the indexes, there are no predefined indexes but you can add some in schema.json as you do in other cases&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;I&apos;m not sure I understand how that would work in practice.&lt;/p&gt;

&lt;p&gt;Schema.json is used to define database indexes during development of a module version. As custom fields are defined specifically for a tenant, during the operation of the system, they are not known during development. How would developers know to define a database index for a property that does not exist during development, and may not exist for many organisations (tenants)? &lt;/p&gt;</comment>
                                                            <comment id="14776" author="557058:2002428d-c11e-48c4-98e0-a5b1104bd0b6" created="Tue, 22 Sep 2020 15:56:59 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=63e2a2771b13d42998e4e706&quot; class=&quot;user-hover&quot; rel=&quot;63e2a2771b13d42998e4e706&quot; data-account-id=&quot;63e2a2771b13d42998e4e706&quot; accountid=&quot;63e2a2771b13d42998e4e706&quot; rel=&quot;noreferrer&quot;&gt;Marc Johnson&lt;/a&gt;&lt;br/&gt;
I&apos;m not an expert in json indexes. As I understand if you what to create a specific index on a specific field, like &quot;phone&quot; in my example, this is not possible beforehand unless you know the name. May be you can some how build an index on the content of &quot;customFields&quot; element.. &lt;br/&gt;
Cannot give you the immediate recommendations/guidance, it has to be investigated further&lt;/p&gt;</comment>
                                                            <comment id="14780" author="63e2a2771b13d42998e4e706" created="Tue, 22 Sep 2020 16:06:44 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A2002428d-c11e-48c4-98e0-a5b1104bd0b6&quot; class=&quot;user-hover&quot; rel=&quot;557058:2002428d-c11e-48c4-98e0-a5b1104bd0b6&quot; data-account-id=&quot;557058:2002428d-c11e-48c4-98e0-a5b1104bd0b6&quot; accountid=&quot;557058:2002428d-c11e-48c4-98e0-a5b1104bd0b6&quot; rel=&quot;noreferrer&quot;&gt;Dima Tkachenko&lt;/a&gt; Thank you.&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;As I understand if you what to create a specific index on a specific field, like &quot;phone&quot; in my example, this is not possible beforehand unless you know the name.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;That fits with my understanding.&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;Maybe you can some how build an index on the content of &quot;customFields&quot; element.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;I don&apos;t think that indexing the custom fields object as a whole is likely to give folks the behaviour they expect. I think they expect to be able to search specifically on a particular field.&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;Cannot give you the immediate recomendations/guidance, it has to be investigated additionally&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Who is going to do that investigation?&lt;/p&gt;</comment>
                                                            <comment id="14783" author="70121:84bca0b8-4380-4d87-8a90-53e9133584f6" created="Tue, 22 Sep 2020 16:55:23 +0000"  >&lt;p&gt;Searching over custom fields can be done smoothly using Elastic Search. Two approaches can be used depending on requirements:&lt;br/&gt;
1.) If there is a requirement to have facets for custom fields or to search only over one of this custom fields, &lt;a href=&quot;https://www.elastic.co/guide/en/elasticsearch/reference/current/dynamic-field-mapping.html&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://www.elastic.co/guide/en/elasticsearch/reference/current/dynamic-field-mapping.html&lt;/a&gt; could be leveraged. In such case tenants can work with custom fields like with ordinary one even not caring about that they are custom.&lt;br/&gt;
The drawback of it can be that there could be a plenty of fields. And ES is not supposed to handle thousands of different fields in one index.&lt;br/&gt;
2.) More simple approach is to make heap of all custom fields in one ES field. It will be good in terms of searching performance. But it won&apos;t allow to search only over one field. Although there could be different fields for different types of values (e.g. string, number etc), it is pretty limited and I don&apos;t recommend to go with it.&lt;/p&gt;</comment>
                                                            <comment id="14786" author="5c48911d87530c43d3a188ac" created="Tue, 22 Sep 2020 17:59:22 +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;, Thank you for your engagement and exploration of this. If I am understanding this so far, we can &apos;sort of&apos; get the custom field indexed but the behavior may not be what is expected; investigation is needed. Mikhail is offering Elastic Search as possible solution, though as far as I am aware, Elastic Search hasn&apos;t yet been confirmed to be implemented. &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Af80403de-e149-421e-8750-af45c853402f&quot; class=&quot;user-hover&quot; rel=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; data-account-id=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; accountid=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; rel=&quot;noreferrer&quot;&gt;Charlotte Whitt&lt;/a&gt;, Where do we go from here? What should be the next step? I felt the need to explain why Duke ranked it R1 since Chicago and us are the only 2. &lt;/p&gt;</comment>
                                                            <comment id="14790" author="62a96ae7192edb006f9f1bf9" created="Tue, 22 Sep 2020 18:03:40 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5c48911d87530c43d3a188ac&quot; class=&quot;user-hover&quot; rel=&quot;5c48911d87530c43d3a188ac&quot; data-account-id=&quot;5c48911d87530c43d3a188ac&quot; accountid=&quot;5c48911d87530c43d3a188ac&quot; rel=&quot;noreferrer&quot;&gt;jackie.gottlieb@duke.edu&lt;/a&gt; and &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Af80403de-e149-421e-8750-af45c853402f&quot; class=&quot;user-hover&quot; rel=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; data-account-id=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; accountid=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; rel=&quot;noreferrer&quot;&gt;Charlotte Whitt&lt;/a&gt;, I recommend a separate feature = Inventory App | Search custom fields. &lt;/p&gt;</comment>
                                                            <comment id="14793" author="63e2a2771b13d42998e4e706" created="Fri, 25 Sep 2020 09:28:59 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5c48911d87530c43d3a188ac&quot; class=&quot;user-hover&quot; rel=&quot;5c48911d87530c43d3a188ac&quot; data-account-id=&quot;5c48911d87530c43d3a188ac&quot; accountid=&quot;5c48911d87530c43d3a188ac&quot; rel=&quot;noreferrer&quot;&gt;jackie.gottlieb@duke.edu&lt;/a&gt;&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;Thank you for your engagement and exploration of this. If I am understanding this so far, we can &apos;sort of&apos; get the custom field indexed but the behavior may not be what is expected;&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;At the moment, our approach to indexing requires developers to know the field to be indexed during development. As custom fields are inherently intended to be configured after development, the current approach doesn&apos;t make sense for them (we&apos;d be adding indexes for fields that aren&apos;t there), without compromising their intent (that custom fields are custom and configured by tenants dynamically).&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;as far as I am aware, Elastic Search hasn&apos;t yet been confirmed to be implemented&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;The Technical Council are intending to discuss this next week.&lt;/p&gt;</comment>
                                                            <comment id="14797" author="63e2a2771b13d42998e4e706" created="Fri, 25 Sep 2020 09:30:33 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=70121%3A84bca0b8-4380-4d87-8a90-53e9133584f6&quot; class=&quot;user-hover&quot; rel=&quot;70121:84bca0b8-4380-4d87-8a90-53e9133584f6&quot; data-account-id=&quot;70121:84bca0b8-4380-4d87-8a90-53e9133584f6&quot; accountid=&quot;70121:84bca0b8-4380-4d87-8a90-53e9133584f6&quot; rel=&quot;noreferrer&quot;&gt;Mikhail Fokanov&lt;/a&gt;&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;Searching over custom fields can be done smoothly using Elastic Search&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;I have no doubt that elastic search can index custom fields. What I don&apos;t understand is how it inherently resolves the challenge with custom fields. Does the current Elastic Search proposal include information about how indexes in Elastic Search might be defined dynamically after development?&lt;/p&gt;</comment>
                                                            <comment id="14800" author="70121:84bca0b8-4380-4d87-8a90-53e9133584f6" created="Fri, 25 Sep 2020 12:14:20 +0000"  >&lt;blockquote&gt;&lt;p&gt;Does the current Elastic Search proposal include information about how indexes in Elastic Search might be defined dynamically after development&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;It doesn&apos;t include such information due to absence of this requirements at time of its writing. Dynamic mapping for Elastic Search indexes is needed only if there is such a requirement. So if Elastic is selected as the solution for this issue, I will add such implementation notes to the Search page.&lt;/p&gt;</comment>
                                                            <comment id="14803" author="63e2a2771b13d42998e4e706" created="Fri, 25 Sep 2020 12:18:05 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=70121%3A84bca0b8-4380-4d87-8a90-53e9133584f6&quot; class=&quot;user-hover&quot; rel=&quot;70121:84bca0b8-4380-4d87-8a90-53e9133584f6&quot; data-account-id=&quot;70121:84bca0b8-4380-4d87-8a90-53e9133584f6&quot; accountid=&quot;70121:84bca0b8-4380-4d87-8a90-53e9133584f6&quot; rel=&quot;noreferrer&quot;&gt;Mikhail Fokanov&lt;/a&gt; Thank you for the clarification&lt;/p&gt;</comment>
                                                            <comment id="14806" author="5c48911d87530c43d3a188ac" created="Mon, 30 Nov 2020 21:22:41 +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;, is there a reason for this feature/story not to be directly linked to the custom fields epic (&lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-396&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://folio-org.atlassian.net/browse/UXPROD-396&lt;/a&gt;)? What is the next step in making progress on this? Thanks, Jackie&lt;/p&gt;</comment>
                                                            <comment id="14809" author="557058:c2706f9e-f281-4999-8937-b5c5a8ff211f" created="Wed, 9 Dec 2020 20:34:08 +0000"  >&lt;p&gt;Personally, I would like to see a property of some kind that lets you add in whatever extra properties you need, and not even necessarily have to be defined through Settings like custom fields do. For example, I need to add a date/time value property to holdings that indicate when a holding was stored to OCLC&apos;s database. It&apos;s not something that would need to be rendered in the FOLIO UI. It&apos;s just a field that an external batch program would make use of. Not sure if the customFields property could do that, or, if it should be some other property, like &quot;extraFields&quot; or something along those lines. It wouldn&apos;t need validation or anything. I have a need to do something similar in locations as well for the spine label printing app that I&apos;m working on. It would be good if it were implemented across the board for all objects (or at least the top-level ones that appear as tables).&lt;/p&gt;</comment>
                                                            <comment id="14812" author="557058:f80403de-e149-421e-8750-af45c853402f" created="Thu, 10 Dec 2020 14:53:25 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ac2706f9e-f281-4999-8937-b5c5a8ff211f&quot; class=&quot;user-hover&quot; rel=&quot;557058:c2706f9e-f281-4999-8937-b5c5a8ff211f&quot; data-account-id=&quot;557058:c2706f9e-f281-4999-8937-b5c5a8ff211f&quot; accountid=&quot;557058:c2706f9e-f281-4999-8937-b5c5a8ff211f&quot; rel=&quot;noreferrer&quot;&gt;Jon Miller&lt;/a&gt; - I agree. I think the current implementation having the custom fields in a dedicated accordion, might just be a short term solution. &lt;/p&gt;

&lt;p&gt;I&apos;ll loop in &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; who will be more able to answer your question, and explain the short term solution and possible plans for more long term solution. &lt;/p&gt;</comment>
                                                            <comment id="14816" author="62a96ae7192edb006f9f1bf9" created="Thu, 10 Dec 2020 15:20:31 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5c48911d87530c43d3a188ac&quot; class=&quot;user-hover&quot; rel=&quot;5c48911d87530c43d3a188ac&quot; data-account-id=&quot;5c48911d87530c43d3a188ac&quot; accountid=&quot;5c48911d87530c43d3a188ac&quot; rel=&quot;noreferrer&quot;&gt;jackie.gottlieb@duke.edu&lt;/a&gt;, it is up to &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Af80403de-e149-421e-8750-af45c853402f&quot; class=&quot;user-hover&quot; rel=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; data-account-id=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; accountid=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; rel=&quot;noreferrer&quot;&gt;Charlotte Whitt&lt;/a&gt; and Core-Functional to move forward on this feature. &lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                            <outwardlinks description="blocks">
                                        <issuelink>
            <issuekey id="13184">UXPROD-2848</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="13176">UXPROD-2248</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                            <issuelinktype id="10001">
                    <name>Cloners</name>
                                                                <inwardlinks description="is cloned by">
                                        <issuelink>
            <issuekey id="13338">UXPROD-3580</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10008">
                    <name>Defines</name>
                                            <outwardlinks description="defines">
                                        <issuelink>
            <issuekey id="13688">UXPROD-396</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="13170">UXPROD-2178</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="11798">UXPROD-2212</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="10222">UXPROD-33</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="11256">UXPROD-2143</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="11280" name="screenshot-1.png" size="501419" author="557058:2002428d-c11e-48c4-98e0-a5b1104bd0b6" created="Tue, 22 Sep 2020 11:08:48 +0000"/>
                            <attachment id="11281" name="screenshot-2.png" size="257219" author="557058:2002428d-c11e-48c4-98e0-a5b1104bd0b6" created="Tue, 22 Sep 2020 11:11:56 +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="10123"><![CDATA[XL < 15 days]]></customfieldvalue>

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

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10055" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Back-End Confidence factor</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10129"><![CDATA[20%]]></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="10153"><![CDATA[Folijet]]></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)">Custom Fields</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10050" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Front End Estimate</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10099"><![CDATA[XL < 15 days]]></customfieldvalue>

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

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

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_10062" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>Kiwi Planning Points (DO NOT CHANGE)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>33.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                            <customfield id="customfield_10063" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>PO Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>81.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_10019" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i00j47:</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="10224"><![CDATA[R2]]></customfieldvalue>

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

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

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10091" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: U of AL (MVP Oct 2020)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10325"><![CDATA[R2]]></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_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_10095" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>Score</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>30.5</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, 17 Jun 2020 21:15:07 +0000</customfieldvalue>

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