Understanding Document IDs & Document Sets in SharePoint 2013 & Office 365

Posted by Errin O'Connor on May, 07, 2015 05:05

SharePoint 2013 & Office 365’s SharePoint Online Document IDs capabilities allow you to manage and track items regardless of where there are stored. Being able to track important content such as a legal contact, even if it is moved from one document library to another for appropriate reasons, that legal contract will retains its underlying Document ID.

Document ID capabilities allow you to easily track content from its creation through archival and also will allow important documents that have been archived to be located for retrieval. Document IDs are a site collection level feature that can be easily activated and when a document is generated a unique ID is applied and automatically searchable.

Document Sets in SharePoint 2013 | Office 365 | SharePoint Online

Document Sets is a feature in SharePoint 2013 and/or Office 365’s SharePoint Online that will allow your organization’s users to incorporate multiple documents or files into a unique “set” or type of folder so that there is a relational set of attributes and unique elements that enable them to be managed as a single deliverable.

Document Sets can provide your organization with the following:

  • Organizations that want to manage “multi-document sets” consistently can configure a new Document Set content type for each work product they typically create and utilize
  • Policies, tagging, and templates can be applied to any document set that is created
  • Content Types let us wrap up Documents in formal metadata
  • Helps when you are working multiple documents at the same time

By default, Document Sets inherit permissions from the library in which they are located and you can opt to specify unique permissions for a Document Set if you need to restrict or change who has access to the documents in an individual Document Set.

Users are able to interact with document sets in much the same way that they interact with regular SharePoint folders.

In addition, Document Sets can provide your organization with the following:

  • All documents in a Document Set share the metadata and the entire set can also be versioned
  • Any kind of document that your SharePoint farm is configured to support can be included in a Document Set
  • Anytime you want to enable users to group multiple documents that support a single project or task together into a single entity.
  • When you need to organize unmanaged documents and enable collaboration on documents that have all been invested with similar metadata
  • Ease workflow deployment on multiple items with SharePoint Designer 2013
  • Metadata only has to be updated in one place for it to be applied to all the documents contained within the Document Set
  • Gives the ability to capture a version of all documents within a container
  • Lives as a site collection feature that must be specifically enabled

Note: In Office 365, the Document Sets feature is currently only available with the Enterprise or “E” plans.

Document Sets and Folders present a similar interface to users however, the functionality in Document Sets are specifically targeted to support business processes and the management of content as a single unit.

[gravityforms id=41 title=”true” description=”false”]
<div class='gf_browser_unknown gform_wrapper exit_intent_popup_wrapper' id='gform_wrapper_41' ><form method='post' enctype='multipart/form-data' id='gform_41' class='exit_intent_popup' action='/document-ids-document-sets-in-sharepoint-2013-office-365/'> <div class='gform_heading'> <h3 class='gform_title'>Exit Intent</h3> <span class='gform_description'></span> </div> <div class='gform_body'><ul id='gform_fields_41' class='gform_fields top_label form_sublabel_below description_below'><li id='field_41_1' class='gfield gform_hidden field_sublabel_below field_description_below gfield_visibility_visible' ><input name='input_1' id='input_41_1' type='hidden' class='gform_hidden' aria-invalid="false" value='' /></li><li id='field_41_9' class='gfield gfield_contains_required field_sublabel_below field_description_below gfield_visibility_visible' ><label class='gfield_label' for='input_41_9' >Full Name<span class='gfield_required'>*</span></label><div class='ginput_container ginput_container_text'><input name='input_9' id='input_41_9' type='text' value='' class='medium' placeholder='Full Name' aria-required="true" aria-invalid="false" /></div></li><li id='field_41_6' class='gfield gfield_contains_required field_sublabel_below field_description_below gfield_visibility_visible' ><label class='gfield_label' for='input_41_6' >Email<span class='gfield_required'>*</span></label><div class='ginput_container ginput_container_email'> <input name='input_6' id='input_41_6' type='text' value='' class='medium' placeholder='Email Address' aria-required="true" aria-invalid="false" /> </div></li><li id='field_41_7' class='gfield gfield_contains_required field_sublabel_below field_description_below gfield_visibility_visible' ><label class='gfield_label' for='input_41_7' >Phone<span class='gfield_required'>*</span></label><div class='ginput_container ginput_container_phone'><input name='input_7' id='input_41_7' type='text' value='' class='medium' placeholder='Phone Number' aria-required="true" aria-invalid="false" /></div></li><li id='field_41_10' class='gfield gfield_contains_required field_sublabel_below field_description_below gfield_visibility_visible' ><label class='gfield_label' for='input_41_10' >Company Name<span class='gfield_required'>*</span></label><div class='ginput_container ginput_container_text'><input name='input_10' id='input_41_10' type='text' value='' class='medium' placeholder='Company Name' aria-required="true" aria-invalid="false" /></div></li><li id='field_41_8' class='gfield field_sublabel_below field_description_below gfield_visibility_visible' ><label class='gfield_label' for='input_41_8' >Message</label><div class='ginput_container ginput_container_textarea'><textarea name='input_8' id='input_41_8' class='textarea medium' placeholder='Type your message here...' aria-invalid="false" rows='10' cols='50'></textarea></div></li> </ul></div> <div class='gform_footer top_label'> <input type='submit' id='gform_submit_button_41' class='gform_button button' value='Submit' onclick='if(window["gf_submitting_41"]){return false;} window["gf_submitting_41"]=true; ' onkeypress='if( event.keyCode == 13 ){ if(window["gf_submitting_41"]){return false;} window["gf_submitting_41"]=true; jQuery("#gform_41").trigger("submit",[true]); }' /> <input type='hidden' class='gform_hidden' name='is_submit_41' value='1' /> <input type='hidden' class='gform_hidden' name='gform_submit' value='41' /> <input type='hidden' class='gform_hidden' name='gform_unique_id' value='' /> <input type='hidden' class='gform_hidden' name='state_41' value='WyJbXSIsIjEwNTJhNGVmMWMyNzI3YTJmMjdiZTA1NjU4ZDMzYzY3Il0=' /> <input type='hidden' class='gform_hidden' name='gform_target_page_number_41' id='gform_target_page_number_41' value='0' /> <input type='hidden' class='gform_hidden' name='gform_source_page_number_41' id='gform_source_page_number_41' value='1' /> <input type='hidden' name='gform_field_values' value='' /> </div> </form> </div><script type='text/javascript'> jQuery(document).bind('gform_post_render', function(event, formId, currentPage){if(formId == 41) {if(typeof Placeholders != 'undefined'){ Placeholders.enable(); }jQuery('#input_41_7').mask('(999) 999-9999').bind('keypress', function(e){if(e.which == 13){jQuery(this).blur();} } );} } );jQuery(document).bind('gform_post_conditional_logic', function(event, formId, fields, isInit){} );</script><script type='text/javascript'> jQuery(document).ready(function(){jQuery(document).trigger('gform_post_render', [41, 1]) } ); </script>