Hybrid Self-Service Site Creation now available for SharePoint Server 2013


At the center of collaboration is the site and modern Team Site in Office 365 are core to discovering and showcasing the most relevant and important information to you and your business. While SharePoint Online in Office 365 is an attractive alternative to on-premises business solutions with SharePoint. You might want to or need to deploy specific solutions in the cloud while still maintaining your on-premises investments or gradually move to cloud using a staged, workload-driven approach.

Hybrid scenarios with Office 365 and SharePoint on-premises allow you to bring the cloud to your business while bringing the business to the cloud. Today we’re pleased to announce the availability of hybrid self-service site creation for customers of SharePoint Server 2013.

New hybrid self-service site creation allows SharePoint administrators to direct users site creations requests to Office 365. This new hybrid capability allows administrators of SharePoint Server 2013 to have the option to enable their existing or new Self-Service Site Creation flow redirect users to SharePoint Online to create a Group (with an associated Team Site). SharePoint administrators can turn this feature on or off on the Self-service Site Collection Management page, accessible from SharePoint 2013 Central Administration.

This capability is included in the March 2017 Public Update available later today. Download the March 2017 Public Update for SharePoint Server 2013 at https://technet.microsoft.com/en-us/library/mt715807(v=office.16).aspx#BKMK_2013.


New with the March 2017 Public Update for SharePoint Server 2013 is the option to Create Site Collections in SharePoint Online as illustrated above. When selecting this option any hybrid user that goes to the Self-service Site Creation page (/_layouts/15/scsignup.aspx) will be redirected to SharePoint Online Group creation, and will be able to create a Group and associated Team Site in the Cloud using the new modern group creation flow. Hybrid users are defined through inclusion in one or more audiences as configured when enabling the hybrid sites feature in SharePoint Server 2013. To learn more about hybrid sites and audiences see also https://support.office.com/article/5ff7e56a-7af2-4511-adec-1e043afe244e.


For on-premises only users, or those excluded from the hybrid audience as described above, they will still be able to use the existing On-Premise Self-service Site Creation experience.

In addition to the configuration options available directly through SharePoint 2013 Central Administration, there will also be entry points to the configuration page through a one-time Central Administration alert box and from the Hybrid Picker in Office 365.

The cloud is no longer a luxury—it’s central to a mobile, modern workplace—and Office 365 brings the cloud to you, on your terms and across SharePoint and OneDrive we’re constantly working to help you take advantage of the power of Office 365. Kick start the journey to the cloud with hybrid self-service site creation today.


Learn more about hybrid scenarios across Office 365 at http://hybrid.office.com/.

Download the hybrid scenarios pocket guide with SharePoint and Office 365 at https://go.microsoft.com/fwlink/?linkid=842608.

Get more information on implementing hybrid scenarios with SharePoint and Office 365 at https://support.office.com/en-us/article/SharePoint-Hybrid-4c89a95a-a58c-4fc1-974a-389d4f195383.


Q:  Will this feature be available to SharePoint Server 2016?

A:  Yes.  In H2 CY2017 we’ll make available hybrid self-service site creation to customers of SharePoint Server 2016.  In the near term you can continue to deploy the hybrid sites feature as an interim solution.  To learn more about hybrid sites see also https://support.office.com/en-us/article/SharePoint-hybrid-sites-and-search-5ff7e56a-7af2-4511-adec-1e043afe244e.

Simplifying Hybrid Configuration with the new Hybrid Scenario Picker

This month we continued to invest in simplifying the Office 365 and SharePoint 2013 hybrid experience with the new hybrid scenario picker available in the Office 365 Administration Center.


The hybrid scenario picker is designed to help customers get up and running quickly with in-market and future hybrid scenarios by providing quick access to hybrid scenarios such as OneDrive for Business and SharePoint Sites in addition to programmatically configuring hybrid prerequisites to include Server-to-Server (S2s) and OAuth connections.



The current hybrid scenario picker experience provides access to two (2) core scenarios supported with SharePoint Server 2013 and the upcoming release of SharePoint Server 2016 Preview.


SharePoint Hybrid OneDrive for Business – The Hybrid OneDrive option redirects your on-premises My Sites/OneDrive host to SharePoint Online OneDrive for Business. Once the wizard completes, any click of the OneDrive link from on-premises will redirect to OneDrive in the Cloud. The redirection is complete and users may begin moving or syncing files to the Cloud for storage, right away.  The wizard also configures a sever-to-server (S2S/OAuth) connection between SharePoint Server on-premises and SharePoint Online.

SharePoint Hybrid Site Features – The Hybrid SharePoint Sites option configures a server-to-server (S2S/OAuth) connection that allows you to join features of your team site to your SharePoint Online site collection in Office 365.  OneDrive for Business redirection is also configured when you click this option. Note that, depending on what hybrid features you want to use, there may be other steps that you need to complete when this wizard finishes.  For example, if you want to configure SharePoint Server search as a hybrid of SharePoint Online and SharePoint Server on-premises.


To successfully configure a hybrid Office 365 and SharePoint 2013 experience using the hybrid scenario picker your SharePoint Server 2013 farm should have the August PU installed, ports 80 and 443 should be open for outbound connections, and users synchronized with Office 365 using Azure Active Directory Sync (AAD Sync).


To learn more about hybrid Office 365 and SharePoint scenarios see also https://technet.microsoft.com/en-us/library/jj838715.aspx.

The SharePoint Journey

Microsoft Ignite will open the window to our vision, strategy, and future for SharePoint and provide a first look at most recent developments with SharePoint Server 2016.  From the business value for organizations looking to modernize their workplace and infrastructure to the technical value it will deliver to IT Professionals and Developers as well as new hybrid investments for those customers looking to enrich their existing investments with cloud innovation.

With Microsoft Ignite just around the corner, it’s time to look back and provide a little historical SharePoint information.

There have been 5SharePoint releases.


“Exchange and SharePoint become best friends”

Exchange Server works on a new information store (Web Store) to support document, web content, and e-mail management.

Codename Tahoe (the genesis of SharePoint Products and Technologies) advances Platinum introducing document management capabilities through WebDAV – Document Authoring and Versioning in addition to an improved search and indexing engine.

Platinum and Tahoe would represent a new, next generation messaging, collaboration, and document management platform.

Learn more about the evolution of SharePoint’s storage architecture at http://blogs.technet.com/b/wbaer/archive/2012/12/20/shredded-storage-and-the-evolution-of-sharepoint-s-storage-architecture.aspx.


“A gem is found in nuggets”

Microsoft makes available a free download called Digital Dashboard Starter Kit introducing our first portal framework.   Solutions based on the starter kit enabled a user interface that could reside within Outlook through visual aids called “nuggets” that displayed information from a variety of content sources – “nuggets” would later take on the name Web Parts.


“A rolling milestone gathers no moss”

Tahoe reaches its beta 1 milestone in early 2000 and the Digital Dashboard Starter Kit is renamed the Digital Dashboard Resource Kit.  In mid-2000 Tahoe reaches another important milestone (Beta 2) with important changes to include a new user interface based on the Digital Dashboard Resource Kit creating a “true” portal user experience and subsequently retiring its codename in favor of SharePoint Portal Server 2001.


“So it begins”

SharePoint Portal Server 2001 is released and creates a portal web site that allows users to share documents and search for information across the organization and enterprise, including SharePoint Team Services-based Web sites—all within one extensible portal interface. SharePoint Portal Server includes robust document management features that allow companies to incorporate business processes into their portal solution, but is limited by the Web Store and Digital Dashboard.

Web Store performance and scalability limited the expansion of SharePoint and Digital Dashboards were developed outside of the core development platform (Visual Studio) which limited the audience for extensibility.

In parallel the fledging portal market began to see unprecedented growth and overlap with the existing  Web Content Management (WCM) market which included CMS 2001.

As the growth and adoption of SharePoint Portal Server 2001 continued to rise in the then new portals market, SharePoint Team Services was released in conjunction with Office 2000 providing web-based team-centric collaboration capabilities.



“Raise the roof”

The Web Store, the storage foundation for SharePoint Portal Server 2001 is replaced with SQL Server as the storage backend – on the other side of the topology Digital Dashboards were phased out in favor of ASP.NET improving overall scalability and portal capabilities at the expense of some document management capabilities, notably document profiles and workflow that were to be removed from the upcoming SharePoint release.

This was also a tumultuous time for SharePoint Team Services – but in the end the teams responsible for SharePoint Portal Server and SharePoint Team Services were converged.  In parallel to the changes affecting the technologies that powered SharePoint, CMS evolved as well leveraging ASP.NET on the frontend and delivered as CMS 2002.

In 2002 SharePoint Team Services officially was renamed as Windows SharePoint Services (WSS) and packaged in Windows Server 2003 as a Feature of the server – like SharePoint Portal Server it also provided a collaboration store and Web Part user interface build on ASP.NET.

