grouper-users - RE: [grouper-users] RE: Folder/stem design best practices
Subject: Grouper Users - Open Discussion List
List archive
- From: Chris Hyzer <>
- To: "Klug, Lawrence" <>, Richard James <>, Emily Eisbruch <>
- Cc: "" <>
- Subject: RE: [grouper-users] RE: Folder/stem design best practices
- Date: Tue, 24 Jan 2012 16:21:44 +0000
- Accept-language: en-US
I captured this in a wiki https://spaces.internet2.edu/display/Grouper/Group+and+folder+design+ideas Thanks, Chris From: [mailto:]
On Behalf Of Klug, Lawrence Thanks Emily, Richard and Chris for all the links. Very helpful indeed. Lawrence From: Richard James [mailto:]
Hi, Further to Chris and Emily’s email linking to our video. We also have a couple of documents on our research website for a project that completed last year, they discuss our grouper structure and naming
convention. http://research.ncl.ac.uk/grand/docs/Grouper%20Service.pdf http://research.ncl.ac.uk/grand/docs/Organising%20Groups%20within%20Grouper.pdf Regards Richard James Infrastructure Systems Administrator ISS Systems Architecture Newcastle University From:
On Behalf Of Emily Eisbruch Here are two more links on this topic: - 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): 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: [] On
Behalf Of Klug, Lawrence 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
Internet2 office: +1-734-352-4996 | mobile +1-734-730-5749 Visit our website: www.internet2.edu |
- [grouper-users] Folder/stem design best practices, Klug, Lawrence, 01/23/2012
- [grouper-users] RE: Folder/stem design best practices, Chris Hyzer, 01/23/2012
- [grouper-users] RE: Folder/stem design best practices, Chris Hyzer, 01/23/2012
- Re: [grouper-users] RE: Folder/stem design best practices, Emily Eisbruch, 01/23/2012
- RE: [grouper-users] RE: Folder/stem design best practices, Richard James, 01/24/2012
- Re: [grouper-users] Folder/stem design best practices, Emily Eisbruch, 01/24/2012
- RE: [grouper-users] RE: Folder/stem design best practices, Klug, Lawrence, 01/24/2012
- RE: [grouper-users] RE: Folder/stem design best practices, Chris Hyzer, 01/24/2012
- RE: [grouper-users] RE: Folder/stem design best practices, Richard James, 01/24/2012
- [grouper-users] RE: Folder/stem design best practices, Chris Hyzer, 01/23/2012
Archive powered by MHonArc 2.6.16.