Spsatl2013 Introduction to the SharePoint's Social APIs

SPSATL 2013
Intro to SharePoint’s
Social APIs
SHAREPOINT SATURDAY ATLANTA – JUNE 8, 2013
MIKE ORYSZAK
BLOG: WWW.MIKEORYSZAK.COM
TWITTER: @NEXT_CONNECT
LINKEDIN: HTTP://WWW.LINKEDIN.COM/IN/MICHAELORYSZAK

SPSATL 2013
About Me
Senior SharePoint Solution Architect w/ B&R Solutions
Microsoft SharePoint Server MVP
Leader for Triangle SharePoint User Group (TriSPUG)
Dev and Architect with MS stack since 1996
Working with SharePoint since 2002
Raleigh-Durham, NC
Scan the QR code for a
chance to win a prize!
2

3 |SharePoint Saturday Atlanta3 |SharePoint Saturday Atlanta

SPSATL 2013
Session
Overview
Feature Overview
API Options
Examples
Closeout
Target Audience:
Developers looking to leverage or
extend SharePoint’s Social Features.
7

SPSATL 2013
Feature Overview
INTRO TO SHAREPOINT’S SOCIAL APIS
8

SPSATL 2013SPSATL 2013
Feature Overview
Social Platform
MySite Host: Centralized Site Collection that supports
Newsfeed – Functions as a social hub
About Me (Profile) Page – Displays information about the person, their expertise, and social activities
Personal Site: Individual Site Collections that contain
Documents (personal and shared)
Blog
Tasks
Apps
Version Differences:
In 2010
 Newsfeed was pretty light; could not take action on messages
 About Me page less focused on social, more focused on organization
In 2013
 Newsfeed supports replies, likes, mentioning people.
 Newsfeed can function more like a social hub for things you are following. Ex. People, Documents, Sites, Tags
9

Feature Overview
Social Content
Social Content
Conversations
Tags/hashtags
Notes
Ratings
Version Differences:
In 2010 Newsfeed was pretty light; could not take action on messages
In 2013
Newsfeed extended to support conversations including replies, likes, mentioning people.
Newsfeed can function more like a social hub for things you are following. Ex. People, Documents, Sites, Tags
10

SPSATL 2013
API Options
11

Social API Options
Multiple Options for interacting with social data and features.
Ranked in recommended order of preference:
Client Object Model for managed code (.NET, Silverlight, Mobile)
Client Object Model for JavaScript
Rest and OData
Server Object model
Soap based Web Services
12

Social API Options
Client Object Model – Managed
Code
This is Microsoft’s recommended approach
Provides a wrapper for the REST based services
Used within the new SharePoint Apps or non-SharePoint Apps not running for the server
Namespaces:
Microsoft.SharePoint.Client.Social
Core objects for interacting with social feeds, posts, and following data
Microsoft.SharePoint.Client.UserProfiles
Contains objects for interacting with user profiles and attributes
13

Social API Options
Client Object Model – Managed
Code
Differs from Server OM in that it requires a Client Context and cannot hold an open connection
Quick Example – Load a User Profile
string spUrl = "http://serverName/";
string user = "domainNameuserName";
ClientContext context = new ClientContext(spUrl);
PeopleManager peopleManager = new PeopleManager(context);
PersonProperties props = peopleManager.GetPropertiesFor(user);
clientContext.Load(props, p => p.AccountName, p => p.UserProfileProperties);
clientContext.ExecuteQuery();
string email = props.UserProfileProperties["Email"].ToString();
string department = props.UserProfileProperties["Department"].ToString();
14

Social API Options
Client Object Model – JavaScript
Great for client-side customizations inside of SharePoint or externally
This is the equivalent of what was previously accomplished with SPServices
Namespaces:
SP.Sharing (/_layouts/sp.js)
Contains objects for interacting with the sharing features
SP.Social (/_layouts/sp.userprofiles.js)
Core objects for interacting with social feeds, posts, and following data
SP.UserProfiles (/_layouts/sp.userprofiles.js)
Contains objects for interacting with user profiles and attributes
15

