Grouper Users - Open Discussion List

[Emily Eisbruch <>]

Here are two more links on this topic:

https://lists.internet2.edu/sympa/arc/grouper-users/2010-05/msg00015.html

https://lists.internet2.edu/sympa/arc/grouper-users/2010-05/msg00014.html

- Emily

On Jan 23, 2012, at 4:19 PM, Chris Hyzer wrote:

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

 

Emily Eisbruch, Technology Transfer Analyst

Internet2

office: +1-734-352-4996 | mobile +1-734-730-5749

Visit our website: www.internet2.edu
Follow us on Twitter: www.twitter.com/internet2
Become a Fan on Facebook: www.internet2.edu/facebook