70-488 Content Type Inheritance

In this article we can explore Content Type Inheritance, its advantages and example.

Content Type Inheritance

Content Type Inheritance allows creation of new content type from an existing one. This allows reusing of existing content type & metadata columns.

Advantages

Following are the advantages of Content Type Inheritance:

1. Reusability

2. Maintainability

Base Content Type

The Base Content Type is System of ID 0x. All the content types will be inheriting from System as the ultimate parent.

Creating an Inherited Content Type

Now we can try creating an inherited content type. In this expense submission scenario, we are trying to create a content type that inherits from Document. We will be adding additional metadata columns for capturing Amount.

Choose Site Settings > Site content types page > Create option.

Enter Name for the content type & Select the Parent Content Type as Document. Click OK button to continue. In the appearing page choose Add from new site column.

Enter the name of the column as Amount and type as Currency.

Click OK button to continue. Now you can attach the content type to a document library.

Create a Document Library and choose Library Settings > Advanced Settings > Allow management of content types > Yes > Click Ok

Again choose Library Settings page & you should be able to see the content types section. Choose the following option.

In the page choose Custom Content Types and add our Expense Content Type to the add box. Click OK button to continue.

Now try to add a new document to the library. Choose the Expense Content Type from the drop down and you will be able to see the Amount column as shown below.

References

http://blogs.msdn.com/b/eigilm/archive/2007/09/04/inherit-content-types.aspx

Summary

In this article we have explored content type inheritance, advantages and example.

70-488 Module1 – Mange the Site Life Cycle

This is part of preparation-series for 70-488.

Topics

Following are the topics:

1. Create a delayed site collection

2. Manage site collection disposition

3. Identify inactive site collections

4. Backup and archive site collection data

Create a Delayed Site Collection

Delayed Site Collection is a Site Collection created but the Template will be chosen later. For creating a delayed site collection, open Central Administration > Create site collections > Custom tab as shown below.

Wait for the site collection to be created & Open it in a new window. You can see the site asks for template.

This is good for Administrators where a Site Collection request comes in without specifying the template.

Managing Site Collection Disposition

Site Collection Disposition deals with Closing & Deletion of site. Closing is the process of preventing site collection from access. Deletion removes the site collection.

We can create a Policy to achieve the same. Open Site Settings > Site Policies page.

You will get the following page.

Click the Create button to create a new policy.

In the appearing page enter the following:

1. Name for the policy

2. Close and Delete functionality

Save changes & your new policy is created.

In the above example, I have selected 1 year from creation date to close the site. Plus, 1 month for deletion from closing date. SharePoint internal timer jobs will be carrying out these tasks and appropriate email notifications will be sent.

It is a good habit to associate Disposition policy on site collection creation. This will ensure unused or irrelevant data being occupying content database & search results.

Identify Inactive Site Collections

To identify inactive site collections, we can use PowerShell script. We can use the SPSite.LastContentModifiedDate property to find obsolete site collections.

Following is the PowerShell script:

Add-PSSnapIn -Name Microsoft.SharePoint.PowerShell

$farm = [Microsoft.SharePoint.Administration.SPFarm]::Local

$websvcs = $farm.Services | where -FilterScript {$_.GetType() -eq [Microsoft.SharePoint.Administration.SPWebService]}

foreach ($websvc in $websvcs)

{

foreach ($webapp in $websvc.WebApplications)

{

foreach ($site in $webapp.Sites)

{

echo $site.HostName $site.Url $site.LastContentModifiedDate $site.ContentDatabase.Name $site.WebApplication.Name

}

}

}

The PowerShell script is available at:

http://www.sharepointcto.com/PowerShell/PowerShell.aspx

Backup and Archive Site Collection Data

Backing up a Site Collection is possible in following ways:

1. Backup through Central Administration

2. Backup through PowerShell

Following is the Backup through Central Administration.

Choose the Perform a site collection backup link item.

The backup process will be initiated in the background.

Archival is the process of storing data for historical purpose & preventing changing of content. Although SharePoint 2013 does not allow any direct-archival mechanisms, we can employ the following methods to achieve it.

1. Use Close policy

2. Move site collection to another location

Archival also ensures the content is not visible in any Search.

References

http://technet.microsoft.com/en-us/library/jj219569(v=office.15).aspx

Summary

In this article we have explored managing site life cycle.