SharePoint 2010 vs. SharePoint 2013 Feature Comparison
- From a document collaboration perspective, the structures of both versions are the same –so if you create a metadata architecture for documents in 2010 it should be fully upgradable to 2013.
- The most significant upgrades in document management are in the user experience –including drag and drop to upload documents and the ability to edit managed metadata in a datasheet view.
- The primary differences are in the social experiences, especially with discussion boards. The 2013 discussion board (with Community features enabled) creates and engaging “Facebook-like” activity stream, which is far more user-friendly than the same feature in SharePoint 2010. The added visual appeal is important because getting people to use the discussion board instead of commonly used “who you know” networks will take some planning and effort. If the software is engaging and familiar it will help with “stickiness.”
- The other significant improvement is search, which you will see in the examples on the next few pages.
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 hover 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 allows you to page through PowerPoint presentations without leaving the search results page. •One click 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 News feed 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 News feed 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 #hash tags. •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 #Hash tags 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). |
| 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. |
| 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. |
SharePoint 2010 Discussion List
SharePoint 2010 Discussion List


No comments:
Post a Comment