Well, this has been done on purpose:
for COMMUNITIES - in
org.dspace.app.xmlui.aspect.administrative.community.EditCommunityMetadataForm:
if (AuthorizeManager.authorizeActionBoolean(context, thisCommunity,
Constants.DELETE))
{
buttonList.addButton("submit_delete").setValue(T_submit_delete);
}
for COLLECTIONS - in
org.dspace.app.xmlui.aspect.administrative.collection.EditCollectionMetadataForm:
//Only System Admins can Delete Collections
if (AuthorizeManager.isAdmin(context))
{
buttonList.addButton("submit_delete").setValue(T_submit_delete);
}
Could somebody explain - why was decided that "Only System Admins can
Delete Collections"?
On Friday, June 24, 2016 at 3:35:03 PM UTC+3, Evgeni Dimitrov wrote:
>
> DSpace 5.4
>
> I have
> - community A
> - in A - subcommunity B
> - in B - collection C
>
> 1. I have an user with "admin" rights on A
> - he can not delete B
> - he can not delete C
>
> 2. I have an user with
> -----"admin" rights on A
> -----"remove" rights on A
> - he can delete B
> - he can not delete C
>
> For one community I need an user who is allowed to do everything (delete
> including) with the lower level subcommunities and collections. How to do
> this?
>
>
--
You received this message because you are subscribed to the Google Groups
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.
