Keep them close: Telligent and SharePoint
When planning a strategy to take advantage of Telligent and SharePoint, try to make sure to keep latency between the servers as low as possible.
Find a place for Social
Establish a strategy to place Telligent WebPart in higher-traffic areas of your current SharePoint deployment. Expand your strategy as needed as social community grows. For the quick launch menu, it is recommended to enable the “SharePoint Integration for Telligent Evolution 2.0” feature found in the Manage site features menu.
User to user: Match user names and emails
Allow for SharePoint Administrators and Telligent Administrators to make sure that user names and emails match on both systems. When comparing user names, it isn't necessary to have the domain name prefixed in Telligent. In other words, these examples are equal: SharePoint user “corp\user1” and Telligent “user1”.
Same service account
When creating service accounts for Telligent and SharePoint, it is a good idea to make sure the user names and passwords match.
Group to site partnerships
It is recommended for SharePoint sites to have unique titles. When partnering with a site from Telligent in the SharePoint Group Partnerships widget, the type-ahead options will have what seems like duplicate items but are really two different sites.
Understanding managed metadata in SharePoint
A good article to get started with Metadata can be found here. It describes ways to set up terms and term sets to support a corporate taxonomy.
Currently, our integrations do not leverage the MMS (Managed Metadata Service), although we are always looking to increase the value of what we offer to increase and expand our reach into the SharePoint environment.