Social API Options
Client Object Model – JavaScript
Similar to Client OM in that it requires a Client Context and cannot hold an open connection
var spUrl = "http://serverName/";
var acctName = "domainNameuserName";
var context = new SP.ClientContext(spUrl);
var peopleManager = new SP.UserProfiles.PeopleManager(context);
var profilePropertyNames = ["Email", "Department", “Title”];
var userProperties = new
SP.UserProfiles.UserProfilePropertiesForUser(context, acctName, profilePropertyNames);
var props = peopleManager. getUserProfilePropertiesFor(userProperties);
context.load(userProperties);
context.executeQueryAsync(
function () { "Email:" + alert(props[0] + " | Department: " + props[1] + " | Title: " +
props[2]); }, function () { alert("Error Loading User Profile") });
16

Social API Options
REST and OData
The data is also available directly via the underlying REST services
These can be accessed from any language
REST Endpoints
Social Feed: http://<mySiteUri>/_api/social.feed
Read or write to a user’s social feed
Social Following: http://<mySiteUri>/_api/social.following
Read or write following information
People Manager: http://<siteUri>/_api/SP.UserProfiles.PeopleManager
Read or write user profile information
17

Social API Options
Server Object Model
Full featured, and traditional developers are most comfortable here
Requires deployment through full trust, server solutions
Social Namespaces:
Microsoft.Office.Server.Social: Core objects for interacting with social feeds, posts, and following data
Microsoft.Office.Server.SocialData: Core objects for interacting with social data such as tags and ratings
Microsoft.Office.Server.UserProfiles: Contains objects for interacting with user profiles and attributes
18

Social API Options
Server Object Model
One difference with the Server OM is that it requires a Service Context to connect to the
appropriate User Profile Service Application.
SPContext context = SPContext.Current;
string accountname = "domainNameuserName";
SPServiceContext svcContext = SPServiceContext.GetContext(context.Site);
UserProfileManager profileManager = new UserProfileManager(svcContext);
UserProfile profile = profileManager.GetUserProfile(accountname);
string email = profile["Email"].Value;
19

Social API Options
Soap Based Web Service API
These have officially been deprecated with SharePoint 2013.
Previously released services still available, but no new investment.
Migrate to another API
20

SPSATL 2013
Examples
21

SPSATL 2013
Examples
Demonstration
.NET Client OM
Read Profile Properties
Access Tags/Note Data
Server OM
Read Profile Properties
22

SPSATL 2013
Closeout
24

SPSATL 2013
Questions?
25

Resources
MSDN API References
Choose the right API
http://msdn.microsoft.com/en-us/library/jj164060.aspx
Server Object Model
http://msdn.microsoft.com/en-us/library/jj193040.aspx
Client Object Model
.Net Client: http://msdn.microsoft.com/en-
us/library/jj193046.aspx
Javascript: http://msdn.microsoft.com/en-
us/library/jj193045.aspx
http://msdn.microsoft.com/en-
us/library/microsoft.sharepoint.client.social.aspx
My Social Blog Posts
http://mikeoryszak.com/tag/social/
Sample Projects
A
B
C
LinkPad
 http://www.linqpad.net/
26

 @SPS_ATL #SPSATL
 speaker sponsor

Session Prizes
1 4 $25 gift cards
2 4 $25 gift cards
3 4 $25 gift cards
4 4 $25 gift cards
5 4 $25 gift cards

Spsatl2013 Introduction to the SharePoint's Social APIs

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (18)

Similar to Spsatl2013 Introduction to the SharePoint's Social APIs

Similar to Spsatl2013 Introduction to the SharePoint's Social APIs (20)

More from Michael Oryszak

More from Michael Oryszak (20)

Recently uploaded

Recently uploaded (20)

Spsatl2013 Introduction to the SharePoint's Social APIs

Editor's Notes