In this same period SharePoint Portal Server (v2 at the time) was officially branded Microsoft Office SharePoint Portal Server 2003 (no longer referred to as codename Matrix), built on top of Windows SharePoint Services, but delivered independent of Windows Server 2003.


This new release contained important scenarios such as search and indexing, but also ushered in personalization (people-centric collaboration), and enhanced taxonomy capabilities with improved overall manageability.


“Got SOX”?

SOX or Sarbanes-Oxley is introduced to the world and changes document and records management practices.  In response, the CMS and SharePoint Portal Server groups converge in 2004 and Web Parts built using ASP.NET were enabled for developers.  The extensibility era begins…

Near the end of 2005 ASP.NET v2 launches to include new native Web Parts and Windows Workflow Foundation becomes a native add-on to Windows Server that provides a new workflow service that other applications can build on.


“Time to Groove”

In 2005, Grove was acquired, a peer-to-peer (P2P) team-based collaboration product that also includes synchronization of SharePoint sites.


“Who puts MOSS on a server anyway”

Microsoft Office SharePoint Server 2007 is born signifying a leap forward in experiences.

Microsoft Office SharePoint Server 2007 was defined as a Microsoft server product that creates a portal website that allows users to share documents and search for information across the organization and enterprise within one extensible portal interface.


Windows SharePoint Services moves forward, but now as a standalone product versus Windows Server feature.

Groove Server 2007 is released with Microsoft Office SharePoint Server 2007, which provides the server software and tools that IT organizations can use to best deploy, manage, and integrate the Groove functionality that comes with the new Groove 2007.


SharePoint Server 2010 is released, the first in two successive releases to drop the Microsoft Office branding.


Groove is renamed SharePoint Workspace and released as Microsoft SharePoint Workspace 2010, the server management platform remains Groove Server and released as Groove Server 2010.


10/11/12 the world is introduced to the most recent generation of SharePoint Products and Technologies, SharePoint 2013.


Personal sites, a staple of SharePoint people-centric collaboration are rebranded and paired with a new sync client powered by Groove as SkyDrive Pro, over the course of the SharePoint Server 2013 release these capabilities will become OneDrive for Business.


The next generation of SharePoint is revealed as SharePoint Server 2016 – want to learn more…  Register now for Microsoft Ignite.

SharePoint and Read-Only Domain Controllers (RODC)

The question of read-only domain controllers (RODC) and SharePoint comes up frequently in conversation and on forums, whether not supported, and what potential issues can be expected if implemented with SharePoint.  This article will help address some of these questions.


Q:  Can I use a read-only domain controller (RODC) with SharePoint 2013?

A:  Yes; however, there are limitations and constraints with certain operations (see below).  An implementation of RODC with SharePoint should assume a writable replication partner.  Introducing an RODC into an environment does impact applications that interact with AD DS to include SharePoint.  An RODC implementation should be thoroughly validated in an isolated non-production environment to understand constraints, limitations, performance, and any potential issues that may not exist with conventional, writable domain controllers.  In addition performance should be carefully monitored where connectivity between the RODC and partner replication server (writable domain controller) is limited.  In conclusion, an RODC implementation with SharePoint must include a writable partner replication server.

For additional information on RODC known issues see http://technet.microsoft.com/en-us/library/cc725669(v=ws.10).aspx.

For RODC placement considerations see http://technet.microsoft.com/en-us/library/cc732632(v=ws.10).aspx.

Q:  What is a RODC?

A:  An RODC is a revised version of a domain controller, introduced in Windows Server 2008 that hosts read-only partitions of AD DS.

RODC’s are most commonly implemented to address a variety of scenarios to include:

  • Placing domains controller where physical security cannot be guaranteed.
  • Domain controllers deployed with additional active server roles.
  • Domain controllers used in Extranet or application-facing roles.
  • Scenarios where low network bandwidth exists, I.e. branch office scenarios.

Q:  How does it work?

A:  Except for account passwords and other filtered attributes, an RODC holds the same user accounts and attributes that a writable domain controller holds. Clients, however, are not able to write changes directly to the RODC. Local applications that request Read access to the directory obtain access, whereas Lightweight Directory Access Protocol (LDAP) applications that perform a Write operation are referred to a writable domain controller in a hub site.

Q:  In what scenarios does SharePoint require a writable domain controller?

