Logo 
Search:

Sharepoint 2010 Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint 2010       RSS Feeds

Benefits of Content Types vs List Template in SharePoint 2007?

  Date: Sep 17    Category: Sharepoint 2010    Views: 722

What are the benefits of using a content type over a list template?

Share: 

 

2 Answers Found

 
Answer #1    Answered On: Sep 17    

One example I like to use to explain the use of content types is a
company letterhead. Let's say you create a content type at the root of
your collection (or, in 2010, the content type hub) that contains the
basic Word document letterhead with the CEO's name on it. If each
department of the company (that is to say, each subsite of the
collection) subscribes to that content type, then everyone can use that
one base letterhead word template.

Let's say the CEO is tired of making eleventy-bajillion dollars a year
and quits. The new CEO is hired and now the letterhead needs to be
changed. If everyone just had a copy of the letterhead in their site,
which is the conceptualization of the list template, then when you
wanted to change the letterhead (the template) you would have to go to
each site and alter it by hand. Once or twice is easy but hundreds of
times may become annoying.

Instead, luckily, you created it as a content type. You would go to the
top-level content type and modify it one time. You could then push those
changes, using the almighty checkbox for pushing the changes down to
every site that inherits that content type, and everyone immediately has
the new letterhead template.

 
Answer #2    Answered On: Sep 17    

SharePoint standard terminology is often

- not very helpful

- in allowing people to understand or relate

- the different parts of SharePoint to each other.

---
A *content type* and a *list template*

- are not really comparable things.

- you would not really decide to use one or the other.

- in fact any *list template* will contain / use

- one or more *content type*
---

The following brief explanation may help ...

---
Each *content type* is really

- a named *item type (definition)*

o that you can create

- to "model" a generic type of information "thing"

o that is used in your day-to-day business

Here are names of some possible *content type*

- standard customer letter

- internal memo

- customer contact details

- task

- issue

- weekly report

Each would have an *item type (definition)*

For a specific *list (instance)* that you have created / evolved

- to the point that you consider it is a "very useful" list and

- that you want to be able to create other lists just like it

- it can be saved as a named *list (template)*

The named *list (template)*

- will include each *item type (definition)*

- that was contained in the *list (instance)*

You still need to understand how a *content type* i.e.

- a named *item type (definition)*

- can help you build a good solution

- to meet your business requirements

Kristopher provided one example.

There are many aspects to a *content type*

- suggest you search on-line for some basic videos

- that will walk you through aspects of a *content type*

 




Tagged: