Grouper Users - Open Discussion List

[Chris Hyzer <>]

Whoops, switch

 

FROM: a top level group in there called “etc”,

TO: a top level folder in there called “etc”,

 

Thanks,

Chris

 

From: [mailto:] On Behalf Of Chris Hyzer
Sent: Monday, January 23, 2012 4:20 PM
To: Klug, Lawrence;
Subject: [grouper-users] RE: Folder/stem design best practices

 

This has been discussed on list before, but I cant seem to find it.  Anyone have a link?

 

Here is this (found by Emily):

 

http://research.ncl.ac.uk/grand/resources/GrouperStructureJan12/GrouperStructureJan12.html

 

At Penn we have two root stems:

 

penn:

 

test:

 

underneath penn: we have “etc”, and every school and center who needs access.  “etc” has groups like which users can get into the UI or WS or are admins etc.  For each school and center we have a top level group in there called “etc”, which has their school/center wide readers, updaters, and admins.  Generally in the school/center folder we have an “apps” folder for that school/center’s apps.  Other schools put the “apps” folder at the top or under their top level folder (in our case “penn”.  Also under “penn” we have “community” which has employees, students, orgs, courses, etc.  Stuff that is generally from the loader and which can be shared among people who need it.

 

Thanks,

Chris

 

From: [mailto:] On Behalf Of Klug, Lawrence
Sent: Monday, January 23, 2012 10:34 AM
To:
Subject: [grouper-users] Folder/stem design best practices

 

We need to come up with a folder/stem design that is appropriate here at UCLA.   We have a four level organizational hierarchy and there will be applications that consume Grouper data for permissions/roles.   Is there any documentation on Folder/stem design best practices?

 

Thanks,

 

Lawrence