Grouper Users - Open Discussion List

["Hyzer, Chris" <>]

I think that suggestion is a good one.  Still lots of ways to do this.

 

Group now has “types” that can mark folders or groups so they can be designated by something other than the folder they are in.

 

https://spaces.at.internet2.edu/display/Grouper/Grouper+types+on+objects

 

But the folder structure is still important…

 

At penn we don’t separate courses into separate school folders since there are so many crosslistings anyways.  We do payroll orgs centrally too

 

At penn we delegate the org folder SchoolOfEngineering, they use that for whatever they want.  For the generic reference groups those might be better placed centrally.  IF the school has reference groups that are loaded, there could be loader jobs there as well if specific to that school.

 

ref:student:courses:<term>:<course>:<section>:…    all courses centrally managed

ref:employee:payrollOrgs:<orgCode>                           all payroll orgs centrally managed

basis:idm:affiliations:<affilCode>                                   all raw affiliations

ref:idm:roles:employee|student|etc                            rollup of raw basis affiliations

ref:org:SchoolOfEngineering:                                          whatever that school wants to do with this folder

ref:org:SchoolOfEngineering:app                                   their apps

 

Thanks

Chris

 

 

From: <> On Behalf Of Jeffrey Williams
Sent: Friday, March 15, 2019 4:39 PM
To: Siju Jacob <>
Cc: Mailing List <>
Subject: Re: [grouper-users] grouper 2.3 folder hierarchy for schools and courses folder

 

Hi Siju,

 

I inherited our Grouper system a few years ago and have been slowly making adjustments to get it more in line with what the deployment guide suggests.

 

 Does it belong directly under root or under orgs or any other folder?    

 

(my $0.02) Bottom of Page 28 ought to get you where you need to be:

The org:
folder is also sometimes used to delineate ownership of applications, and may be used for
organizational scoped or maintained reference groups. The folder structure may replicate the
top-level folder structure, but will be scoped to the particular organization.

 

One way to slice it would be to organize your schools under org: (e.g. Rutgers:SchoolOfEngineering, Rutgers:SchoolOfArtsAndSciences, etc) and replicate at least some part of the top-level structure under that.  I'd say etc: and ref: at minimum.  The schools' ref:(p26) would house student, course, and dept. groups scoped to that particular school.  e.g.

 

Rutgers:SchoolOfEngineering:ref:course: - course rosters including instructors, TAs, etc

Rutgers:SchoolOfEngineering:ref:dept: - organization hierarchies

Rutgers:SchoolOfEngineering:ref:student: - types of students (class year, on-track-grad, incoming-class...)

 

That's my read on it.  Any others?

 

On Fri, Mar 15, 2019 at 3:25 PM Siju Jacob <> wrote:

Hi Team,

               We want to create the groups for schools in the university. We are keeping our staffs under org groups within the org folder.

    We want to keep the students based on each school name groups with in schools folder.

   It’s not clear to me from TIER document where the schools folder will belong to.

   Can someone guide me where will the schools folder belong as per the standards followed by grouper community.

  Does it belong directly under root or under orgs or any other folder?

      Also we want to create groups based on courses. Where will the groups named on each course belong to as per the grouper standard hierarchy.

     Any advice or guidance will be of great help and would be greatly appreciated..!

 

Thanks,

Siju Jacob

 

--

Jeffrey Williams 

Identity Engineer
Identity & Access Services
https://its.uncg.edu