<!-- 
RSS generated by JIRA (1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d) at Fri Feb 09 00:14:23 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-1295] Users App: Add phone number type and email validation to user records</title>
                <link>https://folio-org.atlassian.net/browse/UXPROD-1295</link>
                <project id="10000" key="UXPROD">UX Product</project>
                    <description>&lt;p&gt;Add the following fields to User Detail Record&lt;/p&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;Title/Prefix (also add to user import) - these will be handled with custom fields&lt;/li&gt;
	&lt;li&gt;Preferred pronouns - custom field&lt;br/&gt;
&lt;img class=&quot;emoticon&quot; src=&quot;/images/icons/emoticons/error.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt; alternate name (nickname) - Preferred name  
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;UIU-1649&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UIU-1649&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Preferred first name field on user record&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10309?size=medium&quot; /&gt;
            UIU-1649
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
&lt;/li&gt;
	&lt;li&gt;Add validation to email field&lt;/li&gt;
	&lt;li&gt;Add phone number types&lt;/li&gt;
&lt;/ul&gt;
</description>
                <environment></environment>
        <key id="10832">UXPROD-1295</key>
            <summary>Users App: Add phone number type and email validation to user records</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="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="5f5241b9fcaf93003b5bee25">patty.wanninger</assignee>
                                                                <reporter accountid="62a96ae7192edb006f9f1bf9">Khalilah Gambrell</reporter>
                                    <labels>
                            <label>cap-mvp</label>
                            <label>migration-load</label>
                            <label>po-mvp</label>
                            <label>q4-2019-spillover</label>
                            <label>usermanagement</label>
                    </labels>
                <created>Tue, 6 Nov 2018 19:40:17 +0000</created>
                <updated>Mon, 2 Aug 2021 11:59:05 +0000</updated>
                            <resolved>Wed, 27 May 2020 17:52:40 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>7</watches>
                                                                <comments>
                                                            <comment id="13748" author="5af5ed55244bc90a106063c7" created="Wed, 5 Dec 2018 14:34:21 +0000"  >&lt;p&gt;Removing Q1 2019 fix version due to limited capacity in Q1 2019.  &lt;/p&gt;</comment>
                                                            <comment id="13750" author="5c48911b54e1e6466b11f38c" created="Mon, 5 Aug 2019 20:24:32 +0000"  >&lt;p&gt;
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;UXPROD-261&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-261&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Users App: Additional Identifier Fields&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10322?size=medium&quot; /&gt;
            UXPROD-261
        &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;
 is closed with a note that it would be addressed here - so Duke wants to make absolutely sure that this feature includes the need to have more than three identifiers on a record. The cap of three identifiers is a blocker for us.&lt;/p&gt;

&lt;p&gt;Duke University supports card functions on phones via Apple Wallet and Google Pay, with Blackboard as the backend. That adds to our ID list since many students use their phones as their identification cards. &lt;/p&gt;

&lt;p&gt;So a student with an issued university ID card who also has an iPhone will have the following multiple IDs that FOLIO will need to support: university identifier (unique ID); netID; barcode (on physical card); iPhone ID (uploaded to Blackboard). So that&apos;s 5 identifiers. &lt;/p&gt;

&lt;p&gt;A student in that scenario who picks up a research work-study at our hospital may get an additional identifier in the system for the hospital&apos;s separate door management system. Someone buys them a Google watch, they then might up with seven identifiers. They study abroad at our China campus for a summer, they get eight identifiers that they will expect to be able to freely swap with the physical card.&lt;/p&gt;

&lt;p&gt;What we want to make clear is we don&apos;t see an obvious cap that we would be happy with in the system because we expect this kind of card-of-things ecosystem to grow at Duke, and it will almost certainly appear at other institutions as well.&lt;/p&gt;

&lt;p&gt;Unlike some of the other fields listed here, identifiers do have business logic and workflow considerations especially in terms of questions about anonymization, SSO, user lookup and connecting user records across apps.&lt;/p&gt;
</comment>
                                                            <comment id="13757" author="557058:f80403de-e149-421e-8750-af45c853402f" created="Thu, 3 Oct 2019 19:24:46 +0000"  >&lt;p&gt;Hi &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; - in a meeting discussing migration of User data, then we talked about the need for an element to store Statistical codes (Statistical categories). These locally-created statistical codes are used to associate a patron with categories of importance to the institution. &lt;/p&gt;

