<!-- 
RSS generated by JIRA (1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d) at Fri Feb 09 00:38: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>[UIQM-512] MARC Bib Templates/Permission</title>
                <link>https://folio-org.atlassian.net/browse/UIQM-512</link>
                <project id="10150" key="UIQM">ui-quick-marc</project>
                    <description>&lt;p&gt;Permission for managing BIB rec templates. Quite similar to how its organized in Orders:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Settings (MARC) : View MARC Bibliographic record templates (user with this permission can view and search through all the templates)&lt;/li&gt;
	&lt;li&gt;Settings (MARC) : View, edit MARC Bibliographic record templates&lt;/li&gt;
	&lt;li&gt;Settings (MARC) : View, edit, create new MARC Bibliographic record templates&lt;/li&gt;
	&lt;li&gt;Settings (MARC) : View, edit, delete MARC Bibliographic record templates&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Permissions are not mutually exclusive. User may have more than one permission so they are complementary.&lt;br/&gt;
Only user with permission no. 4 can delete (all) templates&lt;br/&gt;
Only user with permission no. 3 can create a template (from scratch/by duplicating a template/by deriving from existing MARC bib. rec.)&lt;/p&gt;

&lt;p&gt;User with either of those permission has access to Apps / Settings / MARC / Templates:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Bibliographic records templates&lt;/li&gt;
	&lt;li&gt;Holding records templates (in the future -&amp;gt; separate story)&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;NOTE! We are not adding a separete permission for ability to create a New MARC bib record from a template. User with any of the following permissions can use templates:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;quickMARC: Create a new MARC bibliographic record&lt;/li&gt;
	&lt;li&gt;quickMARC: Create a new MARC holdings record&lt;/li&gt;
	&lt;li&gt;quickMARC: Derive new MARC bibliographic record&lt;/li&gt;
	&lt;li&gt;quickMARC: View, edit MARC bibliographic record&lt;/li&gt;
	&lt;li&gt;quickMARC: View, edit MARC holdings record&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;To sum up - during cataloging process &lt;b&gt;every cataloger can use all templates&lt;/b&gt;.&lt;br/&gt;
&#160;&lt;/p&gt;</description>
                <environment></environment>
        <key id="64133">UIQM-512</key>
            <summary>MARC Bib Templates/Permission</summary>
                <type id="10005" iconUrl="https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10309?size=medium">Story</type>
                                            <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="-1">Unassigned</assignee>
                                                                <reporter accountid="557058:7d83f466-4e5c-4751-98ea-136a9a039622">Marcin Mystkowski</reporter>
                                    <labels>
                            <label>cataloging</label>
                            <label>epam-spitfire</label>
                            <label>front-end</label>
                            <label>marc-bib</label>
                    </labels>
                <created>Thu, 27 Apr 2023 07:17:55 +0000</created>
                <updated>Wed, 11 Oct 2023 00:25:45 +0000</updated>
                                                                                <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                <comments>
                                                            <comment id="156004" author="557058:7d83f466-4e5c-4751-98ea-136a9a039622" created="Wed, 24 May 2023 06:59:14 +0000"  >&lt;p&gt;There is another way to organize permission for creating BIB rec templates . Quite similar to how its organized in Orders:&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;Settings (Bib Rec.): Can view Bib Rec. Templates&lt;/li&gt;
	&lt;li&gt;Settings (Bib Rec.): Can view, edit Bib Rec. Templates&lt;/li&gt;
	&lt;li&gt;Settings (Bib Rec.): Can view, edit, create new Bib Rec. Templates&lt;/li&gt;
	&lt;li&gt;Settings (Bib Rec.): Can view, edit, delete Bib Rec. Templates&#160;&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;Permissions are not mutually exclusive. User may have more than one persmission so they are complementary.&lt;/p&gt;

&lt;p&gt;There is no Global editor (uber user) permission.&lt;/p&gt;

&lt;p&gt;There is no such a idea as template owner&#160;&lt;/p&gt;

&lt;p&gt;During cataloging process every cataloger can see and use all templates if he has persmission for cataoging and for usage for this templates&lt;/p&gt;

&lt;p&gt;Only user with permission no.4 can delete (all) templates&#160;&#160;&lt;/p&gt;

&lt;p&gt;Only user with permission no.3 can duplicate templates&lt;/p&gt;

&lt;p&gt;Pros: flexibility, transparency, clear and consistens rules with other Folio apps, we do not need build new logic&#160;&lt;/p&gt;

&lt;p&gt;Cons: I am not sure but I feel that this kind of permission will couse much more templates, wich in fact is much more messy - but it is only a (unjustified) feeling ? Others cons ?&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;</comment>
                                                            <comment id="156005" author="62a96ae7192edb006f9f1bf9" created="Thu, 25 May 2023 11:36:47 +0000"  >&lt;p&gt;Hey &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A7d83f466-4e5c-4751-98ea-136a9a039622&quot; class=&quot;user-hover&quot; rel=&quot;557058:7d83f466-4e5c-4751-98ea-136a9a039622&quot; data-account-id=&quot;557058:7d83f466-4e5c-4751-98ea-136a9a039622&quot; accountid=&quot;557058:7d83f466-4e5c-4751-98ea-136a9a039622&quot; rel=&quot;noreferrer&quot;&gt;Marcin Mystkowski&lt;/a&gt;&#160;&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Should there be a permission: quickMARC: &lt;b&gt;Create&lt;/b&gt;, view, edit, and delete MARC Bib Rec. Templates?&lt;/li&gt;
	&lt;li&gt;Also I agree you should not have another permission to create a MARC bib from a template but we should make sure that there is a scenario to validate that if the user has the ability to create MARC bib then they have the ability to create a MARC bib from a list of templates.&#160;&lt;/li&gt;
