Grouper Users - Open Discussion List

[Tim Darby <>]

That worked, thanks!  It didn't occur to me that the group display
name needed to be a separate query.

Tim

On Fri, Jul 17, 2009 at 9:41 PM, Chris 
Hyzer<>
 wrote:
> Hey,
>
> I think you need to setup your queries a little differently.  Well, first 
> off you need more than one query.  :)
>
> There is the grouperLoaderQuery attribute, which has the query which 
> returns the group_name and subject_id.  Unfortunately the group metadata 
> cannot be specified in that query, if you do, it will be ignored (as you 
> have proven).
>
> The other attribute is: grouperLoaderGroupQuery.  See the description here:
>
> #################################
>
> https://wiki.internet2.edu/confluence/display/GrouperWG/Grouper+-+Loader
>
> grouperLoaderGroupQuery: query (optional) for SQL_GROUP_LIST which should 
> return cols: group_name, group_display_name (optional), group_description 
> (optional) which if there are used for the group display and and extension. 
>  Note: the parent stem display names are only changed when creating them.  
> This should return all groups in the membership list, and if not there, its 
> ok, the extension will be used as display extension, and a generated 
> description. Note: the display name is the display path, with the display 
> extension of each parent stem.  If there is a column named any of the 
> following: readers, viewers, admins, updaters, optins, optouts, then the 
> data in the column (comma separated subjectId's or subjectIdentifers (which 
> can include group names) will be assigned to that privilege list.  Note, 
> existing assignments to that privilege list will not be removed, so if you 
> remove an item from the query, you will need to manually remove it from the 
> groups.  This is a way to have a loaderJob-wide list of readers or viewers.
>
> ##################################
>
> The metadata is loosely coupled from the group list query, since you might 
> want to add a group, and metadata, even if the group has no members.  And 
> it is more normalized that way.
>
> Im looking at the code, and I believe if you add this other query, and run 
> the job, it should update the display names for the groups (so its not only 
> for inserts).  However, parent stems will not be updated by this, might be 
> able to do a generated GSH script from SQL if you need this...
>
> Let me know how it goes.
>
> Thanks,
> Chris
>
>> -----Original Message-----
>> From: 
>> 
>>  
>> [mailto:]
>>  On Behalf Of Tim Darby
>> Sent: Friday, July 17, 2009 11:30 AM
>> To: 
>> 
>> Subject: [grouper-users] group_display_name in loader query
>>
>> Grouper loader is not creating the group display name correctly, so I
>> assume I must have the query wrong.  Instead, it's using the group
>> name as the display name.  Here's my query:
>>
>> select
>> 'arizona.edu:courses:' || a.term_code || ':' || a.course_id || ':' ||
>> a.section_no || ':learner' as group_name,
>> 'University of Arizona:Courses:' || a.term_code || ':' || a.course_id
>> || ':' || a.section_no || ':Learner' as group_display_name
>> b.ua_id as subject_id
>> from.....
>>
>> The group display name is generated as:
>>
>> 'arizona.edu:courses:' || a.term_code || ':' || a.course_id || ':' ||
>> a.section_no || ':learner' as group_name
>>
>> Tim Darby
>> University of Arizona
>
>