Grouper Users - Open Discussion List

[Wallaert-Taquet Brigitte <>]

Le 16/11/2016 à 21:25, Hyzer, Chris a écrit :

Sorry, lots of confusion… I will be updating the wiki…  J

 

Attributes live in the namespace (in a folder) just like groups and folders.

 

So in the new UI currently you see the gear icon because that attribute definition or name lives in that folder, not assigned to that folder.  You currently need the lite UI to view attribute assignments or assign them.  Having this in the new UI is a work in progress.

Hello,

I view the diagrams on attribute framework and thanks because it help a lot but i have again questions.
I'm wondering to know if the Grouper 2.4 would allow to assign an attribute name with the NewUI ?
So, I'm wondering also to know if our usecase would be better with several AttributeDefinition and several AttributeName instead of one type and its several fields ?

So, I explain our usecase :

Currently, we have one type named "GroupeUdl" and 5 optional fields attached : GroupeUdl ---> optional fields : cn-ldap - nom-liste - type-liste - groupe-sender - date-fin (cf screen type-GroupeUdl.jpg)

Notes : cn-ldap is calculated and then filled with a hook at the creation of each group (group.setAttribute(attrIdLdap, cnValue);) - the 4 others fields are filled with AdminUI  (cf screen fill-fields-type.jpg) - all the fields are displayed with changes in groupHeader.jsp, even if they're not filled (cf screens View-fields-filled.jpg - View-fields-half-filled.jpg)

Tomorrow, with Grouper 2.4, perhaps it would be better to use Attribute Definition and Attribute Name ?

For example with the field "type-liste", we create an Attribute Definition "test-type-liste" (cf screen attributeDefinition.jpg) then, we create several values like "liste interne" and "liste modérée" (cf screens attributName-1.jpg - attributeName-2.jpg). So, with liteUI today, perhaps NewUI tomorrow ?, we can assign one (not needed several here) of thoses attributeNames to a group (see screens attributeName-1-to-group1.jpg - attributeName-2-to-group2.jpg). My idea is ok for you ?

Thanks !

Brigitte

 

My question is, if you are looking at a group in the new UI, and you click on an upcoming “attributes” tab.  You want to be able to assign this attribute and value to certain groups.  You said “We don't need this attribute for every group in Grouper, but it wouldn't bother us it if was there.”  So are there certain folders that groups live in that can get this assignment, or it could be any folder?  Is this a provisioning thing?  Does it use a change log consumer?

 

Thanks

Chris

 

From: Jared Hoffman []
Sent: Wednesday, November 16, 2016 3:06 PM
To: Hyzer, Chris
Cc: Imholz, John J. ; ; Carter Schoenfeld
Subject: Re: [grouper-users] RE: Attribute Framework example

 

The attribute definition and name objects do currently show up in the UI as gear icons.

 

If it was by parent folder, that might be confusing if it applied to sub folders. Looking at the UI, I would assume it would apply at that level and below. 

 

 

 

 

On Wed, Nov 16, 2016 at 2:09 PM, Hyzer, Chris <> wrote:

Just curious… if it were in the UI, how do you know which groups it should show up for?  By parent folder?

 

From: Jared Hoffman [mailto:]
Sent: Wednesday, November 16, 2016 1:39 PM
To: Hyzer, Chris <>
Cc: Imholz, John J. <>; ; Carter Schoenfeld <>

Subject: Re: [grouper-users] RE: Attribute Framework example

 

Our initial confusion was understanding the relationship between attribute definition, attribute name and what the attribute was attached to. As we played with the shell and UI interface we saw where the attributes were stored, but we weren't sure how it all connected.

 

Our use case is to add an ID number to a group to help us link it to another system. Our mistaken assumption was that attributes would appear in the group admin UI like grouper loader settings, like types. So perhaps examples of an attribute use case would help with the concept.  We don't need this attribute for every group in Grouper, but it wouldn't bother us it if was there. 

 

We are not concerned with attribute permissions since we're working only at the admin level, not delegated attributes at this time.

 

 

Any direction would be appreciated.

 

Thanks

 

Jared & Carter

 

 

 

On Mon, Nov 14, 2016 at 10:16 AM, Hyzer, Chris <> wrote:

Maybe we could start by you letting me know which parts of this document are confusing or need more information...

https://spaces.internet2.edu/display/Grouper/Grouper+attribute+framework

Or whatever questions you have and I can update the wiki.

Others welcome to comment too :)

Thanks
Chris

-----Original Message-----
From: Jared Hoffman [mailto:]
Sent: Monday, November 14, 2016 9:52 AM
To: Hyzer, Chris <>
Cc: Imholz, John J. <>;
Subject: Re: [grouper-users] RE: Attribute Framework example

> Hmmm, maybe we need an attribute framework training module.

Yes! Please!

We just stat down to try to figure out the attribute framework (first
time) to place some values we'd like to use when programming
memberships to another system.


Jared


On Tue, May 31, 2016 at 11:31 AM, Hyzer, Chris <> wrote:
> Hmmm, maybe we need an attribute framework training module.
>
> Maybe if you want to lay out your design and run it by the list we could give you comments... :)
>
> Seems straightforward your positions on stems.
>
> Yes, with 2.3 you can create a def, def name, assign, and value.
>
> Before 2.3 you could do everything except the def.  The documentation for the def is not yet there but again ask any questions :)
>
> Ok?
>
> Thanks
> Chris
>
> -----Original Message-----
> From: [mailto:] On Behalf Of Imholz, John J.
> Sent: Tuesday, May 31, 2016 9:19 AM
> To:
> Subject: [grouper-users] Attribute Framework example
>
> Are there other examples (other than https://spaces.internet2.edu/display/Grouper/Grouper+attribute+framework ) of using the attribute framework ?
>
> I'm a little confused with that one (too many parameters seem to be the same or similar.)
>
> I've got an org in version 2.3 and I'd like to assign some "position" attributes to stems.  Stems could have a "state_positions" attribute indicating how many state approved positions are in that org.  Stems could also have a "hospital_positions" indicating how many positions are approved by the hospital.
>
> Can all of this (create def, create def name, assign with value) be done with web services?
>
> jji
>



--
Jared Hoffman • Associate Director for Enterprise Infrastructure
Kenyon College LBIS • • 740.427.5948

 

--

Jared Hoffman • Associate Director for Enterprise Infrastructure

Kenyon College LBIS •  • 740.427.5948

 

 

--

Jared Hoffman • Associate Director for Enterprise Infrastructure

Kenyon College LBIS •  • 740.427.5948

 

--


Brigitte WALLAERT TAQUET
Cheffe de projet GED Nuxeo
Experte Grouper d'Internet2

Université de Lille - Sciences et Technologies
| www.univ-lille1.fr
Service: CRI Bât. M4 - Bureau 34 59655 Villeneuve d'Ascq
Tél. +33 (0)3 20 33 71 65

Attachment: Type-GroupeUdl.jpg
Description: JPEG image

Attachment: View-fields-filled.jpg
Description: JPEG image

Attachment: View-fields-half-filled.jpg
Description: JPEG image

Attachment: fill-fields-type.jpg
Description: JPEG image

Attachment: attributeDefinition.jpg
Description: JPEG image

Attachment: attributeName-1.jpg
Description: JPEG image

Attachment: attributeName-2.jpg
Description: JPEG image

Attachment: attributeName-1-to-group1.jpg
Description: JPEG image

Attachment: attributeName-2-to-group2.jpg
Description: JPEG image

Attachment: smime.p7s
Description: Signature cryptographique S/MIME