<!-- 
RSS generated by JIRA (1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d) at Fri Feb 09 00:24:24 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary add field=key&field=summary to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>FOLIO Jira</title>
    <link>https://folio-org.atlassian.net</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>1001.0.0-SNAPSHOT</version>
        <build-number>100246</build-number>
        <build-date>07-02-2024</build-date>
    </build-info>

<item>
            <title>[UXPROD-2490] Add preferred pronouns to user record</title>
                <link>https://folio-org.atlassian.net/browse/UXPROD-2490</link>
                <project id="10000" key="UXPROD">UX Product</project>
                    <description>&lt;p&gt;Add preferred pronouns as a field in the user record; not as a custom field.&lt;/p&gt;</description>
                <environment></environment>
        <key id="11488">UXPROD-2490</key>
            <summary>Add preferred pronouns to user record</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="13651">UXPROD-784</parent>
                                    <priority id="10005" iconUrl="https://dev.folio.org/assets/jira-priority/tbd.svg">TBD</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="5f5241b9fcaf93003b5bee25">patty.wanninger</assignee>
                                                                <reporter accountid="5f5241b9fcaf93003b5bee25">patty.wanninger</reporter>
                                    <labels>
                    </labels>
                <created>Sun, 14 Jun 2020 23:51:36 +0000</created>
                <updated>Mon, 18 Dec 2023 19:01:50 +0000</updated>
                            <resolved>Tue, 15 Sep 2020 15:27:41 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                <comments>
                                                            <comment id="14655" author="5c48911b54e1e6466b11f38c" created="Tue, 16 Jun 2020 20:23:30 +0000"  >&lt;p&gt;Can we clarify that this is to add the field to the User Information accordion, so that it appears with other name information for the patron?&lt;/p&gt;</comment>
                                                            <comment id="14657" author="5f5241b9fcaf93003b5bee25" created="Tue, 15 Sep 2020 15:27:41 +0000"  >&lt;p&gt;preferred pronouns can be put in a custom field.&lt;/p&gt;</comment>
                                                            <comment id="14659" author="557058:8eb52188-0565-4921-b55b-b0b42e919590" created="Thu, 11 Mar 2021 18:27:08 +0000"  >&lt;p&gt;Just following up on this, as custom fields don&apos;t display in the checkout app. Do we need to revisit this question?&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;</comment>
                                                            <comment id="14661" author="557058:8eb52188-0565-4921-b55b-b0b42e919590" created="Thu, 11 Mar 2021 18:47:47 +0000"  >&lt;p&gt;Would one option be to allow custom fields in the users app to be flagged to appear as part of patron data in the checkout app? That would create a great deal of flexibility that would cover not just personal pronouns but other info as well.&lt;/p&gt;</comment>
                                                            <comment id="14665" author="5f5241b9fcaf93003b5bee25" created="Thu, 11 Mar 2021 19:02:00 +0000"  >&lt;p&gt;That would be a different ticket, as this isn&apos;t a custom field. You should reach out to Erin Nettifee, because Duke is doing work to make custom fields work as checkout tokens, and see what she thinks of this idea. You can also come to User Management with this idea.&#160;&lt;/p&gt;</comment>
                                                            <comment id="14669" author="5c48911b54e1e6466b11f38c" created="Thu, 11 Mar 2021 19:04:55 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A8eb52188-0565-4921-b55b-b0b42e919590&quot; class=&quot;user-hover&quot; rel=&quot;557058:8eb52188-0565-4921-b55b-b0b42e919590&quot; data-account-id=&quot;557058:8eb52188-0565-4921-b55b-b0b42e919590&quot; accountid=&quot;557058:8eb52188-0565-4921-b55b-b0b42e919590&quot; rel=&quot;noreferrer&quot;&gt;David Bottorff&lt;/a&gt; If I remember correctly, we did not like the idea of putting preferred pronouns in a custom field because that accordion is far down the page, and because it is easily hidden and would make it easy to unintentionally misgender a patron.&lt;/p&gt;

