Workarea Design issue

baskar

Environment : Teamsite 6.7.1/Solaris 10.

We are designing workarea for a website whose content comes from different departments. Each department will have their own content so department members should not be able to edit the other department content. But most of the templates (dct) for content creation for departments will be same. so we initially thought of creating different workareas named by departments each shared by their department members(workarea shared by group).

But there will be common content like logo and other images,header,footer include html pages etc which will be used by all departments. so everytime common assets needs to be copied to all workares and will lead to replication of same data.Also we feel workareas are not meant to keep different content of website as in this case they contain mainly department html pages & images.

sometimes a department page will have links to other department pages . As content for different departments are in different workareas, it is not possible to access the html pages.(Browse item in DCT have acces to assets only within current workarea).

If we have a single workarea, then the department content can be edited/modified by other department members.Also in workflow, approvers should be based on the content that has been submitted.i.e marketing approvers for content from marketing dept , finance approvers for content from finance etc.so identifying approvers in this case is difficult as all content comes from same workarea.

please provide some suggestions for this scenario.

Adam Stoller

Environment : Teamsite 6.7.1/Solaris 10. We are designing workarea for a website whose content comes from different departments. Each department will have their own content so department members should not be able to edit the other department content. But most of the templates (dct) for content creation for departments will be same. so we initially thought of creating different workareas named by departments each shared by their department members(workarea shared by group). But there will be common content like logo and other images,header,footer include html pages etc which will be used by all departments. so everytime common assets needs to be copied to all workares and will lead to replication of same data.Also we feel workareas are not meant to keep different content of website as in this case they contain mainly department html pages & images. sometimes a department page will have links to other department pages . As content for different departments are in different workareas, it is not possible to access the html pages.(Browse item in DCT have acces to assets only within current workarea). If we have a single workarea, then the department content can be edited/modified by other department members.Also in workflow, approvers should be based on the content that has been submitted.i.e marketing approvers for content from marketing dept , finance approvers for content from finance etc.so identifying approvers in this case is difficult as all content comes from same workarea. please provide some suggestions for this scenario.

Workareas are views onto a branch's contents - they are not independent entities. Attempting to use them as such will cause you no end of problems.

You can use directory structure within a branch, or use sub-branches to separate the different department's contents from one another.

If you use directories - you need to set permissions at the OS level on the files and/or directories that you want to be restricted to one group versus another - but the template will all be shared as common (though you'd need to set up separate sub-directories for the data/ directory with OS-permissions associated so as to prevent users from one department from editing another department's DCRs). Referencing a different department's generated pages could be done through the built-in browser item.

If you use sub-branches, you will want to build your DCTs and PTs dynamically via inline scripts and iw_include statements (respectively) so that you can maintain the code in one place (an Admin branch perhaps) but use them in multiple branches. Referencing a different department's generated pages is more complicated here as you would need to develop your (or borrow someone else's) code for cross-branch browsing (there's code available on this site, but people have had different experiences trying to use it)