Grouper Developers Forum

[Chris Hyzer <>]

> -----Original Message-----
> From: Tom Barton 
> [mailto:]
> Sent: Thursday, March 19, 2009 2:36 PM
> To: Chris Hyzer
> Cc: Grouper Dev
> Subject: Re: [grouper-dev] findByName
> 
> Chris Hyzer wrote:
> > As Shilen said in a different email, the user can rename the group to
> > something, and name it back (thus setting the previous name).
> > Allowing to just set the previous name to an arbitrary name (that
> > they have privileges in the folder for), is just a shortcut so
> > Grouper doesn't have to move all those memberships around and back...
> 
> Aside: must memberships be touched when a group is moved? Isn't that
> just a property of the group object - it's still the same group?

Ah yes, that makes sense.

> 
> > Therefore I don't think we need a restore-previous-name command, or a
> > check to see if it was a previous name, since there is a workaround,
> > we are just saving some time...  also I don't think we need an admin
> > only operation since you don't have to be an admin to move a group
> > and move it back, right?
> 
> The group's ADMIN, is the Admin I meant. That would be consistent with
> the existing security model, I think, for protecting a
> restore-previous-name command. Shilen has already detailed the priv
> checking for the other operations.

Right.

> 
> > The only thing that is weird for me, is if you can assign a previous
> > name, and it wasn't a true previous name, should we still call it
> > "previous name".  Im ok with keeping it that way, it is just not
> > precise...
> 
> So let's call it an alias, or an alternate name, and be clear that
> we're
> *not* attempting to nail the problem of minimizing disruption when
> groups and stems are moved around.

Fine with me.

Chris