Basic features comparison for end user prospective.
Business Scenario
|
SharePoint
2010
|
SharePoint
2013
|
Document Collaboration
|
·
Support for enterprise content
types and shared metadata so that attributes and structures can be maintained
in one place and shared across the enterprise, vastly improving search
results.
|
·
No difference in
approach for organizing content so investment in defining content types and
metadata is fully leveraged in 2013.
·
Several helpful
user experience improvements in the application of metadata, including the
ability to edit managed metadata in a datasheet (spreadsheet) view.
·
“Drag and drop”
ability to upload documents to SharePoint libraries (without having to open
library in “explorer view’).
|
Search
|
·
Comprehensive
enterprise search with the ability to use Boolean operators to create search
queries. For example: search for: cats AND dogs.
·
Wildcard search
available. For example, as search for ho* would find homes, horses, houses,
etc.
·
Faceted search
refiners to easily narrow results based on metadata.
·
Define search
scopes to target to specific collections of content.
·
“Best bets” can
be defined to force certain results to the top of search results.
|
·
Significant
improvements in user experience.
·
Visual display of
contents as you hovers in search results.
·
Best bets now
called Promoted Results.
·
Search remembers
what you have previously searched and clicked and displays these values as
query suggestions at the top of the results page.
·
Results show
number of times a document has been viewed.
·
Results pages
allow you to page through PowerPoint presentations without leaving the search
results page.
·
One clicks to
“view in library.”
|
Expertise Location
|
·
Support for user
profile – both standard and custom attributes
·
People are
searchable – and search can be scoped to people
·
Users define core
areas of expertise in the “Ask me about” column.
|
·
Default people
search displays most recent documents authored by that user
·
Follow people to
see updates based on their Newsfeed posts and what they are publishing
|
Social Computing
|
·
Very limited
capabilities.
·
Users can post a
single status that is not retained and not searchable.
·
New status wipes
out the old status so statuses feel very static.
|
·
Each user has a
Newsfeed that is similar to a Facebook activity stream.
·
See stream of the
entire organization or filter based on topics and people you are following.
·
Post or reply in
the stream using @mentions and #hashtags.
·
Activity posts
are saved for as long as you decide to retain them (most organizations align
this policy with email retention) and are searchable.
·
Follow #Hashtags
to get notified when new content relevant to your area of interest is added.
·
@mention someone
to direct an activity post to their attention (as in Twitter).
|
Communities of Practice
|
·
Must configure an
“out of the box” template to align with community objectives.
·
Community site is
just an instance of a standard team site – with similar requirements for
managing access and assigning privileges.
·
Simplistic
discussion list.
|
·
New “Community”
site template completely focused on conversations.
·
Access very
different from team sites – users can observe conversations and then “join” a
community when they want to post.
·
Community can
allow anyone to join or can require approval by a Moderator before allowing
someone to become a “Member.”
·
Becoming a member
means you are automatically “Following” the community site.
·
Member photos
show up next to all posts.
·
“Gamification”
options to encourage participation – points, badges, and a “top contributors”
leaderboard.
·
Designated users
can be “gifted” a badge – to identify someone as an “Expert” or “Thought
Leader” so that discussion participants can easily distinguish contributions.
·
Ability to
categorize conversations by topic with an image – to create a welcoming
environment and encourage interaction.
|
Workflow
|
·
Several “built
in” workflows with additional options available in SharePoint Designer.
|
·
Significant
enhancements, including new ways to create and visualize workflows.
·
Existing 2010
workflows should upgrade.
|
Collaborating with others outside
the workgroup on individual documents
|
·
Difficult to do
if the person not on the team does not have access to edit the document on
the team site.
·
Only the site
owner can grant permissions.
·
Author can create
a “document workspace” and invite the guest to edit, but then has to publish
the final document back to the main site.
|
·
“Share” button
easily visible for any site and document.
·
Any user can
invite someone to edit an individual document “in place,” but all invitations
are approved by the site owner. (easier to collaborate, but still controlled)
This feature makes it easier to collaborate with people outside the immediate
workgroup but requires that site owners carefully manage permissions when the
collaboration is finished.
·
Users who request
access to a site have an opportunity to explain why they need access so that
site owners can make better decisions about whether or not to grant access.
|
Mobile Access
|
·
Teams can create
mobile views for sites but not necessarily for different types of
mobiledevices..
|
·
Optimized mobile
browser experience - provides a lightweight, contemporary view browsing
experience for users to navigate and access document libraries, lists, wikis,
and Web Parts.
·
Device channels -
you can render a single published SharePoint site in multiple designs to
accommodate different device types.
·
Business
intelligence - SharePoint Server 2013 enables a user to view certain kinds of
dashboard content. This includes PerformancePoint reports and scorecards, and
Excel Services reports in iOS 5.0 Safari browsers on iPad devices.
·
Office Web Apps -
allows users to view Word, Excel, and PowerPoint documents in mobile
browsers.
|
Branding (creating a custom look
and feel)
|
·
Significant
SharePoint knowledge required to design the user interface for SharePoint
sites.
|
·
The new features
in a publishing site minimize the amount of SharePoint knowledge that is
required to successfully design and brand a SharePoint site.
·
Professional web
designers who know HTML, CSS, and JavaScript already have the skills
necessary to design a SharePoint 2013 site – and can use their preferred
tools such as Dreamweaver to create designs for SharePoint.
|
0 comments: