Grouper Developers Forum

[Chris Hyzer <>]

Ok, didn't know that.  I picture existing attributes being replaced post 
1.5... not sure about types and lists... we can explore that later...

> -----Original Message-----
> From: GW Brown, Information Systems and Computing
> [mailto:]
> Sent: Wednesday, July 08, 2009 11:33 AM
> To: Chris Hyzer; Grouper Dev
> Subject: RE: [grouper-dev] Action Items: Grouper Call 24-Jun-09
> 
> --On 08 July 2009 10:17 -0400 Chris Hyzer 
> <>
> wrote:
> 
> >
> >> The difference is that lists are only there if you you define them
> for
> >> a
> >> type and assign the type to a group. Actions are always there and
> are
> >> permission specific - but that just comes back to whether we should
> be
> >> loading attributes in this way.
> >
> > 1. I think lists are global in Grouper.  If you define a list, any
> group
> > can use it (right??)  I didn't think you needed a type on the group
> No, they are part of a type - list vs attribute i.e.
> 
> in QuickStart db:
> 
> select distinct type from grouper_fields ->
> 
> access (internal use - base type)
> attribute
> list
> naming (internal - naming type)
> 
> >
> > 2. Types are only for attribute fields (I thought)
> No
> >
> > 3. You use lists even if you don't define them, the default list is
> the
> > "members" list.  You don't care about this, you just know you don't
> want
> > multiple, that is how the attribute assignment will be.  It will be
> > useful in privileges, and if someone wants to use it for plain old
> > attributes they will be able to.  If you don't need it, pretend like
> it
> > isn't there, just like the "members" list
> Well, a group wouldn't be a group without a list of members...
> >
> > Thanks,
> > Chris
> >
> 
> 
> 
> ----------------------
> GW Brown, Information Systems and Computing
>