www.paulswider.com
Understand Forms of ECM Programming
Best Practices Extending ECM features
SharePoint Sites, Libraries and Lists

 Workflow Project Template

 Policy Object Model

 Search Object Model

 SPFile
Document Management Object Model


Taxonomy Object Model
Lives in SharePoint
Root

Referenced from Any
Project

Code Runs on
Server
using Microsoft.Office.DocumentManagement;
namespace CustomDocumentIDProvider
{
class CustomDocumentIDProvider :
Microsoft.Office.DocumentManagement.DocumentId
Provider
{
…
New Site Collection Feature: Document ID Service
                Adds Unique ID
  Documents Retrieved Regardless of Location
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
…
//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];
}
…
public override void
FeatureActivated(SPFeatureReceiverProperties
properties)
{
SPSite sitecollection =
(SPSite)properties.Feature.Parent;
DocumentId.SetProvider(sitecollection,
typeof(CustomDocumentIDProvider.CustomDocume
ntID));
}
…
$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);
…
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
Lotus Notes Connector
Lives in SharePoint
Root

Referenced from Any
Project

Code Runs on
Server
 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)
Features/Packages
• Standard Deployment
• Multiple Service
  Applications
Upgradable
Understand Forms of ECM Programming
Microsoft.Office.DocumentManagement
   Microsoft.SharePoint.Taxonomy
           Best Practices
SPTechCon Extending ECM for Developers

SPTechCon Extending ECM for Developers

Editor's Notes

  • #5 Form ECM 10Form ECM demo 10Doc Manage namespace 5Document ID Service 20Document Sets 5Taxonomy namespace 5Ctype 10