[
http://jira.dspace.org/jira/browse/DS-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10367#action_10367
]
Andrea Bollini commented on DS-228:
-----------------------------------
It looks as if not "all" the patch was committed, is it right?
I think that only the xmlui staff related to the move item functionality has
been committed, the "community admin" changes are missed (I have not found the
AssingCommunityRoles Class, etc.)
Please note that I'm currently in holiday until 13th July and I'm using a not
very slow connection so I could to have experienced some "local problems"...
Anyway, I'm currently completing the JSPUI porting and I hope to send the patch
before the end of July
Finally, I have the follow question
the ResourcePolicy API (add and remove with AuthorizeManager) is not enforced
with policy check as it was in my original patch (only object admin should be
able to set policy for an object) - adding this will require caution because
all the points of the system could be affected by the change - but this is
needed to keep the system safe if we allow "local" admin to change policies
> Community Admin XMLUI: Delegated Admins Patch
> ----------------------------------------------
>
> Key: DS-228
> URL: http://jira.dspace.org/jira/browse/DS-228
> Project: DSpace 1.x
> Issue Type: New Feature
> Components: DSpace API, XMLUI
> Affects Versions: 1.6.0
> Reporter: Tim Donohue
> Assignee: Tim Donohue
> Fix For: 1.6.0
>
> Attachments: api-sql-rev1.patch, database_schema_changes.sql,
> dspace-api.patch, dspace-xmlui-api.patch, dspace-xmlui-webapp.patch
>
>
> This set of patches enables Delegated Administration within the XMLUI. These
> patches were made against the latest DSpace trunk code (as of 12-Jun-2009) in
> preparation for DSpace 1.6.
> WARNING: THESE PATCHES MODIFY THE CORE API OF DSPACE. THEY ALSO MODIFY THE
> UNDERLYING DATABASE STRUCTURE SLIGHTLY.
> Essentially, this adds delegated administration capabilities, and allows
> administrative rights to auto-inherit from Community to Collection to Item to
> Bundle to Bitstream. (So, if you are a Community Admin, you can also
> administer any Collection in that Community or any Item owned by those
> Collections).
> This now creates three main levels of Admins:
> * System Admin - same as before, can add/edit/delete anything
> * Community Admin - Can add/edit anything within a specific Community
> (including sub-communites, collections, items)
> * Collection Admin - Can add/edit anything within a specific Collection
> (including all items)
> There are a few administrative functions which are limited to SYSTEM ADMINS
> ONLY:
> * Delete Communities, Collections or Items
> * Withdraw / Reinstate items
> List of tasks a Community Admin can perform:
> * Can create / edit Community, Sub-Communities, Collections or Items
> within the Community
> * Can add/edit/remove Authorizations/Roles for Community, Sub-Communities
> or Collections
> * Can move items from one collection to another (must have submit
> privileges on the destination Collection)
> * Can create/remove item templates for Collections in that Community
> * CANNOT delete Communities, Sub-Communities, Collections or Items (also
> cannot withdraw/reinstate items)
> * CANNOT change the default read access for Collections
> List of tasks a Collection Admin can perform:
> * Can create / edit Collection or Items within that Collection
> * Can add/edit/remove Authorizations/Roles for that Collection
> * Can move items from one collection to another (must have submit
> privileges on the destination Collection)
> * Can create/remove item templates for that Collection
> * CANNOT delete Collection or Items within it (also cannot
> withdraw/reinstate items)
> * CANNOT change the default read access for Collections
> There are some additional bug fixes and features in this patch:
> - Adds ability to Move items between Collections (any Admin can perform)
> - Item Templates now appear properly in XMLUI
> - Previously, they looked just like normal "Edit Item" screen and
> allowed adding bitstreams, etc. (which doesn't make sense as they are just
> metadata templates)
> Even though the DSpace core API changes should work for any user interface,
> these patches only create the necessary interfaces for the XMLUI. Equivalent
> JSPUI interfaces would need to be created to ensure equal functionality
> across both interfaces.
> This patch is based on an older version of the "Authorization System:
> Delegate Admins" patch, originally created by Andrea Bollini.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.dspace.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
