Skip to Content.
Sympa Menu

grouper-users - Grouper-WS: Strategies for moving groups/stems?

Subject: Grouper Users - Open Discussion List

List archive

Grouper-WS: Strategies for moving groups/stems?


Chronological Thread 
  • From: Loris Bennett <>
  • To: Grouper Users Mailing List <>
  • Subject: Grouper-WS: Strategies for moving groups/stems?
  • Date: Mon, 13 Oct 2008 15:39:12 +0200

Hi,

On the roadmap the "Namespace Transition Support" is listed. I was
wondering what the status of this is and what strategies people are
using as a workaround. Specifically I am interested in how to deal which
changes in an organizational structure.

Currently I am doing the following:

1. read the organizational structure from a human resources
database
2. construct a corresponding structure of folders in Grouper
using the web services interface
3. add a standard group to each folders
4. read the user data from the HR database
5. add the users to the standard group in the appropriate
folders.

If, say, HR decides to move a group from one unit within a department to
another, that group should remain a member of the department, but should
no longer be a member of any unit-specific groups.

I would envisage doing something like:

1. create new group in the new unit
2. add members of old group to new group
3. determine memberships of old group
4. recreate memberships which need to be preserved
5. add any new memberships required
6. delete all old memberships
7. delete old group

Steps 4 and 5 would require some human interaction regarding what
exactly should be done.

My questions are:

1. Is this the approach that other people are taking?
2. Are there any alternatives?
3. Will "Namespace Transition Support" provide this
functionality?
4. When might NTS be available?

Thanks

Loris

--
Dr. Loris Bennett
Computer Centre
Freie Universit├Ąt Berlin
Berlin, Germany




Archive powered by MHonArc 2.6.16.

Top of Page