Bug #7695

Setting custom taxonomy delete permissions overrides all taxonomy delete permissions

Added by Dan Gillean almost 7 years ago. Updated almost 6 years ago.

Status:NewStart date:12/11/2014
Priority:MediumDue date:
Assignee:-% Done:

0%

Category:Access Control
Target version:-
Google Code Legacy ID: Tested version:2.1, 2.1.1, 2.2
Sponsored:No Requires documentation:

Description

From the User Forum - reported by Zac @ CNSA: https://groups.google.com/d/msg/ica-atom-users/SaWWeFNbK5s/_Ie-D3qqVqUJ

I'm wondering if other folks have run into problems setting per-taxonomy delete permissions in AtoM? It seems that if I attempt to grant (or deny) delete permissions for a specific taxonomy to a group or user, the system instead sets such delete permission for all terms. Is this expected behavior?

Additionally, if I add more than one specific taxonomy to a user or group's taxonomy permissions, the form name for the delete radios for both are set the same. This especially seems strange to me.

Poor quality screencast demonstrating both of the above: https://www.youtube.com/watch?v=XzqMbpBJDEA

I have tested this issue and reproduced the first behavior in stable/2.1.x. So far, I haven't been able to reproduce the second; the delete radios accidentally linking between different custom taxonomy permissions.

Brief script to reproduce (although Zac's video is way better)

  • Navigate to a user, and add custom taxonomy permissions
  • Add per taxonomy permission - e.g. for Places
  • Set ALL taxonomy delete permissions to "Grant"
  • Set Places taxonomy delete permissions to "Deny"
  • Save

Resulting error

  • All taxonomy delete permissions are set to Deny
  • When multiple per-taxonomy permissions were added (e.g. Places and Subjects), one would revert to "inherit"

See attached screenshots.

taxonomy-edit-permissions.png (34.3 KB) Dan Gillean, 12/11/2014 11:42 AM

taxonomy-saved.png (24.9 KB) Dan Gillean, 12/11/2014 11:42 AM


Related issues

Related to Access to Memory (AtoM) - Bug #8988: Setting custom create permissions per taxonomy not working Verified 09/22/2015
Related to Access to Memory (AtoM) - Bug #12118: Groups will not set permissions from more than 1 archival... Feedback 04/09/2018
Related to Access to Memory (AtoM) - Bug #13205: Adding multiple ACL group taxonomy rules - only last one ... New 10/24/2019

History

#1 Updated by Zachary Howarth-Schueler almost 7 years ago

Screencast shot on http://demo.accesstomemory.org/
Should be reproducible there.

I should have noted, you have to save with permissions multiple specific taxonomies and re-edit for the second behaviour to be seen.

#2 Updated by Dan Gillean almost 7 years ago

Thanks, Zac. I will take a look again to confirm soon. Appreciate the info!

#3 Updated by Dan Gillean about 6 years ago

  • Related to Bug #8988: Setting custom create permissions per taxonomy not working added

#4 Updated by Jesús García Crespo almost 6 years ago

  • Assignee deleted (Jesús García Crespo)

#5 Updated by Dan Gillean about 2 years ago

  • Related to Bug #12118: Groups will not set permissions from more than 1 archival institution for descriptions added

#6 Updated by Dan Gillean about 2 years ago

  • Related to Bug #13205: Adding multiple ACL group taxonomy rules - only last one added applies added

Also available in: Atom PDF