Hi Glen,

I don't have an answer but I'll recount my own experience if you don't
mind. I did what you described, I added a group called cataloguers to
the workflow step for all collections, albeit I had to do it
programmatically because of the restrictions imposed by the UI that you
have described. At a later date I then wanted to delete certain
collections and couldn't do so because the code tried to delete
associated groups. The code expected the groups to be uniquely
associated with the collection. So, I concluded that yes I should have
done what you described and added my cataloguers groups into all the
COLLECTION_NN_xxx groups. Its messy, but its seems that's what the code
expects at this point in time.

Cheers, Robin.


On Tue, 2011-02-15 at 02:10 +0000, Glenn Little wrote:
> I'm using the xmlui interface (both Reference and Mirage).  The only
> way I can find to add a group to, say, admin a collection is to edit
> that collection (or community) and on the "Assign Roles" tab, do a
> "Create" under whichever category I want.
> 
> But why does that create a group where the name is hard-coded to be
> something like COLLECTION_34_ADMIN, with no way to edit that?
> 
> And say I had one group in particular that I wanted to give admin
> rights to for 7 out of a set of 10 sibling collections?  Do I have to
> create a COLLECTION_NN_ADMIN group for each, then create my own group
> and add it to each of those COLLLECTION_NN_ADMIN groups?
> 
> How do you avoid the group list getting all cluttered up?
> 
> Thanks...
> 
> -glenn
> 
> ------------------------------------------------------------------------------
> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
> Pinpoint memory and threading errors before they happen.
> Find and fix more than 250 security defects in the development cycle.
> Locate bottlenecks in serial and parallel code that limit performance.
> http://p.sf.net/sfu/intel-dev2devfeb
> _______________________________________________
> DSpace-tech mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/dspace-tech



------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Reply via email to