On Aug 29, 2008, at 4:07 PM, Mark Diggory wrote:
> Its come to my attention recently that the "Collection Administrator"
> rights differ between the JSPUI and the XMLUI (thank you Claudia).
> More specifically it is the following case.
> JSPUI CA can:
> 1.) Add/Remove submitters
> 2.) Map Items to the collection
Actually, strike (2), Collection Admins do not have sufficient
permissions to Map or Submit Items to the collection unless they are
also added to the Submitters role. This state is created in both the
JSPUI and XMLUI on collection creation.
> 3.) Edit Collection Metadata
> XMLUI CA can only:
> 1.) Edit Collection Metadata
> We need a clear fix for these differences, it appears to require
> working on the cocoon flow-script as well as those classes within the
> administration aspect. Though I understand the classes, I do not
> fully understand the flow script, is there a developer that can spend
> some cycles assisting us in coming up with a solution for this?
> Finally, to allow both Collection Administrators to "Map" Items and
> for Workflow Steps to Complete their processes, its clear that they
> need to either (a) be members of the submitters group, or (b) have
> permissions to Add to the collection "permute" to those roles as
> well, right now this is not the case and these roles can not
> currently complete their required tasks XMLUI. It appears that the
> JSPUI treats the Collection Administrator as a Submitter, how might
> we approach this with the XMLUI?
> Mark R. Diggory - DSpace Developer and Systems Manager
> MIT Libraries, Systems and Technology Services
> Massachusetts Institute of Technology
> Home Page: http://purl.org/net/mdiggory/homepage
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> Build the coolest Linux based applications with Moblin SDK & win
> great prizes
> Grand prize is a trip for two to an Open Source event anywhere in
> the world
> Dspace-devel mailing list