&lt;p&gt;Say, perhaps, that a patron told us that their preferred pronouns are they/them, and we update their user record, but they come up to the desk later on and the staff member they see at their next visit doesn&apos;t realize they had provided their pronouns, and misgenders the patron. That is a bad scenario for the library and the patron.&lt;/p&gt;</comment>
                                                            <comment id="14673" author="557058:8eb52188-0565-4921-b55b-b0b42e919590" created="Thu, 11 Mar 2021 19:51:45 +0000"  >&lt;p&gt;Hi &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; Erin, that makes sense to me. My concern is that right now neither preferred name nor preferred pronouns are displayed on the checkout app at all, which is frankly where more frontline staff will interact with patrons. It doesn&apos;t appear there is a ticket for preferred name to appear in the checkout app. That seems like something worth opening, and higher priority than pronouns to me. There also doesn&apos;t appear to be an open Jira for preferred pronouns at all, only this one closed as &quot;won&apos;t do&quot;&lt;/p&gt;</comment>
                                                            <comment id="14676" author="5c48911b54e1e6466b11f38c" created="Thu, 11 Mar 2021 19:55:47 +0000"  >&lt;p&gt;Yah &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5f5241b9fcaf93003b5bee25&quot; class=&quot;user-hover&quot; rel=&quot;5f5241b9fcaf93003b5bee25&quot; data-account-id=&quot;5f5241b9fcaf93003b5bee25&quot; accountid=&quot;5f5241b9fcaf93003b5bee25&quot; rel=&quot;noreferrer&quot;&gt;patty.wanninger&lt;/a&gt; I think David&apos;s right - this may have been closed with the assumption a custom field would suffice, but given that it won&apos;t, we need a new feature to scope out requirements. &lt;/p&gt;</comment>
                                                            <comment id="14678" author="557058:8eb52188-0565-4921-b55b-b0b42e919590" created="Thu, 11 Mar 2021 19:58:39 +0000"  >&lt;p&gt;&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;&#160; I concur that a new ticket should be opened for preferred pronouns. I also am seeing &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5f5241b9fcaf93003b5bee25&quot; class=&quot;user-hover&quot; rel=&quot;5f5241b9fcaf93003b5bee25&quot; data-account-id=&quot;5f5241b9fcaf93003b5bee25&quot; accountid=&quot;5f5241b9fcaf93003b5bee25&quot; rel=&quot;noreferrer&quot;&gt;patty.wanninger&lt;/a&gt;&apos;s comment on the preferred name ticket that a story for displaying preferred name in the checkout app and elsewhere is being drafted, which is great news!&lt;/p&gt;

&lt;p&gt;I still wonder if, as a lower priority, there might be an argument to be made to allow institutions creating custom fields to indicate whether those custom fields should display in the patron info pane of the checkout app.&lt;/p&gt;</comment>
                                                            <comment id="14682" author="5f5241b9fcaf93003b5bee25" created="Thu, 11 Mar 2021 20:44:41 +0000"  >&lt;p&gt;Either UM or RA could write a new feature for putting custom fields the the checkout patron display. &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A8eb52188-0565-4921-b55b-b0b42e919590&quot; class=&quot;user-hover&quot; rel=&quot;557058:8eb52188-0565-4921-b55b-b0b42e919590&quot; data-account-id=&quot;557058:8eb52188-0565-4921-b55b-b0b42e919590&quot; accountid=&quot;557058:8eb52188-0565-4921-b55b-b0b42e919590&quot; rel=&quot;noreferrer&quot;&gt;David Bottorff&lt;/a&gt;&#160;and &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;&#160;Let me know if you want UM to do it - David, you could talk to Maura, who is the convener of the UM SIG.&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;</comment>
                                                            <comment id="14684" author="557058:8eb52188-0565-4921-b55b-b0b42e919590" created="Fri, 12 Mar 2021 16:01:22 +0000"  >&lt;p&gt;Probably makes sense for RA to do it, given that it&apos;s adding info to the Checkout App. I&apos;ll bring it up on Monday&apos;s call.&lt;/p&gt;</comment>
                                                            <comment id="14686" author="557058:8eb52188-0565-4921-b55b-b0b42e919590" created="Fri, 12 Mar 2021 17:53:07 +0000"  >&lt;p&gt;I&apos;ll also add that my understanding is that calling them &quot;preferred pronouns&quot; is something being moved away from, at least in some areas, as one&apos;s pronouns aren&apos;t a preference. &quot;Pronouns of refereence&quot; or simply &quot;pronouns&quot; would probably be a better term&#160;&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="13585">UXPROD-4603</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10000" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummarycf">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10014" key="com.pyxis.greenhopper.jira:gh-epic-link">
                        <customfieldname>Epic Link</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue key="$xmlutils.escape($text)">Users App</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10045" key="com.atlassian.jira.plugin.system.customfieldtypes:textarea">
                        <customfieldname>Potential Workaround</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Add pronouns as a custom field and allow custom fields to be placed in the user record by tenant.</customfieldvalue>

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

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                            <customfield id="customfield_10069" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: Cornell (Full Sum 2021)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10213"><![CDATA[R1]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10070" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: Duke (Full Sum 2021)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10218"><![CDATA[R1]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_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>Tue, 16 Jun 2020 20:23:30 +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>