desgin branch | workarea

in existing sturcture, we only have 1 branch and 1 workarea.

But we want to secure the files
each department only can access into its own department file

I dont know which's the best way to do
create a branch / sub-brach for each department
or create a workarea for each department

on each department, we are sharing same header and footer file.

--------------------------------------------
TS 6.1 W2K3
OpenDeploy 6.0
CC Pro/Std

Find more posts tagged with

Comments

iwovGraduate

Based on what you said, you should use a separate branch for each department. However I would say that this decision would require a lot more analysis. You might want to read up the white paper on branching structure. Its pretty old, but very useful.

Adam Stoller

There are various ways you can go about this - some of the trade-offs are more important based on the size of each department's content.

One thing NOT to do: have different permissions on files and directories in different workareas on the same branch. This does not work, it goes completely against the model supported by the product, it will cause you no end of pain.

You can set specific access rights on directories and files at the OS-level and, assuming you have some reasonable directory / file naming convention, you can support this in an automated fashion using the submit.cfg file.

If you do that - you still have the choice of whether or not to set up different workareas for each department or use a single shared workarea. If you use separate workareas - remember that each workarea will see ALL the files in that branch - and the access rights on the files and directories within each workarea will be identical. What differs is the access one has to the workarea itself.

If you decide to use separate branches, you may need to deal with iwproxy regex settings to make things appear seamless even though the content (headers, footers, images) may be in a different branch than the one within which you are currently working.

You should probably browse through a bunch of the forum posts and KB articles - and you may want to see if you can track down a copy of Russell Nakano's "Web Content Management - A Collaborative Approach" (you can find reviews of this book online too - both praising it and ridiculing it... but I believe it covers a varieity of ways to break things up within TeamSite and thus might come in valuable for you in this case).

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

cc96ai

Thanks for the information

btw, Can i know where can i find "white paper on branching structure" ?

--------------------------------------------
TS 6.1 W2K3
OpenDeploy 6.0
CC Pro/Std

Migrateduser

Here's one:
http://devnet.interwoven.com/site.fcgi/techlib/049531

Regards,

lissa