&lt;p&gt;In the GAPs analysis from 2018 Statistical codes were identified as a missing element - see row #4 in the spreadsheet - &lt;a href=&quot;https://docs.google.com/spreadsheets/d/1jiMJz-wTBhSkpVrJOFQh2tGmm9-AXATphu2dMcACkws/edit#gid=1182096279&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://docs.google.com/spreadsheets/d/1jiMJz-wTBhSkpVrJOFQh2tGmm9-AXATphu2dMcACkws/edit#gid=1182096279&lt;/a&gt;&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;This gap was discussed and validated by user management SIG. Cornell: we NEED these codes. They are VITAL to reporting, and are useful for other functions, such as helping patrons at reference and circulation.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;So it seams like an element several libraries would need for their migration, and therefore it might be better to have Statistical codes implemented as a dedicated FOLIO element, where libraries can customize their values in a reference table - and not something each library should implement by using  customizable fields. &lt;/p&gt;

&lt;p&gt;CC: &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ac8ae162b-1267-4990-9205-42958e72b515&quot; class=&quot;user-hover&quot; rel=&quot;557058:c8ae162b-1267-4990-9205-42958e72b515&quot; data-account-id=&quot;557058:c8ae162b-1267-4990-9205-42958e72b515&quot; accountid=&quot;557058:c8ae162b-1267-4990-9205-42958e72b515&quot; rel=&quot;noreferrer&quot;&gt;Maura Byrne&lt;/a&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; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5c706fbb47a54a6728e59df2&quot; class=&quot;user-hover&quot; rel=&quot;5c706fbb47a54a6728e59df2&quot; data-account-id=&quot;5c706fbb47a54a6728e59df2&quot; accountid=&quot;5c706fbb47a54a6728e59df2&quot; rel=&quot;noreferrer&quot;&gt;Wayne Schneider&lt;/a&gt;&lt;/p&gt;


</comment>
                                                            <comment id="13759" author="5c48911b54e1e6466b11f38c" created="Thu, 3 Oct 2019 19:39:45 +0000"  >&lt;p&gt;Hi &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&apos;ll give some feedback with the caveat that I may not understand all of the available feature set that we could get with using statistical codes.&lt;/p&gt;

&lt;p&gt;One concern about the statistical codes feature was the UI experience in settings - you can&apos;t sort any of the values, for example. Most of the universities on the UM call are large and would have department lists that could be several hundred items long. I also can&apos;t create a statistical type and then assign a new code to that type (I will report that as a bug - I was just testing in FOLIO-snapshot.)&lt;/p&gt;

&lt;p&gt;Also, as far as I have understood it, using statistical codes means that libraries would maintain their own copies of the departmental value field. &lt;b&gt;Assuming that custom fields are available for the bulk loader&lt;/b&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;, if they were used, it could simply store a value provided by central IDM and then we wouldn&apos;t have to maintain our own list. &lt;/p&gt;

&lt;p&gt;If we used statistical codes instead, we&apos;d have to write a separate integration to update that list with the list of departments from identity management, and then another integration to actually load patrons with those values. Or perhaps those updates could happen in one integration script. But it doesn&apos;t seem to gain anything by storing the value in its own table when its already being sent in from the central source and can just go straight into the user record directly.&lt;/p&gt;</comment>
                                                            <comment id="13761" author="557058:f80403de-e149-421e-8750-af45c853402f" created="Thu, 3 Oct 2019 19:57:53 +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; - thank you so much for you fast feedback. &lt;/p&gt;

&lt;p&gt;In Inventory we have implemented Statistical code types, and Statistical codes. These list are maintained as reference tables in the Settings app &amp;gt; Inventory. A similar solution for the User app with reference data could easily be populate with the separate institutions data, e.g. a list of departments from identity management. &lt;/p&gt;

&lt;p&gt;Maybe &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5c706fbb47a54a6728e59df2&quot; class=&quot;user-hover&quot; rel=&quot;5c706fbb47a54a6728e59df2&quot; data-account-id=&quot;5c706fbb47a54a6728e59df2&quot; accountid=&quot;5c706fbb47a54a6728e59df2&quot; rel=&quot;noreferrer&quot;&gt;Wayne Schneider&lt;/a&gt; can say a little more about if there would be a need for two steps in the integration process or updates could happen in one integration script.  &lt;/p&gt;

&lt;p&gt;Re. the &lt;b&gt;bug&lt;/b&gt;: can&apos;t create a statistical type and then assign a new code to that type - then that&apos;s such an annoying bug! It was filed as: 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;UIIN-725&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UIIN-725&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Inability to create a statistical code&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10303?size=medium&quot; /&gt;
            UIIN-725
        &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;br/&gt;
