renaming a branch

We're building a new site that will consolidate some existing sites. Those that already exist are in the hs_****_policy branch of TeamSite. We're considering eventually renaming this branch to yyy_officer_div, if possible. Not sure whether you can rename a branch or if you just have to set up a new one...I'm also wondering if you have a way of identifying all individuals who currently have access to the existing hs_****_policy branch by doing a query.

Find more posts tagged with

Comments

Migrateduser

To your last question, it depends on your setup -- the very easiest thing you can do is to set up the new branch and workareas, then populate the workareas by doing a "COPY TO" from the original workarea. This will copy over all files, extended attributes, etc., but you'll need to change applicable configuration files, of course. This is probably the least invasive way.

You COULD be a little fancier and use OpenDeploy to do the job, but that seems like overkill.

Dave

Current Environment(s):
(1) TS 6.1 SP2 on W2K3
(2) TS 6.1 SP2 on W2K

Adam Stoller

You can rename branches, workareas, directories, and files -- about the only thing I don't think you can [easily] rename [at least not through the GUI] is the archive store (i.e. "default")

I don't think there is any OOTB solution for finding all users who have access - you would need to look at the access rights you granted on the branch and on each workarea of the branch to get a sense of all *possible* users who have access.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

indian

What is involved in renaming, or for that matter creating a new on and copying the files into the branch? How does the branch name correspond to the deployed directory, which would give a good estimation of how much modification would be required of each page to correspond to a new location (if the deployed directory structure is effected). What does the "properties" information tell us?

Migrateduser

You can rename the branch straight from the CCPro GUI. You'd need to check for a number of things after doing this, however:

1. The branch's users would need access rights to the renamed branch (which you know already).
2. Any active workflows would be compromised -- the areavpath, attached files, and possibly other job and/or task variables would become different if the branch were renamed.
3. OpenDeploy, DataDeploy, and other applications external to -- but interfacing with -- TeamSite would need to be reconfigured to reflect the renamed branch.
4. Any customizations (extended attributes, FormAPI, workflow scripts, etc.) would need to "know" about the renamed branch.

I'm sure there's more than a few additions to that list, but those are the ones I can think of right now. The "properties" information contains such information about an object as: created and modified timestamps, owner, group, locking information, extended attributes, and status. Depending on what type of object you're referring to (branch, file, workarea, etc.), it might have all or simply a combination of these items. Also, if you were to make a copy of an object using traditional OS methods ("copy" on Windows or "cp" on Unix), not all of these properties would propagate. The most efficient way to copy these files is by using one of the CLT's, as these will recognize the object and backing store for what they are and not treat the object as though it's a regular file or directory, which it is not.

Dave

Current Environment(s):
(1) TS 6.1 SP2 on W2K3
(2) TS 6.1 SP2 on W2K

Michael

What the effects of renaming a branch are in your situation really depends on your unique configuration. You will need to determine the correspondence between a branch name and other parts of the solution including the deployed directory - you can do this by examining some pertinent system doco (hopefully) or perhaps by examining the code and config... (more likely

)

Good luck!

Cheers
Michael.