Namespace Transition

Requirements

1. Allow users to move or copy a group or set of groups from one stem to another.
2. Allow users to move or copy an entire stem from one stem to another.
3. For moves, optionally allow users to create an alias -- https://wiki.internet2.edu/confluence/display/GrouperWG/Grouper+aliases
4. Expose functionality in Grouper WS.
5. Expose functionality in GSH.
6. Expose functionality in Grouper UI.
7. Expose functionality in Grouper Client.

Design Details

1. For a move, the group and stem UUIDs should remain the same.  However, the name and display name attributes will need to be updated.  The parent stem will also need to be updated for the group or stem being moved. 
2. For a move, validate that the user has admin privileges to all groups and stem privileges to all stems.
3. For a copy, validate that the user has read privileges to all groups.
4. If a group that's moving is a factor of a composite, it should continue to be a factor after the move.  However, if you're copying a group that's a factor of a composite, the new group will not be a factor.
5. For a move, all access privileges, naming privileges, attributes, and custom lists should be moved.  Also, after a group move, populate the name_history attribute of the group with the old group name.
6. For a copy, allow users to choose which memberships, privileges, and custom attributes to copy.  If the group being copied has aliases, those aliases should not be copied.  Also, the name_history attribute should not be copied.
7. LDAP-PC should apply these namespace changes to LDAP in an efficient manner.  I'm not sure how LDAP-PC would currently react to these changes, so that's something that may need to be looked at.