Inability to create a statistical code, and should have been solved by now.&lt;/p&gt;</comment>
                                                            <comment id="13763" author="5c48911b54e1e6466b11f38c" created="Thu, 3 Oct 2019 20:12:11 +0000"  >&lt;p&gt;Sure, I&#8217;ll check again before submitting the bug to make sure it&#8217;s repeatable. &lt;/p&gt;

&lt;p&gt;With regards to using statistical codes, it&#8217;s unclear to me what the use case is for that approach over using custom fields. Can you explain that more?&lt;/p&gt;</comment>
                                                            <comment id="13765" author="5c706fbb47a54a6728e59df2" created="Thu, 3 Oct 2019 20:38:53 +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; I think that custom fields are a possible workaround for a system not supporting a multi-value, coded field (or controlled vocabulary) for tracking users statistical categories or classes. Some disadvantages:&lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;A custom field will not have a controlled vocabulary maintained in the system&lt;/li&gt;
	&lt;li&gt;Unless custom fields can be arrays (not clear to me from the documentation I&apos;ve seen), each facet you wish to report on would need to be captured with a separate custom field.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Different systems support this kind of requirement in different ways. It can be useful to think of a field that contains statistical categories for reporting separate from information that describes the patron or the patron&apos;s access privileges. I don&apos;t know if that&apos;s convincing to the UM SIG members &amp;#8211; &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 I were trying to chase down how the identified gap above was resolved. Perhaps the SIG decided it was not a major issue, after all, and that custom fields meet the requirement.&lt;/p&gt;

&lt;p&gt;With respect to maintaining a code list based on a central registry &amp;#8211; I agree that if that is a requirement, it would be a separate integration to account for, whether or not it is run in one script or two.&lt;/p&gt;</comment>
                                                            <comment id="13767" author="62a96ae7192edb006f9f1bf9" created="Fri, 4 Oct 2019 00:04:19 +0000"  >&lt;p&gt;I think custom fields can support. Maybe we can get on a call to discuss but I don&apos;t see any reason why custom fields could not do what&apos;s described. In fact I have outlined some requirements related to it.&lt;/p&gt;</comment>
                                                            <comment id="13769" author="5c48911b54e1e6466b11f38c" created="Fri, 4 Oct 2019 12:14:40 +0000"  >&lt;p&gt;Hi all - a few followups to this this morning.&lt;/p&gt;

&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;: FWIW, we did scope department as its own field, and that&apos;s in process. See 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;UIU-1224&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UIU-1224&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Create/Edit/View User Record |  add Department field &quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10309?size=medium&quot; /&gt;
            UIU-1224
        &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;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5c706fbb47a54a6728e59df2&quot; class=&quot;user-hover&quot; rel=&quot;5c706fbb47a54a6728e59df2&quot; data-account-id=&quot;5c706fbb47a54a6728e59df2&quot; accountid=&quot;5c706fbb47a54a6728e59df2&quot; rel=&quot;noreferrer&quot;&gt;Wayne Schneider&lt;/a&gt;: It&apos;s not my call as to whether this gets reassessed, so I hope it&apos;s not coming across that way. The last time the SIG touched on this was in July - &lt;a href=&quot;https://folio-org.atlassian.net/wiki/display/UM/2019-07-31+Meeting+notes&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://folio-org.atlassian.net/wiki/display/UM/2019-07-31+Meeting+notes&lt;/a&gt; - and we were looking at a lot of this from the eye of what needed to go in the MVP and trying to be pretty focused on not asking for features that we didn&apos;t think were absolutely needed. If you or others from implementing institutions feel its important and should be reassessed, it could certainly be proposed for an upcoming SIG meeting.&lt;/p&gt;

&lt;p&gt;I do think we&apos;re also conflating a bit the use cases where data needs to be managed in FOLIO for users (say, for users created manually,) and use cases where the data is coming in externally and managed externally. In the case of department in the IdM field, as far as I&apos;m concerned, it&apos;s already a controlled vocabulary that&apos;s controlled outside of FOLIO and so I would want to do the least amount of management possible. Of course, there are also questions then about how fields themselves are editable or not editable, and how much you might need to clean up manually added data.&lt;/p&gt;

&lt;p&gt;If we did implement statistical fields, I would want UI improvements to the way that they are controlled in Settings. I don&apos;t find the UI usable for long lists that have to be managed in the FOLIO GUI.&lt;/p&gt;</comment>
                                                            <comment id="13770" author="557058:f80403de-e149-421e-8750-af45c853402f" created="Fri, 4 Oct 2019 18:08:10 +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; - I admit that the Settings pages definitely can be improved. What we use for now is the standard settings component for editing values in reference data. &lt;/p&gt;

