Knowledge Sharing
With Omnia, you can establish a solution for structured knowledge sharing within your intranet.
Start off by watching this introductory video.
Here is a summary of the best practice recommendations:
Keep communities open. Anyone in the organization should be able to share their knowledge within a community.
Make sure that every community has at least one moderator. The role of the moderator is to:
Make sure there are some initial relevant content before community launch.
Setup promoted tags in the community and describe how they are going to be used.
Decide on activity points in the community and set up relevant badges.
Spread the word about the community.
Recruit and support community members.
Follow up on the level of activity in the community.
Commitment and adoption is key:
Ensure leadership involvement.
Make sure to focus on knowledge sharing in the internal intranet marketing work.
Make sure you communicate to community members how and why to use rating of content.
Follow-up on the whole knowledge sharing solution using governance features in Omnia such as metrics and surveys.
Make an entry-point for communities and clear navigation to community content:
Set up a Community Portal and navigation to it.
Create a tutorial to help users get started.
Set up a specific search category for community content in Enterprise Search.
Set up the community subscription activity feed in the notification panel.
Follow the steps below to setup a solution based on the recommendations above.
Note
The instruction is based on Omnia 6.8. If you have another version installed, some labels, page types and layouts may differ.
Prerequisites
Go to Omnia Admin > Features (Tenant).
Activate the feature “Default Community Properties and Page Types”.
Go to the Business Profile where you want to deploy communities.
Activate the feature “Default Community Template”.
Refresh the web browser (F5).
EnterPrise Search
Follow these instructions to configure relevant properties and a search category for Communities.
Ensure you have a term set setup for Object Types within your SharePoint term store.
Add the terms “Community Discussion”, “Community Article” and “Community Document”.
Ensure you have an enterprise property setup for Object Type and make it SharePoint Searchable.
Go to Omnia Admin > Page Types and select the page type Discussion.
Add Object Type as a property. Set the default value to “Discussion” and make sure it is hidden from all edit forms.
Repeat steps 9 - 10 for the page types Knowledge Article and Shared Document.
Create a new community.
Start a new discussion.
Grab a cup of coffee and wait for the SharePoint Search to crawl the newly created discussion.
Go to SharePoint admin center > More features > Search.
Find the crawled property ows_taxid_OmniaObjectType and map it to a refinable string.
Find the crawled property ows_SiteName and map it to a refinable string.
Go to Omnia Admin > Properties > Enterprise Properties and update the mapped search settings of the property Object Type.
Create a new Enterprise Property that can be used as a search refiner.
Go to SharePoint admin center > Content services > Term store.
Open the term set Object Types and copy the Unique identifiers for the terms Community Article, Community Discussion and Community Document to Notepad for later use.
Go to Omnia Admin > [Default business profile] > Search.
Create a new search category for Communities.
Use “Local SharePoint Results” as result source and create a search query that gets all objects of type Community Article, Community Discussion and Community Document. (Use the unique identifiers that you copied to Notepad.)
Add the search category to Quick Search and Advanced Search.
Add refiners in Advanced Search: Object Type, Modified, Community.
Notification Panel
Follow the steps below to add the community subscription activity feed to the notifcation panel.
Create a new category for Communities and add the activity feed block.
Configure the activity feed block accordingly.
Community Portal
Follow these steps to setup a community portal.
Create a new Publishing App where the community portal can be hosted.
Create a new Page Collection for the start layout in the community portal.
Go into design mode and start adding sections and blocks.
The “Get Started” action is only needed if you intend to create a tutorial for the community portal.
The “Create Community” action should be set as action type “Create App” and only include community templates.
We recommend that you set up a tabbed section with three different rollups. Sort by Title ascending.
My Communities: Scope “Followed” and “Run query on load”. Add community templates as filter.
New Communities: Scope “All (Public)” and “Run query on load”. Add community templates as filter and Created = “One month from today”. Sort by Created descending.
All Communities: Scope “All (Public)” and “Run query on load”. Add community templates as filter. Sort by Title ascending. Add a search box to the filter.
Set the newly created Page Collection as the default page collection in the Publishing App.
Go to Omnia Admin > Workspace > Navigation Bar and create a link action as an entry-point to the community portal.
To highlight the knowledge sharing solution, we also recommend a banner on the start page, either to the community portal or directly to a newly created community.