Skip to Content.
Sympa Menu

grouper-dev - RE: [grouper-dev] findByName

Subject: Grouper Developers Forum

List archive

RE: [grouper-dev] findByName

Chronological Thread 
  • From: Chris Hyzer <>
  • To: Shilen Patel <>, Tom Zeller <>
  • Cc: Grouper Dev <>
  • Subject: RE: [grouper-dev] findByName
  • Date: Thu, 19 Mar 2009 10:48:47 -0400
  • Accept-language: en-US
  • Acceptlanguage: en-US

Cant we just have a group.addPreviousName(name) [which currently replaces the
current one] and group.deletePreviousName(name)? if someone tries to use a
previous name which is removed, then they just add it back. If it is a
question as to whether they know what the name is, cant they look in the logs
to see where the error is occurring? And yes, I think we can assume people
will use auditing, and if they don't want to, we don't need to code around it.

These methods can be callable by GSH, and I can expose them via WS and client
fairly easily with the save group service (in the detail portion)


> -----Original Message-----
> From: Shilen Patel
> [mailto:]
> Sent: Thursday, March 19, 2009 7:56 AM
> To: Tom Zeller
> Cc: Grouper Dev
> Subject: Re: [grouper-dev] findByName
> Based on what I was hearing in previous discussions, this didn't seem
> to be very important. Even though people might stop using the
> previous name, having it remain in the system might not do any harm.
> However, we can add the option to remove it if you think it would be
> useful. But there may be more to consider.
> So say if somebody removes a previous name then realizes that it's
> still being used and so the user wants to add the previous name back.
> How does that get handled?
> One way might be to always populate the previous_name column but also
> have another column (previous_name_searchable) that determines if the
> group can actually be found using the previous name. The new column
> can be turned on and off by admins of the group. But if our future
> method of doing multi-valued attributes won't be able to handle this,
> then we might need a separate table for this data after all.
> Another way might be to let admins of a group add back previous names
> based on audit data if that information is easy to query. But
> everyone might not be using audit.
> Perhaps we just give the user a warning saying that once you remove
> the previous name, you cannot add it back (unless you go directly into
> the database of course).
> Thoughts?
> Thanks!
> -- Shilen
> On Mar 18, 2009, at 4:14 PM, Tom Zeller wrote:
> > Are we also providing a method to remove previous name(s) ?
> >
> > TomZ

Archive powered by MHonArc 2.6.16.

Top of Page