Grouper Users - Open Discussion List

[Shilen Patel <>]

Hi,

So the alternate group ID is typically set as the previous group ID when a group is moved or renamed.  The intention was for the API to continue to be able to find the group by its old name to potentially make it easier to transition from one name to another.  So given that, I think the behavior that you're seeing is expected.   Or do you disagree? :)

Thanks!

-- Shilen

From: Gagné Sébastien <>
Date: Mon, 14 Jan 2013 11:21:34 -0500
To: <>
Subject: [grouper-users] Questions about Alternate ID

Hi,

We ran into a “bug” and that made us realise we might have been wrong about how we thought of alternate IDs in Grouper.

 

First, our problem : I tried to automatically create (via GroupSave) a group with the same Name as another’s group Alternate ID. We thought we would get an error for a duplicate group extension (we have a Group Hook to check that), but we didn’t. Digging around I found that in the GroupSave method, it tries to find if the group already exists, but this method check both the current ID and the alternate ID. In this case a modify is detected, the group isn’t created and my logic based on duplicate group ID is bypassed.

 

So how should alternate group ID be treated ? In this case we wanted to keep a trace of where the group was before, but it seems Alternate IDs should be regarded as a copy of the group.

Is the GroupSave wrong to check the Alternate ID ?

 

Right now I did “set alternate ID = false”, to avoid the problem, but I’ll probably have to change my hook to take into account alternate IDs, that would probably be the best solution (albeit a little heavier processing when mass creating groups…)

 

 

Sébastien Gagné,     | Analyste en informatique

514-343-6111 x33844  | Université de Montréal,

                     | Pavillon Roger-Gaudry, local X-100-11