SharePoint Server 2010 delivers a broad set of content management capabilities for organizations to manage content. One of the new capabilities is the “Document Set” feature. (To know more on what’s new for document management read the Introducing Document Management in SharePoint 2010 post by Adam Harmetz in the Microsoft Enterprise Content Management (ECM) Team Blog)
Document Set enables users to group multiple documents, that support a single project or task, together into a single entity. All documents in a Document Set share the metadata and the entire set can also be versioned.
Some example where document set might be useful to manage information would be:
- RFP response: managing multiple documents like proposal (.docx), presentation (.pptx), estimates and pricing (.xlsx) which are part of the response to a RFP
- Product documentation: managing multiple documents like TDM/BDM brochure (.docx/.pdf), evaluation guides (.docx), various presentations (.pptx), feature comparison sheets (.xlsx) etc. which need to be created as part of product release
Document sets are built on SharePoint Server 2010 content types, and you can create multiple unique document set content types as part of your implementation.
Note: Document Set feature is not available in SharePoint Foundation 2010.
Users interact with document sets in much the same way that they interact with regular SharePoint folders. There are some differences though which make them very useful in some scenarios:
A document set content type can be used as-is, customized by modifying its settings in the site content gallery or when the document set is added to the document library, or used as the basis for creating a custom document set content type
A Welcome page that welcomes and orients users of a document set by displaying the contents of the set and its properties. You can use this default Welcome page or create your own
A New page for the document set. You can use this default New page or create your own
Restrict the Content Types allowed in the document set by selecting from a list of available site content types
Include specific items/documents you want to be in all the new Document Sets created from the Content Type. There is also an option of prefixing each file name by the name of the Document Set
List of metadata to synchronize with all items in the document set
Versioning capabilities for document sets
New workflow activities used to create workflows with document sets
An object model that you can use to programmatically manipulate document set objects, templates, metadata, and URLs for custom New pages and Welcome pages. More on this in the Part 2 of this blog post
For more details, you can refer to the Document Sets Infrastructure in the SharePoint Server 2010 Software Development Kit (SDK).
This is how the ribbon for a Document Set looks:
In real world scenario, you would configure a custom Document Set content type for each work product your users typically create. To create a custom Document Set content type, create a child of the default Document Set content type. In the custom content type you would then define all the approved content types, default items, columns, shared columns, workflows and policies.
Following are some of the important considerations you should be aware of when planning a solution with Document Sets:
- There is no limit on the number of documents that can exist in a Document Set. However, display load times may be limited by the list view threshold which by default is set at 5,000 items. Read more on this here: SharePoint Server 2010 Capacity Management: Software Boundaries and Limits
- Folders are not allowed in document sets
- Metadata navigation cannot be used in a Document Set
- When you use the Send to feature with a Document Set, the sum for all documents in a Document Set cannot be larger than 50MB. So, for a collection or work product with a very large number of items, a folder structure in a document library may be a better solution.
- There is no limit on the number of Document Sets that can exist in a document library. However, the number of Document Sets that can appear in lists will be limited by the list view threshold.
The Document Sets planning (SharePoint Server 2010) article provides guidance on how you can integrate them with your Microsoft SharePoint Server 2010 document management solution.
How to Enable Document Sets?
Document Set is a site collection level feature that must be first activated.
Follow the steps given below:
- Go to Site Settings > Site Collection Features page
- Activate Document Sets feature
- Open the Document Library in which you want to enable document sets
- Go to Document Library Settings > Advanced Settings page for the library
- Change the Allow management of content types? setting to Yes
- On the Document Library Settings page, click on Add from existing site content types link
- Select Document Set content type (or any custom content type you created based on it) from the Available Site Content Types options list.
Welcome Page is the landing page for document set and is used to present metadata, descriptions, and lists of documents belonging to the document set. Each Document Set content type can have its own Welcome page. When a document set content type is created, the Welcome page is created at the site level. Then, when the content type is added to a list, the Welcome page is copied to the list level. The pages are stored at:
- Site level: <WebUrl>/_CTS/<ContentTypeName>
- List level: <ListUrl>/forms/<ContentTypeName>
The Welcome page can be customized by using:
- The browser
- Microsoft SharePoint Designer 2010
- The object model
You can read more on this here: How to: Customize the Welcome Page
How Versioning works?
Document set versioning is additive, which means it does not replace versioning for individual items, but instead provides an additional layer of support designed specifically for viewing and managing the document set life cycle. So, individual items inside a set can have versions and the set itself can also have versions.
A document set version is simply a set of metadata associated with the document set, including a Check in comments text field, a summary view of document set properties, and a summary view of changes to properties of document sets. It also tracks what version of the selected document was “current” at the time when the document set version was captured.
A document set has a Version History page that enables users to see the version history and act on a previous version of a document set.
You can also “delete” or “restore” a version. Only thing to remember is that when you a delete a document set version, it does not delete the versions of the items in the document set.