Grouper Users - Open Discussion List

["William G. Thompson, Jr." <>]

LDAP is often handy as a starting place for reference groups, as it
tends to have interesting data backed by processes that keep it
reasonably up to date. In this case however, I think I'd see if we
couldn't get that value unpacked by the update process and have it
maintain a few RDMBS tables that could be used by the loader jobs...or
better yet if possible, craft some new database views directly on the
source.

On Fri, Mar 31, 2017 at 1:12 PM, Liam Hoekenga 
<>
 wrote:
> We have a couple of "packed" attributes in our LDAP source - basically a
> string representation of object... a single attribute containing data useful
> for creating several different "reference" groups, e.g.
>
> {jobCategory=Staff}:{campus=ANN-ARBOR}:{deptId=111111}:{deptGroup=COLLEGE_OF_ART}:{deptDescription=Wicker
> Baskets}:{deptGroupDescription=Container Based Art
> Forms}:{deptVPArea=VP_CONTAINER_AFFAIRS}:{jobcode=222222}:{jobFamily=333}:{emplStatus=A}:{regTemp=R}:{supervisorId=44444444}:{tenureStatus=NA}:{jobIndicator=P}
>
> I was hoping to get some advice on processing them economically.
>
> Is there a way to retrieve this data once and explode it into multiple
> attribute based groups in one fell swoop?  (Maybe using the hook mechanism?)
>
> Or would we need to define a bunch of attribute based groups that looked at
> a piece of the data and did something with it?
>
> Liam
>