[
http://jira.dspace.org/jira/browse/DS-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Donohue resolved DS-228.
----------------------------
Resolution: Fixed
Fix Version/s: 1.6.0
Assignee: Tim Donohue
This patch has now been committed to DSpace TRUNK in preparation for DSpace
1.6.0 release.
I've also applied the following updates suggested by Andrea Bollini's previous
comments:
1) db sql include RESTRICT constraint, I suggest to remove it so to make the
change more similar to the other schema decision make in DSpace
*This change has been made as suggested.*
2) dspace-api patch use old DatabaseManager method to query (i.e. don't make
properly use of prepared statement and parameter binding)
*This change has been made as suggested.*
3) deleting of a community should not automatically delete the admin group as
we already done with collection
This change was *NOT* made for the following reason: The Community should
auto-delete its own "Administrators" Group. The Collection also auto-deletes
its own "Administrators" group. As these two groups are *different* admin
groups, both calls are necessary, to ensure that those Administrator groups
don't remain in the database even after the Community/Collection was deleted.
4) I have seen that we add to the admin group also other permission (WRITE,
ADD) but this should be not necessary
*This change has been made as suggested.* Creating a Community Admin should
only add the "ADMIN" permission, and need not add the "WRITE" or "ADD"
permission (as it was previously).
5) it has been introduced a useful convenience method groupFromColumn in the
Community class we should find a more appropriate home for it
For now, I've left this "groupFromColumn()" method on the Community object, as
I'm not sure where this is best placed (though I agree with Andrea that it may
be best to pull this out into a more appropriate home).
> 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
