IW403 Records Management Improvements in SharePoint 2010

Clarity. Direction. Confidence. RECORDS MANAGEMENT IMPROVEMENTS IN SHAREPOINT 2010John F. HollidaySharePoint Architects, Inc.www.SharePointArchitects.uswww.JohnHolliday.net BEST PRACTICES CONFERENCE SHAREPOINT

About Me Books Professional SharePoint 2007 Development Professional SharePoint 2007 Records Management Development Activities/Projects SharePoint Server MVP, Developer, Consultant CAML.NET Framework/CAML.NET IntelliSense SharePoint Developer Network (@SPDEVNET) SharePoint Heroes (sharepointheroes.com) BEST PRACTICES CONFERENCE SHAREPOINT

AgendaReview Records Management Challenges in SharePoint 2007Overview of Key RM Features in SharePoint 2010Understand the new “In Place” Records Management featuresUnderstand the 2010 Records Center BEST PRACTICES CONFERENCE SHAREPOINT

Key Challenges for RM in MOSSDeclaring Records How to identify documents as recordsProtecting Records How to control what happens to “records”Developing File Plans How to specify controls for many record types in one place BEST PRACTICES CONFERENCE SHAREPOINT

Declaring Records in MOSS 2007“Declaration” = “Send to Repository” Limited UX “Send To…” link on ECB 1 Records Center per Farm Complex Data Flow Required coordination between source content type and target routing type (record series) BEST PRACTICES CONFERENCE SHAREPOINT

MOSS Record Declaration BEST PRACTICES CONFERENCE SHAREPOINT

Protecting Records in MOSS 2007“Protection” = “Send to Repository” Access control based on access to records center Retention rules defined in separate policies for records center (site collection) BEST PRACTICES CONFERENCE SHAREPOINT

File Planning in MOSS 2007“File Plan” = “Routing Table” No Hierarchy, only DocLib folders No metadata inheritance from folders No ability to attach rules to folders Except via custom folder content types No ability to route to folders Except with custom routers BEST PRACTICES CONFERENCE SHAREPOINT

Key Features for RM in 2010 Document ID Service Content Type Syndication Centralized Taxonomy Management Content Organizer for Routing Hierarchical File Plans Multi-Stage Retention Policies “In Place” Record DeclarationNew Features in 2010 BEST PRACTICES CONFERENCE SHAREPOINT

DocumentIdentifiersBEST PRACTICES CONFERENCE SHAREPOINT

Document Identifiers Every document can have a unique ID Ability to reference documents by ID Ability to move docs without breaking links Scoped to Site Collection (docid feature) Adds “Document ID” field to documents Need to checkout/checkin existing docs to get an ID Example DOCID reference: http://<site collection url>/ _layouts/DocIdRedir.aspx?ID=<doc id>Unique Document IDs BEST PRACTICES CONFERENCE SHAREPOINT

Content TypeSyndication BEST PRACTICES CONFERENCE SHAREPOINT

Content Type Enhancements Global Content Types Available throughout the Farm Can control how they are published Can be used for content organizer rules Important for Records Management Consistent metadata across many sitesContent Type Syndication BEST PRACTICES CONFERENCE SHAREPOINT

Centralized Taxonomy Management (related to content types) Features Add new “Managed Metadata” column Use centralized Term Store to create and manage “Term Sets” Supports hierarchical taxonomies Supports synonyms for terms JAX == JacksonvilleCentral Term Store BEST PRACTICES CONFERENCE SHAREPOINT

The ContentOrganizerBEST PRACTICES CONFERENCE SHAREPOINT

New Concept:Content Organizer Records Center Property = Value? Folder Incoming Content Documents Type Match? Custom Library Rules BEST PRACTICES CONFERENCE SHAREPOINT

Content Organizer Metadata-driven Routing Automatically handles incoming records (no need for custom router) Target destination determined from metadata (configured using rules) Support for file plan hierarchy Can target subfolders of destination library Automatically applies policies associated with target locationContent Organizer BEST PRACTICES CONFERENCE SHAREPOINT

SP2010 Records Center BEST PRACTICES CONFERENCE SHAREPOINT

Content Organizer Rules BEST PRACTICES CONFERENCE SHAREPOINT

Send to Site Configure target sites in site settings Target sites must have Content Organizer feature activated Select target sites in Content Organizer Overcomes “single records repository” problem Target sites can have their own routing rulesContent Organizer BEST PRACTICES CONFERENCE SHAREPOINT

Folder Partitioning Can pre-specify maximum number of items per container Automatically create a new folder when (n + 1)th item is added Automatically notify user of new location with hyperlink to the resulting URL Can specify a custom naming scheme for new folders added this way “Items Uploaded After <date>”Content Organizer BEST PRACTICES CONFERENCE SHAREPOINT

Preserving Context Can keep original audit entries and properties with the document after it is routed Easy to view “history” of original document Easy to compare “state” of original documentContent Organizer BEST PRACTICES CONFERENCE SHAREPOINT

Handling Duplicates Can specify what to do if an incoming document has the same name as an existing document Create a new version Append a unique identifierContent Organizer BEST PRACTICES CONFERENCE SHAREPOINT

Permissions Designate users as “Rule Managers” Need this permission to create and edit organizer rules Also requires Manage Web Site permission Notified if documents remain in drop off library after rules have been applied Can specify how long before email is sent Documents still in library after N daysContent Organizer BEST PRACTICES CONFERENCE SHAREPOINT

