The Heat in SharePoint Semantics June 23 to June 28
July 3, 2012
This week, SharePoint Semantics delivered readers some informative posts that are pertinent to the search community. The majority of the posts were related to Microsoft’s recent acquisition of a social networking company for enterprises.
The June 26 post, “SharePoint Joel Riffs on the Happy Pairing of SharePoint and Yammer” showed readers that there’s more to the word yammer than meets the eye. Microsoft, an established tech giant, will be acquiring the enterprise social networking pioneer, Yammer.
SharePoint Joe seems to think that the two will make an excellent pairing. He lists ten reasons for his excitement:
They include that Yammer embraces the cloud, that Yammer will enrich SharePoint’s social strategy, that Yammer can leverage SharePoint’s document repositories, that both integrate well with Dynamics CRM, that Yammer will improve the disappointing SharePoint Discussions, that Yammer Web part profiles will encourage interaction, and that Yammer will improve feedback. Have a look at the official infographic released by both Microsoft and Yammer and included in the article and see if you share the enthusiasm as well.
Another perspective on the same topic comes from the post “Chris Wright Predicts that SharePoint in the Cloud Will Soon OverShadow On Premise.” It emphasizes what this acquisition will mean for the future of SharePoint on premise versus the cloud.
Wright seems to think that there will be a divergence after the initial release:
If the likes of Yammer will only be making a full appearance in SharePoint Online does that not leave us with one product for ‘On Premise’ customers and a potentially very different product for cloud customers? Whilst I would expect some Yammer goodness to appear in the full fat version of SharePoint (Yammer already offers some nice integration options that should now be easy to improve) we do seem to be looking for the first time at a shift in roles, with cloud customers no longer the poor relation.
On a slightly different topic, the post “Understanding Metadata to Enrich Your SharePoint Experience” refers readers to an article that explains how to use document sets, folders, and metadata.
The article states:
It is possible to set default Metadata for every folder in your Document Library. You can set defaults on all of the subfolders from the root, by default this will be inherited…If you have multiple documents that are part of a single project or tasks, you can use a Document Set. With Document Sets you can group, multiple documents and share the Metadata en versioning. In a Document Set you can pass Metadata from the Document Set to the documents in the Document Set.
Regardless of whether or not your interest lies with SharePoint best practices or the future of the company as a whole, it is always a good idea to look into third party solutions that have been proven to work over the years. The Semaphore Content Intelligence Platform from Smartlogic works wonders when it is partnered with SharePoint.
Jasmine Ashton, July 3, 2012