IT tutorials
 
Technology
 

Sharepoint 2010 : Enterprise Content Management - Hierarchical File Plans and Folder-Based Retention, Records Center

10/8/2013 9:01:54 PM
- Free product key for windows 10
- Free Product Key for Microsoft office 365
- Malwarebytes Premium 3.7.1 Serial Keys (LifeTime) 2019

1. Hierarchical File Plans and Folder-Based Retention

The reality is that usually the amount of content and categories of content generated in a typical organization will require a better manageability of retention policies. For instance, the policies would sound something like this: "If this e-mail is more than six months old, go ahead and archive it, but if the CEO sent it, don't archive it." This sounds very much like the ability to set retention policies and then be able to override certain retention policies under special conditions.

So think of it this way: if you were managing e-mail or documents, then based on sender or creator of the document, the content could be routed to an appropriate document library. Even better, if you had a centralized place for managing all records, the document could be routed to an appropriate folder. Thus, there could be a folder called Documents that are Records, but if the CEO created such a document, you could have a subfolder called CEO's Documents. Then by using appropriate content organizer rules, you could theoretically route the documents to the appropriate location. This is the beginning of the formation of your hierarchical file plan!

Now, wouldn't it be nice if in this file plan you could apply hierarchical retention policies? And that you can! Usually you would take such an approach in a records center or centralized records management, but nothing stops you from using this feature right inside your site collections. Simply activate the Library and Folder Based Retention feature at the site collection level and then visit the MyDox document library you created earlier. Under MyDox, create a folder called Child, put some documents in it, and create a folder called GrandChild and put some documents in it, too. Now, go into the information management policy settings of the MyDox document library, and you should see Library Based Retention Schedule option. This can be seen in Figure 1.

Figure 1. Specifying retention schedules on a document library

On this screen, choose to change source for the retention for this document library. You will be able to change the retention policy source from content types to library and folders. By changing the retention source to Library and Folders, you will now be able to add retention stages at the library level. Go ahead and add a retention schedule specifying that if a document has a created date > 1 year, it is moved to the Recycle bin (see Figure 2).

Figure 2. Specifying a retention policy

Now, I'd like to draw your attention to the left side of the preceding figure You can see the folder structure shown as a tree view! Hmm, I wonder what happens if I click the Child folder? The UI changes to that shown in Figure 3.

Figure 3. Children inherit retention policies from the parent

By default, child folders inherit from the parent's retention policies, but you have the ability to configure retention stages at the child level different from the parent. This is referred to as a hierarchical file plan and retention policies specified in your hierarchical file plan.

One final thing I'd like to mention before I shift my focus to the Records Center is the availability of a list definition called Records Library that has automatic records declaration and such relevant features preconfigured for you. Go ahead and create a list based on the Records Library and examine its facilities. You will find that it is simply a document library with automatic declaration of records turned on, among other things.

2. Records Center

The Records Center is a site that puts together all the features I described previously as a single site. It is available to create as a child site or as a site collection. But in order to be able to create the Records Center as a child site, you must activate the content organizer features first. Whether you create the Records Center as a site or as a site collection, the feature set is the same. But what creating the Records Center as its own site collection does give you is the ability to segregate that site collection as its own content database and thus be able to use RBS capabilities of SharePoint to store all those documents in an alternate storage. Believe me, you will need it.

Through central administration, create a site collection based on the Records Center template called Records at /sites/Records. When you create the Records Center you will notice the following:

  • This is a site collection with the content organizer turned on. There is a Drop Off Library and you can set up various content organizer rules to route the documents accordingly.

  • There is a records library created for you.

  • There is a facility to submit new records or to query for an existing record using the unique document ID facilities in SharePoint.

  • You will find a custom action under site settings called Manage Records Center that takes you to a page at http://sp2010/sites/Records/rcconsole.aspx. This page puts together all the convenient facilities in a SharePoint records center , activated as individual features.

The Records Center is intended to be that gargantuan centralized location where all records for the organization are ingested. There is another site definition called the Document Center.
 
Others
 
- Sharepoint 2010 : Enterprise Content Management - In-Place Records Management
- Sharepoint 2010 : Enterprise Content Management - Enterprise Content Types
- Sharepoint 2010 : Enterprise Content Management - Content Organizer
- Sharepoint 2010 : Enterprise Content Management - Managed Metadata, Keywords and Tags
- Windows 8 : Managing BitLocker Drive Encryption (part 4) - Managing and Troubleshooting BitLocker
- Windows 8 : Managing BitLocker Drive Encryption (part 3) - Enabling BitLocker on System Volumes
- Windows 8 : Managing BitLocker Drive Encryption (part 2) - Enabling BitLocker on USB Flash Drives
- Windows 8 : Managing BitLocker Drive Encryption (part 1) - Enabling BitLocker on Nonsystem Volumes
- Windows Server 2012 : Continuous availability (part 8) - Easy conversion between installation options
- Windows Server 2012 : Continuous availability (part 8) - Windows NIC Teaming
 
 
Top 10
 
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 2) - Wireframes,Legends
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 1) - Swimlanes
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Formatting and sizing lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Adding shapes to lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Sizing containers
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 3) - The Other Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 2) - The Data Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 1) - The Format Properties of a Control
- Microsoft Access 2010 : Form Properties and Why Should You Use Them - Working with the Properties Window
- Microsoft Visio 2013 : Using the Organization Chart Wizard with new data
Technology FAQ
- Is possible to just to use a wireless router to extend wireless access to wireless access points?
- Ruby - Insert Struct to MySql
- how to find my Symantec pcAnywhere serial number
- About direct X / Open GL issue
- How to determine eclipse version?
- What SAN cert Exchange 2010 for UM, OA?
- How do I populate a SQL Express table from Excel file?
- code for express check out with Paypal.
- Problem with Templated User Control
- ShellExecute SW_HIDE
programming4us programming4us