[UIQM-512] MARC Bib Templates/Permission Created: 27/Apr/23  Updated: 11/Oct/23

Status: Draft
Project: ui-quick-marc
Components: None
Affects versions: None
Fix versions: None

Type: Story Priority: P3
Reporter: Marcin Mystkowski Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: cataloging, epam-spitfire, front-end, marc-bib
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File image-2023-05-25-14-09-13-522.png    
Issue links:
Relates
relates to UXPROD-3939 Bibliographic Templates Support - MARC Open
Sprint:
Development Team: Spitfire
RCA Group: TBD

 Description   

Permission for managing BIB rec templates. Quite similar to how its organized in Orders:

  • Settings (MARC) : View MARC Bibliographic record templates (user with this permission can view and search through all the templates)
  • Settings (MARC) : View, edit MARC Bibliographic record templates
  • Settings (MARC) : View, edit, create new MARC Bibliographic record templates
  • Settings (MARC) : View, edit, delete MARC Bibliographic record templates

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

User with either of those permission has access to Apps / Settings / MARC / Templates:

  • Bibliographic records templates
  • Holding records templates (in the future -> separate story)

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:

  • quickMARC: Create a new MARC bibliographic record
  • quickMARC: Create a new MARC holdings record
  • quickMARC: Derive new MARC bibliographic record
  • quickMARC: View, edit MARC bibliographic record
  • quickMARC: View, edit MARC holdings record

To sum up - during cataloging process every cataloger can use all templates.
 



 Comments   
Comment by Marcin Mystkowski [ 24/May/23 ]

There is another way to organize permission for creating BIB rec templates . Quite similar to how its organized in Orders:

  1. Settings (Bib Rec.): Can view Bib Rec. Templates
  2. Settings (Bib Rec.): Can view, edit Bib Rec. Templates
  3. Settings (Bib Rec.): Can view, edit, create new Bib Rec. Templates
  4. Settings (Bib Rec.): Can view, edit, delete Bib Rec. Templates 

Permissions are not mutually exclusive. User may have more than one persmission so they are complementary.

There is no Global editor (uber user) permission.

There is no such a idea as template owner 

During cataloging process every cataloger can see and use all templates if he has persmission for cataoging and for usage for this templates

Only user with permission no.4 can delete (all) templates  

Only user with permission no.3 can duplicate templates

Pros: flexibility, transparency, clear and consistens rules with other Folio apps, we do not need build new logic 

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 ?

 

 

Comment by Khalilah Gambrell [ 25/May/23 ]

Hey Marcin Mystkowski 

  • Should there be a permission: quickMARC: Create, view, edit, and delete MARC Bib Rec. Templates?
  • 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. 
Comment by Marcin Mystkowski [ 25/May/23 ]

Hey Khalilah Gambrell 

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

 

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:

  • quickMARC: Create a new MARC bibliographic record
  • quickMARC: Create a new MARC holdings record
  • quickMARC: Derive new MARC bibliographic record
  • quickMARC: View, edit MARC bibliographic record
  • quickMARC: View, edit MARC holdings record

 

Comment by Khalilah Gambrell [ 25/May/23 ]

Hey Marcin Mystkowski  

  1. 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. 
  2. Aligning with Orders template permissions is fine. I noticed that they do not have a permission that allows for all actions  (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. 
Comment by Jacek Gajkiewicz [ 28/Jun/23 ]

Hi Khalilah Gambrell , Marcin Mystkowski

I asked Dennis Bridges why Create and Delete are not put together in orders template permissions. Here is the answer: 

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 “Amazon” template of library 2 for it’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.

The reasons he gave are quite convincing to me, especially the last one.

Generated at Fri Feb 09 00:38:23 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.