Hierarchical File Plans “File Plan” = “Content Organizer” Routes documents based on metadata “Hierarchy” = “Folder” Can target folders from CO rules Can be used anywhere Not just in the Records CenterContent Organizer BEST PRACTICES CONFERENCE SHAREPOINT

Content Organizer: ObservationsDealing with the Classification Issue Records Managers like Taxonomies End Users like Folksonomies Managed Metadata to the rescueBuilding a “classification pipeline” “Funnel” documents towards proper declaration using a series of content organizer rules attached to separate sites BEST PRACTICES CONFERENCE SHAREPOINT

Document RetentionBEST PRACTICES CONFERENCE SHAREPOINT

Document Retention Implemented via Information Policy Can be applied to any document (not just records) Perform actions at end of retention period Actions can include record declarationDocument Retention BEST PRACTICES CONFERENCE SHAREPOINT

Multi-Stage Retention Missing from SP2007 Enables modeling of real-world scenarios Stages are “activated” based on conditions Stages can recur automatically until the „next‟ stage is activated Example: Perform annual review of invoices (recurring), then purge after 3 yearsDocument Retention BEST PRACTICES CONFERENCE SHAREPOINT

InformationPolicy:RetentionStages BEST PRACTICES CONFERENCE SHAREPOINT

Virtual Folders for e-Discovery SharePoint 2007 Best Practice: “Use Metadata, Not Folders” SharePoint 2010 Best Practice: “Use Folders, Inherit Metadata” Virtual Folders provide support for metadata-driven navigation Easy to setup multiple “views” of a records center independent of metadata used for routing & classificationVirtual Folders BEST PRACTICES CONFERENCE SHAREPOINT

In-Place Records Management“Records Management for Active Documents” – but what does it mean? 1. Special handling for declared records Control over who can edit/delete records Apply different retention policy for declared records 2. Programmatic control over record declaration 1. Declare records in response to a user action 2. Declare records from a workflow activity BEST PRACTICES CONFERENCE SHAREPOINT

In-Place Records: CaveatCannot Utilize Location-Based Features: Cannot assign records to file plan folders Records don‟t actually “move” Cannot inherit rules + permissions from folder as specified by file planCannot Invoke Content Organizer Rules Cannot trap record declaration event to modify metadata or move the record BEST PRACTICES CONFERENCE SHAREPOINT

In-Place “Recordization” in General“Manage In Place” in ECM literature Ability to create and manage (file plan + retention rules + permissions) in one place => EDRMS Ability to create associations between EDRMS components and individual documents or folders Ability to apply EDRMS components to documents and folders (rules), and lock them down without moving them BEST PRACTICES CONFERENCE SHAREPOINT

In-Place RM Feature ActivationIn-Place Records BEST PRACTICES CONFERENCE SHAREPOINT

Record Declaration SettingsIn-Place Records BEST PRACTICES CONFERENCE SHAREPOINT

RecordDeclarationIn-Place Records BEST PRACTICES CONFERENCE SHAREPOINT

Legal Holds Tied to Search New “Search and Add Holds” Page Use search criteria to locate documents Use search results to perform actions Examples: copy to a new location mark as read only Can be applied to any type of content Can have multiple holds for a site Use Excel to get holds reportLegal Holds BEST PRACTICES CONFERENCE SHAREPOINT

Search and Add to HoldLegal Holds BEST PRACTICES CONFERENCE SHAREPOINT

Enhanced Reporting Can use Excel to generate reports: Documents declared as records Documents associated with holdsReporting BEST PRACTICES CONFERENCE SHAREPOINT

Records Repository Scalability No (technical) Need for External Storage 10s of Millions of documents in a single Records Center 100s of Millions of documents in a distributed repository May still need an external storage solution to manage total cost of ownership (TCO) Records become less active over time Makes sense to offload to less expensive mediaStorage/Scalability BEST PRACTICES CONFERENCE SHAREPOINT

Email Records Management Designed for Exchange 2010 Integrated Email Archiving Integrated Email Retention Integrated Email Discovery Can use Content Organizer for Email Recommended only for Records Center Avoid inconsistency/complexity Avoid bottlenecks/bandwidth issuesEmail Records BEST PRACTICES CONFERENCE SHAREPOINT

Enabling Email ProcessingFrom PowerShell Enable-SPFeature –id EmailRouting –url “<site url>”Creates a separate list to receive emails Assigns a unique email address Creates a built-in content type for emails “E-mail Submission” Pre-defined fields common to emails BEST PRACTICES CONFERENCE SHAREPOINT

SummarySharePoint 2010 improves traditional RM byproviding better support for common tasks.New features in SharePoint 2010 further enhancethe RM story by making it easier to organizecontent and manage metadata.In-Place records management means richer andmore intuitive UX for records managers and endusers. BEST PRACTICES CONFERENCE SHAREPOINT

For More Information Visit my blog: www.SharePointArchitects.us/johnholliday Thank you! BEST PRACTICES CONFERENCE SHAREPOINT

IW403 Records Management Improvements in SharePoint 2010

by John F. Holliday on Apr 17, 2011

Accessibility

Categories

Tags

Upload Details

Usage Rights

2 Embeds 85

Statistics

IW403 Records Management Improvements in SharePoint 2010 — Presentation Transcript

http://www.sharepointarchitects.us	79
http://localhost	6