This document discusses various object models in SharePoint for ECM programming including the Document Management Object Model, Taxonomy Object Model, Workflow Object Model, Search Object Model, and SPFile. It provides an example of extending the Document ID service and implementing a custom document ID provider. It also mentions document sets in SharePoint 2010 which allow grouping related documents and inheriting metadata from the set to individual items.

2. www.paulswider.com

3. Understand Forms of ECM Programming
Best Practices Extending ECM features

5. SharePoint Sites, Libraries and Lists
Document Management Object Model
Taxonomy Object Model
Workflow Object Model

6. Workflow Object Model
Workflow Project Template
Policy Object Model
Search Object Model
SPFile

7. Lives in SharePoint
Root
Referenced from Any
Project
Code Runs on
Server

8. using Microsoft.Office.DocumentManagement;
namespace CustomDocumentIDProvider
{
class CustomDocumentIDProvider :
Microsoft.Office.DocumentManagement.DocumentId
Provider
{
…

10. New Site Collection Feature: Document ID Service
Adds Unique ID
Documents Retrieved Regardless of Location

11. public override bool
DoCustomSearchBeforeDefaultSearch
{
//property used to trigger our custom search first.
//If false then we will use the SharePoint search when
retrieving
Document IDs
Get
…

12. //Implement our own finder method.
//Return empty if no results
public override string[]
GetDocumentUrlsById(Microsoft.SharePoint.SP
Site
site, string documentId)
{
string[] searchhits = new string[0];
return new string[0];
}
…

13. public override void
FeatureActivated(SPFeatureReceiverProperties
properties)
{
SPSite sitecollection =
(SPSite)properties.Feature.Parent;
DocumentId.SetProvider(sitecollection,
typeof(CustomDocumentIDProvider.CustomDocume
ntID));
}
…

14. $site = Get-SPSite http://MyServer
[System.Reflection.Assembly]::LoadWithPartialName("
Microsoft.Office.DocumentManagement") $assembly =
[System.Reflection.Assembly]::Load("CustomDocIdPro
vider") $type =
$assembly.GetType("Microsoft.SDK.MOSS.Samples.Cu
stomDocumentIDProvider");
[Microsoft.Office.DocumentManagement.DocumentId]::
SetProvider($site, $type);
…

16. SharePoint 2010 introduces document sets, or a
collection of documents, spreadsheets, presentations,
etc. that make up a single work product
Compound Document Inherits from Folder
Metadata exists on individual items and the set as a
whole

19. Lotus Notes Connector

20. Lives in SharePoint
Root
Referenced from Any
Project
Code Runs on
Server

22.  Content Types are ‟published” from a ‟normal” Site Content Type Gallery
 Maximum of 1 Hub per Metadata Shared Application Service
 It is not a requirement that a Metadata Service syndicate content types
 It is not a requirement that a service connection consume content types
from the service
 Setting a site collection to be the hub enables necessary components on hub
 Content Type with all the corresponding columns
 Including Document Set Content Type
 Policies
 And workflow associations (not the workflows)

24. Features/Packages
• Standard Deployment
• Multiple Service
Applications
Upgradable

25. Understand Forms of ECM Programming
Microsoft.Office.DocumentManagement
Microsoft.SharePoint.Taxonomy
Best Practices