we have a MSSP2010 and I want to use it as a Knowledgebase for many big projects. Each project has a Blog, Contacts, Wiki, etc...
All projects Blogs have entries of the same categories, Contacts of the same categories, Wiki Articles of the same categories, etc...
I would like to create our SharePoint in a way to have all information in one Blog, one Contact List, one Wiki, etc... and then create views that query only the necessary data for this particular view in sub sites. This way each Team can create its own View of the customers situation.
EXAMPLE STRUCTURE
MSSP2010
-KB
--Blog (centralized --> contains all Blog entries of all customers tagged with categories)
--Wiki (centralized)--> contains all Blog entries of all customers tagged with categories)
--...
-Customer View
--Customer A
---Blog with Filter for Customer A
---Wiki with Filter for Customer A
---...
--Customer B
---Blog with Filter for Customer B
---Wiki with Filter for Customer B
---...
-Blog View
--Site with Blog filtered for Category News
--Site with Blog filtered for Category Problems
--....
-Wiki View
--Site with Wiki filtered for Category News
--Site with Wiki filtered for Category Problems
--....
EXAMPLE CATEGORIES:
Customer1 = Ferrari Blog Article Categories = News | Problems | Updates | ...
Customer2 = Lamborghini Blog Article Categories = News | Problems | Updates | ...
I know I can filter for categories with Tags. But I don’t know the following:
How do I create one centralized Blog and show only the filtered result on the corresponding sub site. On the sub site a Blog should look like a Blog and not like a list and a Wiki like a Wiki and not like a list.
I hope I could make myself understandable... sorry for my poor English Which Lists / Sites / ... could I use? Do you have a better approach with the same result?
Please help me with this tricky planning of the architecture of my SP
Thank you BR Steffen