&lt;p&gt;Re. the problem with managing long list in Settings, then this is a known problem. I have an old UX story in for that - but only in draft, and it has not really been picked up. The problems we have for Settings &amp;gt; Inventory &amp;gt; Format is not that different from maintaining a list of statistical codes - both have a category/type, and then the values. See 
    &lt;span class=&quot;jira-issue-macro&quot; data-jira-key=&quot;UX-208&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UX-208&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;UX. Filter and look-up feature for searching the Format list (Settings)&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10309?size=medium&quot; /&gt;
            UX-208
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-complete jira-macro-single-issue-export-pdf&quot;&gt;Draft&lt;/span&gt;
            &lt;/span&gt;
. &lt;/p&gt;

&lt;p&gt;For the MVP I think Wayne, and I have mostly been thinking about, that we need a place to migrate this data to. It can be Custom fields - but maybe that then will result in, that all the migrating libraries are doing local solutions, for some very similar data; which soon after MVP, then these elements are to be implemented as a FOLIO defined element. &lt;/p&gt;

&lt;p&gt;But I&apos;m not an expert on User data - so the custom fields might be the right way to solve this &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;&lt;/p&gt;</comment>
                                                            <comment id="13773" author="5c48911b54e1e6466b11f38c" created="Mon, 7 Oct 2019 12:53:05 +0000"  >&lt;p&gt;It sounds like this would be an appropriate topic to bring back to UM, perhaps when Charlotte, Wayne and/or Khalilah can join the call. I&apos;ll defer to &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; and &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ac8ae162b-1267-4990-9205-42958e72b515&quot; class=&quot;user-hover&quot; rel=&quot;557058:c8ae162b-1267-4990-9205-42958e72b515&quot; data-account-id=&quot;557058:c8ae162b-1267-4990-9205-42958e72b515&quot; accountid=&quot;557058:c8ae162b-1267-4990-9205-42958e72b515&quot; rel=&quot;noreferrer&quot;&gt;Maura Byrne&lt;/a&gt; on any of that.&lt;/p&gt;</comment>
                                                            <comment id="13774" author="5c48911b54e1e6466b11f38c" created="Mon, 7 Oct 2019 14:30:23 +0000"  >&lt;p&gt;A colleague here at Duke also reminded me that custom fields to the LDP (&lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-1864&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://folio-org.atlassian.net/browse/UXPROD-1864&lt;/a&gt;) did not make MVP, so that may be enough to say this decision needs to be reassessed as well.&lt;/p&gt;</comment>
                                                            <comment id="13775" author="5c7405f424a84d1307801d06" created="Tue, 8 Oct 2019 13:11:56 +0000"  >&lt;p&gt;I believe that there are some institutions that are loading &apos;alternate&apos; name in their current systems. Is that something they&apos;ll be able to continue if it&apos;s a custom field?  &lt;br/&gt;
Please be aware that the data here may not be a nickname - one important use for this field is to allow gender transitioned and transitioning people to list their preferred name.   I would also very strongly suggest that the label for this field be changed back to &apos;preferred name&apos;.&lt;/p&gt;</comment>
                                                            <comment id="13777" author="5c48911b54e1e6466b11f38c" created="Tue, 8 Oct 2019 13:29:14 +0000"  >&lt;p&gt;Hi &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; - yes, we should be able to import into a custom field if I&apos;m understanding this Jira correctly: &lt;a href=&quot;https://folio-org.atlassian.net/browse/MODCFIELDS-10&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://folio-org.atlassian.net/browse/MODCFIELDS-10&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;And then an individual institution can label it as they deem appropriate.&lt;/p&gt;</comment>
                                                            <comment id="13779" author="62a96ae7192edb006f9f1bf9" created="Tue, 8 Oct 2019 21:09:17 +0000"  >&lt;p&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; and &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 like to split up this feature into two &lt;br/&gt;
1.) New fields: External System ID and Departments &lt;br/&gt;
2.) Update bulk user import with additional user fields &lt;/p&gt;