A:  There are a number of individual scenarios where a Write operation is required, some of which are base SharePoint functionality, and others workload dependent.

NOTE This is not an exhaustive list.


SharePoint implements Service Connection Points that are created during installation and configuration.  Service Connection Points object represents one or more instances of a service that is available in a network.  For additional information on SharePoint and Service Connection Points see also http://blogs.technet.com/b/wbaer/archive/2010/04/28/service-connection-points-and-governance-with-sharepoint-server-2010.aspx.

Profile Synchronization

If you'll export property values from SharePoint to AD DS, the synchronization account must have Create Child Objects (this object and all descendants) and Write All Properties (this object and all descendants) permissions on the organizational unit (OU) with which you are synchronizing.

NOTE Replicate Directory Changes does not require a writable domain controller.

The Replicate Directory Changes permission enables the synchronization account to read AD DS objects and to discover AD DS objects that have been changed in the domain.  The Replicate Directory Changes permission allows an account to query for the changes in the directory. This permission does not allow an account to make any changes in the directory.

People Picker

People picker is unable to resolve users in a trusted forest if the only domain controller SharePoint can access is read-only.   For additional information on People Picker and RODC’s see also http://support.microsoft.com/kb/970612/en-us.

Managed Service Accounts

SharePoint 2010 introduced the concept of a managed service account with works in correlation with AD DS to enable automatic password management, which can better isolate these services from other services on the computer.  Registering a managed account in SharePoint, allows SharePoint to change the credentials for a managed account at a specified interval.

Incoming E-mail and Provisioning Contacts

Incoming E-mail implements the SharePoint Directory Management service to connect SharePoint sites to the user directory which allows users to create and manage e-mail distribution groups from SharePoint in addition to creating contacts in the user directory.  The SharePoint Directory Management service communicates with AD DS.

Publishing SharePoint on an Active Directory Service Connection Point

See also Installation/Configuration above.


In most cases an organization should not experience the issues listed above as a RODC implementation should include writable partner replication servers.

In Extranet and perimeter network scenarios, writer operations will fail, RODC is not a candidate in such scenarios; however, where connectivity exists between and RODC and a partner replication server, a write operation will return a referral to a writable domain controller – if connectivity to a writable domain controller is not available, then Write operations fail regardless of whether the application uses LDAP or ADSI.

For additional RODC planning and deployment information see also http://technet.microsoft.com/en-us/library/cc771744(v=WS.10).aspx.

Document Property Promotion and Demotion Overview and Considerations


Document Property Promotion and Demotion is a Feature in versions of SharePoint designed to synchronize specific metadata across documents and its parent List columns and/or fields.

Property promotion refers to the process of extracting values from properties of a document and writing those values to corresponding columns on the list or document library where the document is stored.

Property demotion is the same process in reverse. Values are read from list columns and written to document properties.

Document Parser

SharePoint works together with a document parser to provide automation of the process of promoting and demoting properties so if the value of a one or more document properties changes, those changes are automatically synchronized to the parent List object or conversely when the values of the parent List columns or fields in a list item change, those changes are synchronized to the subordinate document associated with the item.

Document Parsers represent a significant advantage to managing metadata associated with one or more documents stored in a SharePoint List or Library, by providing a programmatic approach to managing the metadata associated with a document removing the need to manually synchronize important document characteristics across a document and its parent container.  By default SharePoint Server 2013 provides document parsers (pluggable) for the following types:

docx      SharePoint.SPDocumentParser.OfficeParser

docm      SharePoint.SPDocumentParser.OfficeParser

dotx      SharePoint.SPDocumentParser.OfficeParser

dotm      SharePoint.SPDocumentParser.OfficeParser

pptx      SharePoint.SPDocumentParser.OfficeParser

pptm      SharePoint.SPDocumentParser.OfficeParser

potm      SharePoint.SPDocumentParser.OfficeParser

potx      SharePoint.SPDocumentParser.OfficeParser

ppsx      SharePoint.SPDocumentParser.OfficeParser

ppsm      SharePoint.SPDocumentParser.OfficeParser

xlsx      SharePoint.SPDocumentParser.OfficeParser

xlsb      SharePoint.SPDocumentParser.OfficeParser

xlsm      SharePoint.SPDocumentParser.OfficeParser

xltx      SharePoint.SPDocumentParser.OfficeParser

xltm      SharePoint.SPDocumentParser.OfficeParser

gif       SharePoint.SPDocumentParser.ImageParser

jpeg      SharePoint.SPDocumentParser.ImageParser