&lt;/ul&gt;
</comment>
                                                            <comment id="156006" author="557058:7d83f466-4e5c-4751-98ea-136a9a039622" created="Thu, 25 May 2023 12:10:43 +0000"  >&lt;p&gt;Hey &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;&#160;&lt;/p&gt;

&lt;p&gt;I did several tests with templates for orders, and with permissions for templates for orders&#160; So proposal is excatly the same as in orders. I realized that if user have got #3 and #4 then have got full permission:&lt;/p&gt;

&lt;p&gt;&lt;span class=&quot;image-wrap&quot; style=&quot;&quot;&gt;&lt;img src=&quot;/rest/api/3/attachment/content/49910&quot; height=&quot;463&quot; width=&quot;810&quot; style=&quot;border: 0px solid black&quot; /&gt;&lt;/span&gt;&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;NOTE! We are not adding a separete permission for ability to create a New MARC bib record from a template. User with any of the following permissions can use templates:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;quickMARC: Create a new MARC bibliographic record&lt;/li&gt;
	&lt;li&gt;quickMARC: Create a new MARC holdings record&lt;/li&gt;
	&lt;li&gt;quickMARC: Derive new MARC bibliographic record&lt;/li&gt;
	&lt;li&gt;quickMARC: View, edit MARC bibliographic record&lt;/li&gt;
	&lt;li&gt;quickMARC: View, edit MARC holdings record&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;&#160;&lt;/p&gt;</comment>
                                                            <comment id="156007" author="62a96ae7192edb006f9f1bf9" created="Thu, 25 May 2023 12:18:25 +0000"  >&lt;p&gt;Hey &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A7d83f466-4e5c-4751-98ea-136a9a039622&quot; class=&quot;user-hover&quot; rel=&quot;557058:7d83f466-4e5c-4751-98ea-136a9a039622&quot; data-account-id=&quot;557058:7d83f466-4e5c-4751-98ea-136a9a039622&quot; accountid=&quot;557058:7d83f466-4e5c-4751-98ea-136a9a039622&quot; rel=&quot;noreferrer&quot;&gt;Marcin Mystkowski&lt;/a&gt; &#160;&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;I agree about not adding a separate permission for ability to create a New MARC bib record from a template. User with any of the following permissions can use templates.&#160;&lt;/li&gt;
	&lt;li&gt;Aligning with Orders template permissions is fine. I noticed that they do not have a permission that allows for all actions&#160; (Create, Edit, View, and Delete) so it seems that a person must be assigned two permissions in order to get Delete action permission. So I was only pointing it out in case we want to find out why they did it this way.&#160;&lt;/li&gt;
&lt;/ol&gt;
</comment>
                                                            <comment id="156008" author="557058:80d140c2-f918-47a8-baea-bff889a4e1d0" created="Wed, 28 Jun 2023 07:41:39 +0000"  >&lt;p&gt;Hi &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;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A7d83f466-4e5c-4751-98ea-136a9a039622&quot; class=&quot;user-hover&quot; rel=&quot;557058:7d83f466-4e5c-4751-98ea-136a9a039622&quot; data-account-id=&quot;557058:7d83f466-4e5c-4751-98ea-136a9a039622&quot; accountid=&quot;557058:7d83f466-4e5c-4751-98ea-136a9a039622&quot; rel=&quot;noreferrer&quot;&gt;Marcin Mystkowski&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I asked &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A2f7b6349-450b-419a-ba54-c181f51383ad&quot; class=&quot;user-hover&quot; rel=&quot;557058:2f7b6349-450b-419a-ba54-c181f51383ad&quot; data-account-id=&quot;557058:2f7b6349-450b-419a-ba54-c181f51383ad&quot; accountid=&quot;557058:2f7b6349-450b-419a-ba54-c181f51383ad&quot; rel=&quot;noreferrer&quot;&gt;Dennis Bridges&lt;/a&gt; why Create and Delete are not put together in orders template permissions. Here is the answer:&#160;&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;This was done in order to allow for more tightly controlled deletion of templates. Some of our current FOLIO implementations are made up of multiple institutions in one tenant. In these cases it is possibile for a user from library 1 to mistake the &#8220;Amazon&#8221; template of library 2 for it&#8217;s own template etc. It is an edge case perhaps but the reason why we separated create and delete. It also allows lower permissioned users to be able to create templates that perhaps only they themselves would use.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;The reasons he gave are quite convincing to me, especially the last one.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="12704">UXPROD-3939</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="49910" name="image-2023-05-25-14-09-13-522.png" size="189640" author="557058:7d83f466-4e5c-4751-98ea-136a9a039622" created="Thu, 25 May 2023 12:09:14 +0000"/>
                    </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_10057" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Development Team</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10180"><![CDATA[Spitfire]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10063" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>PO Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                    <customfield id="customfield_10106" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>RCA Group</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10367"><![CDATA[TBD]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10019" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|hzx1ni:00010090003900i2901io200i0000300090005js</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>Thu, 25 May 2023 11:36:47 +0000</customfieldvalue>

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