Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Various issues
System
Hi Guys :
I am working for a large company with 10K+ users. We have TeamSite in place and it runs on Win2K server. However, we are planning on using TeamSite to manage "Content" and just not web content. That means, we want to store content based on the content categories and then use some mechanism to "Assemble" different pieces of contents together.
For example, we want to have Legal Content in one area to which only folks in legal have access to. Then we want to have a area for business strategy to which only business planning team have access to. Similarly we may have different business areas that have their own folder or branch.
Also every time a content chunk is modified we want it to route through approval chain and then get it submitted to Staging. Please keep in mind that we are not doing this for the web alone. Web is just one channel that would use the content.
Can some of you share some ideas how to build a hierarchy that is scalable and manageable and still secure. Shall we build a branch for every business unit or shall we build folders under a branch and every business unit has a folder.
Also you need to keep in mind that there is another software that we will use to pull everything together. What we plan to do is tag every piece of content that go together and then assemble appropriate content chunks.
Any thoughts and insights would be most helpful.
Thanks
Find more posts tagged with
Comments
sunil_j
Hi Ashish,
A branch with multiple workareas - one for each business uints would be sufficient and appropriate for the said task in hand. The workareas have to be shared with the appropriate business groups and then you can configure an Author-Submit workflow to execute an explicit approval process.
Regards
Sunil