jpg       SharePoint.SPDocumentParser.ImageParser

jpe       SharePoint.SPDocumentParser.ImageParser

jfif      SharePoint.SPDocumentParser.ImageParser

bmp       SharePoint.SPDocumentParser.ImageParser

dib       SharePoint.SPDocumentParser.ImageParser

png       SharePoint.SPDocumentParser.ImageParser

tif       SharePoint.SPDocumentParser.ImageParser

tiff      SharePoint.SPDocumentParser.ImageParser

ico       SharePoint.SPDocumentParser.ImageParser

wdp       SharePoint.SPDocumentParser.ImageParser

hdp       SharePoint.SPDocumentParser.ImageParser

In addition to the parsers provided out of the box, SharePoint Server 2013 also provides an extensible document parsing infrastructure that allows developers to install custom parsers for types not included out of the box to enable the process of property promotion and demotion for those types.



Document Promotion and Demotion is applied when the following conditions are met:

  • A document is uploaded to a SharePoint Document Library
  • List item fields associated with a document are modified
  • SPFile object properties are programmatically modified
  • A document is downloaded after the list item schema is modified (first run experience only)



In each scenario SharePoint will attempt to determine whether or not a parser is associated with the document type and in the event a parser is associated with the document type, SharePoint invokes the parser and sends the parser the document and property bag object.  If a promotion scenario, the document parser will fill the property bag with the values that need to be synchronized with the parent list or in a demotion scenario, extracts values from the property bag that need to be written to the document.

Content Types

Referencing the illustration above, when using the document parser interface, document parsers can access the Content Type assigned to a document and subsequently store the content type in the document in addition to updating the Content Type definition stored in the document to match the version of the definition used by a List or Document Library.


Validating Input / Output

For content supportive of Document Parsing an XML namespace designation is added to the document metadata, in some cases, the document itself.

Example 1

Create a new HTML type document “PropValidation.html”.

Copy into the document the following HTML:

            <span>Hello World</span>

Save as something.html

Upload to a SharePoint Document Library and open the document.

The following html will be added to the document

<html xmlns:mso="urn:schemas-microsoft-com:office:office" xmlns:msdt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882">
<!–[if gte mso 9]><xml>
<mso:IsMyDocuments msdt:dt="string">1</mso:IsMyDocuments>

            <span>Hello World</span>

Notice the UUID element.  The UUID is an XML namespace designation used as part of property demotion, everyone who saves an HTML-like file to a SharePoint document Library will have the same GUID inserted into the document.

Example 2

Create a new Microsoft Word Document (Document.docx).

Edit the document properties and specify a Title property of “Parse this field”.


Upload the document to a Document Library.  The Title column field associated with the document will reflect the document property (promotion).


Edit the Title property of Document.docx in the browser.


Download the document, the document property will be updated to reflect the value specified in the Title column field associated with the document (demotion).



Special Content Type Considerations