&lt;p&gt;The reason I request this breakup is it might make it easier to estimate and breakdown work.  &lt;/p&gt;</comment>
                                                            <comment id="10036" author="5f5241b9fcaf93003b5bee25" created="Fri, 11 Oct 2019 16:09:12 +0000"  >&lt;p&gt;I split this into two features and asked Ian Walls to adopt the bulk load stories.&lt;/p&gt;</comment>
                                                            <comment id="10045" author="5c48911b54e1e6466b11f38c" created="Mon, 2 Mar 2020 17:01:16 +0000"  >&lt;p&gt;It looks like departments was split into its own feature (
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;UXPROD-2147&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-2147&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Users App: Department Field&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10322?size=medium&quot; /&gt;
            UXPROD-2147
        &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;
) but I don&apos;t see where the additional external system IDs were split into their own feature. I can see UIU jiras for them but not an UXPROD.  &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; can you advise?&lt;/p&gt;</comment>
                                                            <comment id="10048" author="5f5241b9fcaf93003b5bee25" created="Wed, 11 Mar 2020 18:39:40 +0000"  >&lt;p&gt;here it is &lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-2148&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://folio-org.atlassian.net/browse/UXPROD-2148&lt;/a&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;&lt;/p&gt;</comment>
                                                            <comment id="10051" author="5f5241b9fcaf93003b5bee25" created="Wed, 11 Mar 2020 22:08:13 +0000"  >&lt;p&gt;Split titles and honorifics into own feature &lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-2317&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://folio-org.atlassian.net/browse/UXPROD-2317&lt;/a&gt;&lt;/p&gt;</comment>
                                                            <comment id="10054" author="5f5241b9fcaf93003b5bee25" created="Wed, 27 May 2020 17:52:40 +0000"  >&lt;p&gt;Add Phone type and email validation never ranked high enough for development.&lt;/p&gt;</comment>
                                                            <comment id="10058" author="5f5241b9fcaf93003b5bee25" created="Fri, 16 Oct 2020 15:16:20 +0000"  >&lt;p&gt;Related ticket 
    &lt;span class=&quot;jira-issue-macro&quot; data-jira-key=&quot;UXPROD-2489&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-2489&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Make phone a repeatable field with type labels&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10322?size=medium&quot; /&gt;
            UXPROD-2489
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-complete jira-macro-single-issue-export-pdf&quot;&gt;Draft&lt;/span&gt;
            &lt;/span&gt;
 is specifically for phone number type.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                            <outwardlinks description="blocks">
                                        <issuelink>
            <issuekey id="11781">UXPROD-2062</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="13009">UXPROD-1830</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                            <issuelinktype id="10001">
                    <name>Cloners</name>
                                                                <inwardlinks description="is cloned by">
                                        <issuelink>
            <issuekey id="11258">UXPROD-2147</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10008">
                    <name>Defines</name>
                                            <outwardlinks description="defines">
                                        <issuelink>
            <issuekey id="42103">UIU-256</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="is defined by ">
                                        <issuelink>
            <issuekey id="42028">UIU-1036</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="42035">UIU-1196</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="45278">UIU-1211</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="45290">UIU-1224</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="65155">UICHKOUT-551</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10002">
                    <name>Duplicate</name>
                                                                <inwardlinks description="is duplicated by">
                                        <issuelink>
            <issuekey id="10320">UXPROD-261</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="42036">UIU-1291</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="33498">REP-221</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="67674">MODUSERS-99</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="44945">UIU-696</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="10943">UXPROD-1400</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="10132">UXPROD-850</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10007">
                    <name>Requires</name>
                                            <outwardlinks description="requires">
                                        <issuelink>
            <issuekey id="67553">MODUSERS-159</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="is required by">
                                        <issuelink>
            <issuekey id="11209">UXPROD-2117</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="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>557058:a957226f-df85-4fc8-97f4-8b27a26029ed</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="10187"><![CDATA[Vega]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10014" key="com.pyxis.greenhopper.jira:gh-epic-link">
                        <customfieldname>Epic Link</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue key="$xmlutils.escape($text)">Users App</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10056" key="com.atlassian.jira.plugin.system.customfieldtypes:textarea">
                        <customfieldname>Estimation Notes and Assumptions</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Holly did estimates because we needed to get something set for the capacity plan ASAP and no one else was estimating this feature.</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>557058:a957226f-df85-4fc8-97f4-8b27a26029ed</customfieldvalue>

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

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10063" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>PO Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>106.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10064" key="com.atlassian.jira.plugin.system.customfieldtypes:textarea">
                        <customfieldname>PO Ranking Note</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Even though Users will be making use of custom fields, there are a still few fields where it makes sense to just add them to the data schema.</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                <customfield id="customfield_10019" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i00l92:</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_10066" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: BNCF (MVP Feb 2020)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10198"><![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="10207"><![CDATA[R5]]></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="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_10073" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: FLO (MVP Sum 2020)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10233"><![CDATA[R1]]></customfieldvalue>

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

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                    <customfield id="customfield_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="10258"><![CDATA[R1]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10079" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: Leipzig (Full TBD)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10263"><![CDATA[R1]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10085" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: MO State (MVP June 2020)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="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="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="10248"><![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>Wed, 5 Dec 2018 14:34:21 +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>