SPTechCon Extending ECM for Developers

1,166 views

Published on

ECM and SharePoint for Developers

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,166
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
9
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Form ECM 10Form ECM demo 10Doc Manage namespace 5Document ID Service 20Document Sets 5Taxonomy namespace 5Ctype 10
  • SPTechCon Extending ECM for Developers

    1. 1. www.paulswider.com
    2. 2. Understand Forms of ECM ProgrammingBest Practices Extending ECM features
    3. 3. SharePoint Sites, Libraries and Lists Workflow Project Template Policy Object Model Search Object Model SPFile
    4. 4. Document Management Object ModelTaxonomy Object Model
    5. 5. Lives in SharePointRootReferenced from AnyProjectCode Runs onServer
    6. 6. using Microsoft.Office.DocumentManagement;namespace CustomDocumentIDProvider{class CustomDocumentIDProvider :Microsoft.Office.DocumentManagement.DocumentIdProvider{…
    7. 7. New Site Collection Feature: Document ID Service Adds Unique ID Documents Retrieved Regardless of Location
    8. 8. public override boolDoCustomSearchBeforeDefaultSearch{//property used to trigger our custom search first.//If false then we will use the SharePoint search whenretrievingDocument IDsGet…
    9. 9. //Implement our own finder method.//Return empty if no resultspublic override string[]GetDocumentUrlsById(Microsoft.SharePoint.SPSitesite, string documentId){string[] searchhits = new string[0];return new string[0];}…
    10. 10. public override voidFeatureActivated(SPFeatureReceiverPropertiesproperties){SPSite sitecollection =(SPSite)properties.Feature.Parent;DocumentId.SetProvider(sitecollection,typeof(CustomDocumentIDProvider.CustomDocumentID));}…
    11. 11. $site = Get-SPSite http://MyServer[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.Office.DocumentManagement") $assembly =[System.Reflection.Assembly]::Load("CustomDocIdProvider") $type =$assembly.GetType("Microsoft.SDK.MOSS.Samples.CustomDocumentIDProvider");[Microsoft.Office.DocumentManagement.DocumentId]::SetProvider($site, $type);…
    12. 12. SharePoint 2010 introduces document sets, or a collection ofdocuments, 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
    13. 13. Lotus Notes Connector
    14. 14. Lives in SharePointRootReferenced from AnyProjectCode Runs onServer
    15. 15.  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)
    16. 16. Features/Packages• Standard Deployment• Multiple Service ApplicationsUpgradable
    17. 17. Understand Forms of ECM ProgrammingMicrosoft.Office.DocumentManagement Microsoft.SharePoint.Taxonomy Best Practices

    ×