users cannot edit bitstreams of their workspace item

75 views

Skip to first unread message

Franziska Rapp

unread,

Aug 19, 2021, 3:55:34 AM8/19/21

to DSpace Technical Support

Hi,

We have cases where users can no longer edit the bitstream(s) of their workspace item. They can edit the metadata, though.
The error is: "Authorization denied for action REMOVE on BUNDLE:xxxxx by user xx."

When they initially upload their item, they do not have that problem. It occurs with items that were submitted and then rejected.

This happened shortly after we introduced community admins and modified the section in dspace.cfg where the rights for delegate admins are defined. One of the changes was to restrict the create/delete bitstreams permissions for the community admin, collection admin and item admin. We made these changes because in our repository community admins should not create/delete bitstreams of archived items.

# ITEM ADMIN

core.authorization.item-admin.policies = false

# also bundle...

core.authorization.item-admin.create-bitstream = false

core.authorization.item-admin.delete-bitstream = false

core.authorization.item-admin.cc-license = false

Any help would be much appreciated.

Best regards
Franziska

-- 
Franziska Rapp
Communication and Information Center (kiz)
Ulm University

Franziska Rapp

unread,

Aug 23, 2021, 2:15:31 AM8/23/21

to DSpace Technical Support

Hi,

Some addition to my original post: Conceptually I would expect the two things to be unrelated. I would expect delegate admin rights defined in dspace.cfg only apply to users who are delegate admins (e.g. in the community admin or collection admin group). Restrictions in the delegate admin section in dspace.cfg do not apply to other users, it that correct?

I also wonder whether rights are managed differently when a user initially submits an item versus when an item has already been submitted and rejected. I couldn't find information on this in the documentation and would be glad to get some hints and pointers.