Share, Follow, and Sync: How SharePoint 2013 uses Personal MySites for Social functionality
•
2 likes•1,831 views
SharePoint 2013 uses MySites to enable social functionality. MySites provide each user with a personal profile page and content storage. Users can follow other users, sites, documents and tags, which are then aggregated on their MySite. Content can be shared with others who request access. Tasks and documents can be synced to Outlook and mobile devices, though syncing has stability issues. Yammer integration is supported through apps rather than the built-in social features.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Share, Follow, and Sync: How SharePoint 2013 uses Personal MySites for Social functionality
Similar to Share, Follow, and Sync: How SharePoint 2013 uses Personal MySites for Social functionality (20)
Recently uploaded
Recently uploaded (20)
Share, Follow, and Sync: How SharePoint 2013 uses Personal MySites for Social functionality
- 1. How SharePoint 2013 uses MySites for Social Functionality
- 2. Paul Papanek Stork • Principal SharePoint Architect for BlueChip Consulting Group • http://www.bluechip-llc.com • SharePoint MVP for 7 years • SharePoint Microsoft Certified Master • Author • Developer’s Guide to WSS 3.0 • MOSS 2007 Best Practices • MCTS: WSS 3.0 Configuration Study Guide (70-631) • SharePoint 2010 Development for Office 365 • Contact Information • Email: Paul.Stork@bluechip-llc.com • Blog: http://dontPaPanic.com/blog • Twitter: @PStork
- 3. Agenda • Overview of SharePoint 2013 Social • A Brief Tour of MySites • Sharing Sites and Documents • Following Sites, Documents, People, and Tags • Sync • Yammer
- 4. What’s New in 2013 Social • Community Site Template • Redesigned Newsfeed and Microblogging • Easier Content Sharing • Better Aggregation of Tasks • Easier Bookmarking of Sites and Documents Many of these New Features Require a Personal MySite
- 5. Brief Tour of MySites • Same Basic Structure as SP 2010 • Shared MySite Host • Displays Profile for User Properties • Newsfeed • Individual MySites for each User • Per User Storage • Links to Followed Sites • Links to Followed Documents • Aggregation of Your Tasks
- 7. Share Content with Others • Same Permissions Infrastructure • Share Breaks Inheritance Automatically • Individual ACL limits raised (50,000 per list) • Uses the Access Request Feature • Disabling Sharing • Can’t disable Share Links • Turning off Access Request results in Error • O365 Alternative – Members can Share setting • Lists work like SP 2010
- 8. Sharing a Site • A User fills out Sharing Dialog • Decides Whether to Send Email • Optionally chooses what group/permission level • An Access Request is Generated • Access Request for Approved • Email Generated to Original Recipient
- 10. Sharing a Document • A User fills out Sharing Dialog • Decides Whether to Send Email • Optionally chooses what group/permission level • An Access Request is Generated - and - • Email Generated to Original Recipient • Access Denied if Recipient Accesses Document • Access Request Approved • Recipient can Open Document
- 12. Follow • Four Types of Things can be Followed • People – Colleagues in 2010 • Sites • Documents • #Tags – Created through Microblogging Note: #Tags are not the same as Tags and Notes
- 13. Follow Site or Document • Creates Link to Site or Document in personal MySite • Suggestions Provided in Personal MySite • Follow Links can be easily removed • Web Feature to Enable/Disable Following Documents or Sites
- 14. Follow People • Can be Disabled in User Profile Permissions • Newsfeed is the Primary Use • Reference others in Microblogging using ‘@name’
- 15. Follow #Tags • #Tags created Primarily in Microblogging and Community Sites • #Tags stored in Managed Metadata Service • Trending #Tags displayed in MySite Host
- 16. Newsfeed (Microblogging) • Includes Microblogging and generated activity • Site specific activity stored in site content database • User specific activity stored in personal MySite
- 18. Sync Libraries • Sync Libraries to Local PC • OneDrive limit 20,000 files • Library limit 5,000 files • Sync Currently has Stability Issues • Turn it OFF • Site Settings > Search > Search and offline availability • PowerShell Get-SPSite -limit all | get-SPWeb -limit all | Foreach { $_.Title = $_.Title; $_.ExcludeFromOfflineClient=1; $_.Update() }
- 19. OneDrive for Business • OneDrive for Business ≠ OneDrive • OneDrive for Business = Personal My Site Library • Multiple clients available • Client installed with Office 2013 or Office Pro Plus (O365) • OneDrive for Business Sync Client http://support.microsoft.com/kb/2903984 • OneDrive for Business App (Windows 8 or Windows phone)
- 20. Sync Tasks • Sync Tasks to Outlook • With Exchange 2013 • Requires SSL • Requires Exchange Web Extensions • With Exchange 2010 • Turn Off Farm Level Feature - • Sync Tasks to Personal MySite • Uses Search and Work Management Service • Doesn’t Require Exchange 2013 • Removed from Office 365
- 22. Yammer Integration • Remove Webparts from MySite Host • Newsfeed • Followed Counts • Trending Tags • Remove Site Feed Webpart on Team Sites • Add CSS changes to hide Social Links • Do NOT hand edit the CoreV15.css file • Override specific styles by deploying your own CSS file using a feature • Install the Yammer home feed APP part on your My Site Host
- 24. Additional Resources • Configure Exchange 2013 for Task Sync http://technet.microsoft.com/en-us/library/jj554516.aspx • What's new in social computing in SharePoint Server 2013 http://technet.microsoft.com/en-us/library/jj219766.aspx • Advancing the enterprise social roadmap http://blogs.office.com/b/sharepoint/archive/2013/06/24/advancing- the-enterprise-social-roadmap-june-2013.aspx • Integrate Yammer with on-premises SP 2013 http://technet.microsoft.com/en-us/library/dn270535.aspx
- 25. Contact Information Email: Paul.Stork@bluechip-llc.com Blog: http://dontPaPanic.com/blog Twitter: @PStork
Editor's Notes
- Individual ACLs now 50,000 per list – see Boundaries and Limits (http://technet.microsoft.com/en-us/library/cc262787.aspx)
- A very effective and easy way is to store the css files either in the file system or in the style library(I vote for the first one). First create a css file with the style definitions you want and save it in the structure in Visual Studio of a SharePoint Project. The files could either be copied to SharePoint root or to a SharePoint library on deployment. Then create a user control which you deploy to the controltemplates/Projectname. In that user control you add the references to your css files add possible javascript files. Create a delegate control that puts your user control in the AdditionalPageHead on the master page. Create a feature for your delegate control that will activate your css.