In some cases a document Content Type may not be associated with the Document Library where the document is uploaded (I.e. a user creates a document from a Document Template containing a Content Type or moved the document to a different Document Library.  In these scenarios, unlike the flow depicted in the image above, SharePoint will:

  • Invoke the Document Parser to demote the out of the box default List Content Type for the Document Library into the document if the document contains a property for a Content Type, but the document property is empty.  SharePoint will then promote the document properties to match columns in the out of the box List Content Type.
  • Leaves the document Content Type unchanged if the Document Library allows any Content Type and the document is assigned a Content Type not associated with the Document Library.  SharePoint will not promote the document Content Type, but will promote any document properties that match the Document Library columns.


If a List is set to allow any Content Type, documents of any Content Type can be uploaded and their Content Types will not be overwritten which subsequently enables movement of documents between Libraries without the documents losing their metadata.

  • Invokes the Document Parser to demote the out of the box List Content Type for the Document Library into the document if the document is assigned a Content Type that is not associated with the Document Library and the Document Library does not allow any Content Types (see Note above).  SharePoint then promotes the document properties that match columns in the out of the box List Content Type and stores the document.

Enumerating Pluggable Parsers

Enumeration of Document Parsers lists all of the default (pluggable) parsers shipped with SharePoint.

To enumerate pluggable parsers refer to the following code sample.


namespace EnumParsers
    using System;
    using System.Collections.Generic;
    using System.Globalization;
    using System.Linq;
    using System.Text;
    using System.Threading.Tasks;
    using Microsoft.SharePoint.Administration;

    public static class Program
        private static void Main()
            SPFarm objFarm = SPFarm.Local;
            SPWebService service = objFarm.Services.GetValue<SPWebService>(string.Empty);

            Dictionary<string, SPDocumentParser> objParser = service.PluggableParsers;
            Dictionary<string, SPDocumentParser>.KeyCollection keys = objParser.Keys;

            Console.WriteLine("Extension     Parser");
            Console.WriteLine("---------     -------");
            foreach (string key in keys)
                Console.WriteLine(string.Format(CultureInfo.CurrentCulture, "{0, -7}       {1}", objParser[key].FileExtension, objParser[key].ProgId));

Disabling the Document Parser

The Document Parser can be enabled and/or disabled on-premises by configuring the SPWeb.ParserEnabled value to True|False.


namespace ParserEnabled
    using System;
    using System.Collections.Generic;
    using System.Linq;
    using System.Text;
    using System.Threading.Tasks;
    using Microsoft.SharePoint;
    using Microsoft.SharePoint.Administration;

    class Program
        static void Main(string[] args)
            SPFarm oFarm = SPFarm.Local;
                SPWebApplication webApp = SPWebApplication.Lookup(new Uri("http://www.contoso.com"));

                foreach (SPSite site in webApp.Sites)
                    foreach (SPWeb web in site.AllWebs)
                        if (web.ParserEnabled == true)
                            web.ParserEnabled = false;

Windows PowerShell

$web = Get-SPWeb www.contoso.com
$web.ParserEnabled = $false


Disabled Document Parsing should be carefully considered as it will also impact Features dependent on promotion and demotion.  For example, content type syndication and document information panels.

Disabling Document Parsing is effectively a one-way operation.  Disabling parsing disables the bidirectional synchronization of document properties, if disabled, and subsequently re-enabled and the properties are diverged while disabled, the original property values will be synchronized as contained within the property bag.

Similarly, Document Parsers also affect how content types are managed.  For example, when SharePoint invokes a parser to promote document properties (writes the properties to the parent List), the parser writes all document properties to an instance of the IParserPropertyBag interface and then determines which properties in the property bag match the columns on the parent List or Library.  If the property bag indicates that the document has an assigned content type, and the content type is supported by the document library, SharePoint promotes the document properties that match the columns that are included in the content type.

Associating Custom Parsers with File Types

In addition to enumeration and disabling document parsers, you can also add a document parser and associate with a specific parser.

The example below associates a custom document parser with an RTF extension.


namespace AddParsers
    using System;
    using System.Collections.Generic;
    using System.Globalization;
    using System.Linq;
    using System.Text;
    using System.Threading.Tasks;
    using Microsoft.SharePoint.Administration;

    public static class Program
        static void Main(string[] args)
            SPWebService service = SPWebService.ContentService;
            Dictionary<string, SPDocumentParser> parsers = service.PluggableParsers;

            string extension = "rtf";
            string progID = parsers["docx"].ProgId;
            SPDocumentParser customParser = new SPDocumentParser(progID, extension);

            if (parsers.ContainsKey(extension))

            service.PluggableParsers.Add(extension, customParser);


Document parsing in SharePoint provides a number of benefits to the management of metadata around documents,

Metadata management is a powerful capability offered in SharePoint, document parsing simplifies the scenario of maintaining consistent metadata between documents and their parent libraries and parent libraries and their subordinate documents.

In SharePoint several Features leverage Document Parser logic to include:

Link Fixup

Link Fixup is used to indicate a Web Part property that contain one or more links to a document, if the document is moved or renamed, Link Fixup corrects the absolute Url to reflect the new location as a relative Url.  See also ManagedLinkAttribute.Fixup property.

Property Panels

Document Information Panels are forms that are displayed within the client application, and which contains fields for the document metadata. Document information panels enable users to enter important metadata about a file anytime they want, without having to leave the client application.  For example, a Document Information Panel may include custom properties to associated with a document, such as declaration information, specific terms, etc.

For files stored in document libraries, the document information is actually the columns of the content type assigned to that file. The document information panel displays a field for each content type property, or column, the user can edit.

For documents stored in SharePoint, these property values are promoted back to the document library, as column values, when the user updates them in the document. Similarly, if the user updates the content type column values in the SharePoint user interface, the new values are demoted into the document itself, as document properties.

Metadata Portability

See Special Content Type Considerations above.


Document Parsers in SharePoint provide an abstract method for users when managing metadata (document properties) across client and server.