...
[14:04:39 CDT(-0500)] <athena> cool 
[14:14:46 CDT(-0500)] <athena> ok, what do the group mappings look like?
[14:14:53 CDT(-0500)] <athena> is groupName the string name or the id?
[14:15:59 CDT(-0500)] <EricDalquist> ID, GROU_SERVICE, GROUP_NAME
[14:16:15 CDT(-0500)] <EricDalquist> where ID is a synthetic identifier specific to the group mapping table
[14:16:45 CDT(-0500)] <EricDalquist> so like a login event lists all the groups a user is in via the group keys: pags.everyone
[14:17:25 CDT(-0500)] <EricDalquist> during aggregation "pags.everyone" is resolved by the groups API to its actual IEntityGroup
[14:18:12 CDT(-0500)] <EricDalquist> and then a row is found or created for the service "pags" and the name "Everyone"
[14:18:23 CDT(-0500)] <athena> ok
[14:18:28 CDT(-0500)] <EricDalquist> the goal is to de-couple the aggregation data from the actual portal data
[14:18:44 CDT(-0500)] <EricDalquist> so that if someone changes the name of, or deletes, a group
[14:18:51 CDT(-0500)] <EricDalquist> it doesn't break a bunch of already aggregated data
[14:18:53 CDT(-0500)] <athena> makes sense
[17:04:18 CDT(-0500)] <athena> EricDalquist: is there a reason we can't query group mappings by id or is that just an oversight?
[17:04:28 CDT(-0500)] <EricDalquist> just oversight
[17:04:35 CDT(-0500)] <EricDalquist> I only wrote the APIs I needed at the time
[17:06:08 CDT(-0500)] <athena> ok
[17:06:17 CDT(-0500)] <athena> i think we probably need to just hold off for 4.0.6 at this point
[17:06:28 CDT(-0500)] <athena> unless you run into something that delays 4.0.5 another day or two
[17:06:33 CDT(-0500)] <EricDalquist> ok
[17:06:43 CDT(-0500)] <athena> really close though
[17:06:53 CDT(-0500)] <athena> and then we'll have pretty happy graphs
[17:11:26 CDT(-0500)] <mmoayyed> Folks, question on LdapPersonAttributeDao. Do you mind exlaining how the queryAttributeMapping property is used?
[17:12:10 CDT(-0500)] <mmoayyed> I am having trouble understanding how the query wrt to the attr map defined there is generated