23. Site Columns
Site Beta
List Columns
Site Alpha
Content Types are made of site columns.
List A
Fruit:
• Bananas
• Grapes
• Apples
List B
Fruit:
• Plantains
• Wine
• Applesauce
Fruit:
• Bananas
• Grapes
• Apples
List A
List C
List D
List B
24.
25.
26. Click the “Site Actions” button
Then, click “Site Settings” at the bottom
of the drop down menu.
27. Click “Site Columns” under “Galleries”
This is the Site Column
Gallery.
Click “Create.”
32. We’ve
created a List
Content Type,
now let’s make
a Library
Content Type!
Ifyouchosea“Document“ContentType,
(whichis1ofthe2mostwidelyusedParent
ContentTypesinSharePoint)youcanattacha
documenttoit.
Click“AdvancedSettings.”
36. Laura Roger’s blog: Content Types as Statuses
http://www.sharepoint911.com/blogs/laura/Lists/Posts/Post.aspx?List=676af157%
2D7d96%2D4e15%2Da987%2D54b8a3e4d948&ID=49
Sarah Haase: Content Types for Edit Forms
http://sarahlhaase.wordpress.com/2011/03/21/using-content-types-to-modify-
the-newform-aspx-and-editform-aspx-pages/
MSDN Blogs: Document Content Types-
http://blogs.msdn.com/b/martinkearn/archive/2006/03/27/561809.aspx
MSDN Blogs: Best Practices and in-depth overview-
http://msdn.microsoft.com/en-us/library/ee330223(v=office.12).aspx
Kelly Rusk: Content Type Best Practices
http://blog.concurrency.com/sharepoint/sharepoint-2010-basics-content-types-
and-site-columns/
Some additional Content Type Resources
38. Library Purpose
Library in a team site Collaboration; easy sharing of content among peers; content control, such as
versioning; SharePoint Server searching.
Library in a portal area Content that is intended for a wider audience in the organization; similar to a
library in a team site, but typically implemented with a more-stringent review
and approval process.
Library in a Document
Center site
A large-scale library useful as an enterprise knowledge base or historical
archive; includes features to help users navigate, search, and manage a large
number of documents in a deep hierarchy by using a set of specialized Web
Parts.
Documents Purpose Author Users Format
Engagement ideas
and requests
Develop new customer
engagements
Project leader Sales
manager;
project
leader
.doc
Proposals Describe a proposed
customer engagement
Project leader Project
managers;
project
team
members;
customers
.doc
Contracts Commit to a consulting
engagement
Lawyer Project
leader;
project
manager;
sales
manager;
customers
.doc
43. User entry in
DIP populates
control in
Office doc
template
Build
standardized file
names by
concatenating
metadata
As shown, the
DIP can be quite
simple, or can be
very robust,
depending on the
needs of a
particular
content type
47. Kind of record Record category Description
Benefit plans, insurance
plans, pension plans
Employee Benefit
Descriptions
Descriptions of all employee
benefit plans.
Payroll timesheets,
supplementary payroll
information
Payroll Records Summaries of hours
worked, overtime, and
salary paid.
Vendor invoices Invoices Records of goods or
services purchased from
vendors.
Product surveys,
questionnaires, training
manuals, training videos
Training Materials Provides internal or external
training.
...
Records Description Media
Record
category Retention Disposition Contact
401k plans Description
of employee
benefit plan.
Web pages Employee
Benefit Plans
X years None Kathi Flood
Insurance
plans
Description
of employee
insurance
plan.
Print Employee
Benefit Plans
X years None Reshma
Patel
Pension
plans
Description
of employee
pension
plan.
Print Employee
Benefit Plans
X years None Reshma
Patel
...
I. Shared Taxonomy
Using the Taxonomy Term Store information is easier to find, share, reuse and repurpose. This is because it combines corporate taxonomy with social navigators to store as much context around information as possible.
A. Social Navigators
Find content based on (people or information?) relationships
Find content based on ratings provided by site users
Find content based on end users tagging content (folksonomy)
B. Taxonomy Term Store
Central service for provisioning taxonomy across Farms and Site Collections
One or more Managed Metadata Services can be consumed
Manage multiple taxonomies in a single service
Support for multilingual terms – Language can be picked up from browser local
C. Manage Terms as Taxonomy Needs Change
Support for synonyms
Support for open and closed terms sets – being able to add content or not – can specify permissions based on term set
Easy to manage over time (copy, move, merge, delete, deprecate)
Integrated with the social store – Can manage the social store as a “term set”