microsoft office sharepoint server...

Microsoft Office SharePoint Server 2007

Microsoft Office SharePoint Server 2007Information Architecture

Microsoft Office SharePoint Server 2007 Information Architecture

Prepared by

Microsoft

Version 1.0.0.0 Baseline

First published

17 March 2008

Copyright

This document and/or software (“this Content”) has been created in partnership with the National Health Service (NHS) in EnglRights to this Content are jointly owned by Microsoft and the NHS in England, although both Microsoft and the NHS are entitled to independently exertheir rights of ownership. Microsoft acknowledges the contribution of the NHS in England through their Common User Interface Readers are referred to www.cui.nhs.uk for further information on the NHS CUI Programme.

All trademarks are the property of their respective companies. Microsoft and Windows are either registerCorporation in the United States and/or other countries.

© Microsoft Corporation and Crown Copyright 2008

Disclaimer

At the time of writing this document, Web sites are referenced using active hyperlinks to the correct Web page. Due to the dytime, these links may become invalid. Microsoft is not responsible for the content of external Intern

The example companies, organisations, products, domain names, eassociation with any real company, organisation, product, domain name, e

Microsoft Office SharePoint Server 2007Version 1.0.0.0

This document and/or software (“this Content”) has been created in partnership with the National Health Service (NHS) in Englare jointly owned by Microsoft and the NHS in England, although both Microsoft and the NHS are entitled to independently exer

their rights of ownership. Microsoft acknowledges the contribution of the NHS in England through their Common User Interface for further information on the NHS CUI Programme.

All trademarks are the property of their respective companies. Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

Crown Copyright 2008

At the time of writing this document, Web sites are referenced using active hyperlinks to the correct Web page. Due to the dytime, these links may become invalid. Microsoft is not responsible for the content of external Internet sites.

The example companies, organisations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious. No association with any real company, organisation, product, domain name, e-mail address, logo, person, places, or events is intended or should be inferred.

Microsoft Office SharePoint Server 2007 Information Architecture 1.0.0.0 Baseline

Prepared by Microsoft

This document and/or software (“this Content”) has been created in partnership with the National Health Service (NHS) in England. Intellectual Property are jointly owned by Microsoft and the NHS in England, although both Microsoft and the NHS are entitled to independently exercise

their rights of ownership. Microsoft acknowledges the contribution of the NHS in England through their Common User Interface programme to this Content.

ed trademarks or trademarks of Microsoft

At the time of writing this document, Web sites are referenced using active hyperlinks to the correct Web page. Due to the dynamic nature of Web sites, in

mail addresses, logos, people, places, and events depicted herein are fictitious. No on, places, or events is intended or should be inferred.

Page ii


TABLE OF CONTENTS

1 Introduction ................................

1.1 What is Information Architecture?

1.2 Why Information Architecture is Important

1.3 Value Proposition ................................

1.4 Assumptions ................................

1.5 Prerequisites ................................

1.5.1 Knowledge Prerequisites

1.5.2 Infrastructure Prerequisites

1.6 Audience ................................

2 Using This Document ................................

2.1 Document Structure ................................

2.2 Getting Started ................................

3 Plan ................................................................

3.1 Plan and Design Site Hierarchy

3.1.1 Organisational Unit ................................

3.1.2 Topics ................................

3.1.3 Personalised Views

3.1.4 Projects ................................

3.1.5 Recommendations ................................

3.2 Plan the Structure of Site Collections and Sites

3.2.1 The Benefits of Using Site Collections

3.2.2 Site Collection Structure

3.2.3 Recommended Site Name and Purpose

3.3 Plan and Design Web Pages

3.3.1 Master Pages ................................

3.3.2 Content Pages ................................

3.3.3 Layout Pages ................................

3.4 Plan and Design Navigation

3.4.1 Global, Current and Breadcrumb Navigation

3.4.2 Web Parts and Navigation Controls

3.4.3 Recommendations ................................

3.5 Plan and Design Content Authoring and Approval

3.5.1 Content Authoring and Approval Process

3.5.2 Where and How Content Can Appear

3.6 Plan Audiences ................................

3.6.1 Key Audiences ................................

3.6.2 Content Targeting to Audiences

3.7 Plan Document Taxonomy and Metadata


ONTENTS

................................................................................................................................

What is Information Architecture? ................................................................

Why Information Architecture is Important ................................................................

................................................................................................

................................................................................................

................................................................................................

Knowledge Prerequisites ................................................................................................

Infrastructure Prerequisites ................................................................................................

................................................................................................................................

................................................................................................

................................................................................................

................................................................................................

................................................................................................

Plan and Design Site Hierarchy ................................................................................................

................................................................................................

................................................................................................................................

................................................................................................

................................................................................................

................................................................................................

Plan the Structure of Site Collections and Sites ................................................................

The Benefits of Using Site Collections ................................................................

Site Collection Structure ................................................................................................

Recommended Site Name and Purpose ................................................................

Plan and Design Web Pages ................................................................................................

................................................................................................

................................................................................................

................................................................................................

esign Navigation ................................................................................................

Global, Current and Breadcrumb Navigation ................................................................

Web Parts and Navigation Controls ................................................................

................................................................................................

nd Design Content Authoring and Approval ................................................................

Content Authoring and Approval Process ................................................................

Where and How Content Can Appear ................................................................

................................................................................................

................................................................................................

Content Targeting to Audiences ................................................................

Plan Document Taxonomy and Metadata ................................................................


Page iii

.................................... 1

............................................................ 1

............................................... 2

...................................................... 2

............................................................. 3

............................................................. 3

.................................... 3

................................. 3

................................... 3

.................................................... 4

.................................................. 4

.......................................................... 5

................................................. 7

................................ 8

.............................................. 8

.................................. 8

............................................. 9

............................................................... 9

.............................................. 9

....................................... 9

.............................................. 11

.................................... 11

.......................................... 12

.................................. 13

.................................................... 14

................................................... 16

.................................................... 18

................................... 20

.................................... 21

.................................................. 23

............................................ 25

................................. 25

......................................... 26

.............................................. 26

....................................................... 27

.................................................. 27

........................................................ 28

.............................................. 30


3.7.1 Recording Stakeholders and Existing Documents

3.7.2 Planning Document Libraries

3.7.3 Planning Metadata and Content Types

3.7.4 Properties Integration with the 2007 Office Release

4 Develop ................................

4.1 Create Site Collection ................................

4.2 Develop Site Hierarchy

4.2.1 Add a Category to the Site Directory

4.2.2 Edit a Category in the Site Directory

4.2.3 Remove a Category from the Site Directory

4.2.4 Create Subsite ................................

4.2.5 Other Ways to Create Sites

4.2.6 Delete Subsite ................................

4.2.7 Edit Sites in the Site Directory

4.2.8 Approve or Reject Sites from the Site Directory

4.2.9 Remove a Site from the Site Directory

4.2.10 Configure Site Directory Settings

4.3 Develop Navigation................................

4.3.1 Global Navigation ................................

4.3.2 Current Navigation ................................

4.3.3 Breadcrumb Navigation

4.3.4 Web Parts ................................

4.4 Develop Web Pages ................................

4.4.1 Master Pages ................................

4.4.2 Content Pages ................................

4.4.3 Page Layouts ................................

4.5 Develop Document Libraries

4.5.1 Create a Document Library

4.5.2 Configure Approval................................

4.5.3 Configure Check-Out

4.5.4 Configure Versioning

4.5.5 Configure Information Rights Management

4.6 Develop Content Types

4.6.1 Create a Custom Document Content Type

4.6.2 Create Columns for the New Custom Content Type

4.6.3 Associate a Content Type with a Document Library

4.6.4 Implement and Update a Document Template

4.7 Develop Audiences ................................

4.7.1 Import Profiles ................................

4.7.2 Create an Audience

4.7.3 Target Content ................................

5 Stabilise ................................


Recording Stakeholders and Existing Documents ................................

Planning Document Libraries ................................................................

Planning Metadata and Content Types ................................................................

Properties Integration with the 2007 Office Release ................................

................................................................................................................................

................................................................................................

................................................................................................

Add a Category to the Site Directory................................................................

Edit a Category in the Site Directory ................................................................

Remove a Category from the Site Directory ................................................................

................................................................................................

Other Ways to Create Sites ..............................................................................................

................................................................................................

Edit Sites in the Site Directory ................................................................

Approve or Reject Sites from the Site Directory ...............................................................

ite from the Site Directory ................................................................

Configure Site Directory Settings ................................................................

................................................................................................

................................................................................................

................................................................................................

Breadcrumb Navigation ................................................................................................

................................................................................................

................................................................................................

................................................................................................

................................................................................................

................................................................................................

Develop Document Libraries ................................................................................................

Create a Document Library ...............................................................................................

................................................................................................

Out ................................................................................................

Configure Versioning ................................................................................................

Configure Information Rights Management ................................................................

Develop Content Types ................................................................................................

Create a Custom Document Content Type ................................................................

Create Columns for the New Custom Content Type ................................

Associate a Content Type with a Document Library ................................

Implement and Update a Document Template ................................................................

................................................................................................

................................................................................................

Create an Audience ................................................................................................

................................................................................................

................................................................................................................................


Page iv

............................................................ 30

............................................................ 31

............................................. 33

......................................................... 37

......................................... 39

............................................. 40

........................................... 42

................................................. 42

................................................. 44

..................................... 45

................................................... 46

.............................. 49

................................................... 50

........................................................... 50

............................... 52

.............................................. 52

.................................................. 53

................................................. 54

.............................................. 54

............................................ 58

..................................... 62

.......................................................... 64

............................................... 73

.................................................... 73

................................................... 82

.................................................... 83

.................................. 87

............................... 87

............................................ 89

........................................ 90

......................................... 90

...................................... 91

.......................................... 92

....................................... 92

......................................................... 94

......................................................... 95

................................. 96

............................................... 100

................................................. 100

........................................ 101

................................................ 102

...................................... 107


5.1 Testing Considerations

5.2 Using Test Computers ................................

5.3 Test Procedures ................................

5.4 Supporting Documents

6 Deploy ................................

6.1 Backup and Restore ................................

6.1.1 Backup ................................

6.1.2 Restore ................................

6.2 Other Migration Tools ................................

APPENDIX A Templates ................................

APPENDIX B Other Resources

APPENDIX C Document Information


................................................................................................

................................................................................................

................................................................................................

................................................................................................

................................................................................................................................

................................................................................................

............................................................................................................................

............................................................................................................................

................................................................................................

................................................................................................

Other Resources ................................................................................................

Document Information ............................................................................................


Page v

......................................... 107

.......................................... 108

................................................... 108

......................................... 109

......................................... 110

............................................. 111

............................ 111

............................ 112

........................................... 114

................................................ 115

..................................... 118

............................ 119


1 INTRODUCTION

This guidance has been created to assist choice when planning, designingon Microsoft® Office SharePointof this document is to provide guidance on:

� The meaning of an information architecture in the context of the Microsoft Office system.

� The planning and design and the Microsoft Office

� The development and within a 2007 Office system environment.

This document should be used in conjunction with the Sample Data1 workbook and Informworksheets aid the planning, designarchitecture and are referred to throughout this document.

The following information is out of scope of this

� Recommendation of a specific information architecture for use by

� Recommendation of specific site and document

� Detailed recommendations on the use of workflows, information management policies, server field controls and style sheets

� Deployment guidance, including guidance on physical topologies, database design and how to define hardware requirementsOffice SharePoint Server 2007 Deployment Guide

It is recommended that this guide is nproject. This is because the vast majority of this guidance is SharePoint Server 2007 specific.

1.1 What is Information Architecture?Information architecture is a strucinformation is labelled, organised and made available to users. If plannedand adhered to correctly, an information an organisation.

In the context of this guidance, an SharePoint Server 2007 site, including presented. It also includes how content, including documents and records, will be classified and how metadata will be applied to 2007 Office system files, such as Word documents, through document information panels and document placeholders.

1 Information Architecture Worksheets http://www.microsoft.com/industry/healthcare/technology/hpo/knowledgeworker/moss2007informationarchitecture.aspx

2 Information Architecture Worksheets http://www.microsoft.com/industry/healthcare/technology/hpo/knowledgeworker/moss2007informationarchitecture.aspx

3 Microsoft Office SharePoint Server 2007 Deployment Guide http://www.microsoft.com/industry/healthcare/technology/hpo/serverbuild/moss2007deplo


NTRODUCTION

has been created to assist healthcare organisations in making the most appropriate choice when planning, designing, developing and implementing an information architecture based

Office SharePoint® Server 2007 and the 2007 Microsoft® Office systemis to provide guidance on:

The meaning of an information architecture in the context of SharePointsystem.

and design of an information architecture based on SharePoint Server 2007Office system.

development and implementation of a chosen information architecture or taxonomy within a 2007 Office system environment.

This document should be used in conjunction with the Information Architecture Worksheets Information Architecture Worksheets – Empty Workbook

worksheets aid the planning, design, development and implementation of an informationand are referred to throughout this document.

following information is out of scope of this guidance:

ecommendation of a specific information architecture for use by healthcare

ecommendation of specific site and document classifications

Detailed recommendations on the use of workflows, information management policies, controls and style sheets

Deployment guidance, including guidance on physical topologies, database design and how to define hardware requirements. Further guidance on this can be found inOffice SharePoint Server 2007 Deployment Guide3

recommended that this guide is not used if SharePoint Server 2007 is out of scope for the project. This is because the vast majority of this guidance is SharePoint Server 2007 specific.

What is Information Architecture? nformation architecture is a structured conceptual model that represents the way in which information is labelled, organised and made available to users. If planned, developed,

nformation architecture will provide consistency and standards across

In the context of this guidance, an information architecture includes how the information in a site, including Web pages, documents, lists, and data is organised and

d. It also includes how content, including documents and records, will be classified and how metadata will be applied to 2007 Office system files, such as Word documents, through document information panels and document placeholders.

Information Architecture Worksheets – Sample Data {R1}: http://www.microsoft.com/industry/healthcare/technology/hpo/knowledgeworker/moss2007informationarchitecture.aspx

chitecture Worksheets – Empty Workbook {R2}: http://www.microsoft.com/industry/healthcare/technology/hpo/knowledgeworker/moss2007informationarchitecture.aspx

Microsoft Office SharePoint Server 2007 Deployment Guide {R3}: http://www.microsoft.com/industry/healthcare/technology/hpo/serverbuild/moss2007deployment.aspx


Page 1

organisations in making the most appropriate and implementing an information architecture based

system. The objective

SharePoint Server 2007 and

SharePoint Server 2007

implementation of a chosen information architecture or taxonomy

Information Architecture Worksheets – orkbook2.The

an information

healthcare organisations

Detailed recommendations on the use of workflows, information management policies,

Deployment guidance, including guidance on physical topologies, database design and how . Further guidance on this can be found in the Microsoft

if SharePoint Server 2007 is out of scope for the project. This is because the vast majority of this guidance is SharePoint Server 2007 specific.

tured conceptual model that represents the way in which developed, implemented

provide consistency and standards across

rchitecture includes how the information in a pages, documents, lists, and data is organised and

d. It also includes how content, including documents and records, will be classified and how metadata will be applied to 2007 Office system files, such as Word documents, through

http://www.microsoft.com/industry/healthcare/technology/hpo/knowledgeworker/moss2007informationarchitecture.aspx


yment.aspx



http://www.microsoft.com/industry/healthcare/technology/hpo/serverbuild/moss2007deployment.aspx


1.2 Why Information ArchitPlanning, designing and adhering to 2007 and the Microsoft Office system will help ensure the management and information distribution, areterminology across a healthcareusers to find and re-use information easily

SharePoint Server 2007 and the and site collections, which help support the implementation of a well designed information architecture. It is the task of information standards professionals, developers and site designers to ensure these are fully utilised. A successful information architecture project will result in the planning and design of:

� Site hierarchy – How site(s) will be structured and should be recorded in the

� Navigation – How site users will navigate through the site(s)the Plan Navigation worksheet

� Web pages – How data will be presented Plan Master Pages, Plan Content Pages (Article), Plan Content Pages (Welcome), Plan a Page Content Type and

� Content authoring and approvalthe content will go throughThis should be recorded in the Restrictions worksheets

� Personalised contentbe recorded in the Plan Audiences

� Document taxonomy and metadatashould be recorded in the Plan Document Libraries, Plan

The quality of the planning and design of an information architecture will also impact how maintainable and usable SharePoint Server 2007defining appropriate site structures, information they need. Failure to consider these elements during the planning phasefrequent modifications of the SharePoint Server 2007

1.3 Value PropositionThis document will equip a healthcaredesign, develop and implement an appropriate system information architecture. This will:

� Ensure the most productive user experience for the correctly planning, developingarchitecture, users will be able to

� Ensure the most effective management of shared documents and information

� Provide consistency in the way documents and other information

� Assist users in the discovery of existing documents and

� Enable an information architecture to be implemented quickly and effectively according to current best practices.

This guide consolidates the vast amount of public information available on and the Microsoft Office systemorganisation in moving to the Stanardized level of the Business Productivity Infrastructure Optimization (BPIO) model for


Why Information Architecture is Important and adhering to an appropriate information architecture for

Office system will help ensure the operational goals, such as document management and information distribution, are effectively met. For example, using a consistent

healthcare organisation will help facilitate better communications, enable use information easily, and provide the basis for consistent processes.

the 2007 Office system include many features, such as content types and site collections, which help support the implementation of a well designed information

nformation architects, solution architects, IT professtandards professionals, developers and site designers to ensure these are fully utilised. A successful information architecture project will result in the planning and design of:

How site(s) will be structured and divided into a set of subsitesshould be recorded in the Site Classification and Site Structure worksheets

How site users will navigate through the site(s). This should be recorded in worksheet

How data will be presented on the site(s). This should be recorded in the Plan Content Pages (Article), Plan Content Pages (Welcome), Plan a and Plan Layout Pages worksheets

Content authoring and approval – How content will be authored, what approval process the content will go through, and what types of content can appear in specific areas of a site. This should be recorded in the Content Authoring and Approval and Plan Content

worksheets

content – How information will be targeted to groups of usersPlan Audiences worksheet

Document taxonomy and metadata – How documents will be classified and taggedshould be recorded in the Document Management Stakeholder, Analyse Document Usage, Plan Document Libraries, Plan a Document Content Type and Site Columns

The quality of the planning and design of an information architecture will also impact how SharePoint Server 2007 and the Microsoft Office system is. For example,

defining appropriate site structures, Web pages and navigation will ensure users can find the information they need. Failure to consider these elements during the planning phase

SharePoint Server 2007 solution after deployment.

Value Proposition healthcare IT professional with the knowledge to effectively plan,

and implement an appropriate SharePoint Server 2007 and Microsofinformation architecture. This will:

Ensure the most productive user experience for the end users and proposed scenario, developing and implementing the most appropriate information

, users will be able to accomplish their goals with minimal effort.

Ensure the most effective management of shared documents and information

Provide consistency in the way documents and other information are categorised

Assist users in the discovery of existing documents and information.

Enable an information architecture to be implemented quickly and effectively according to .

This guide consolidates the vast amount of public information available on SharePoint Server 2007system information architecture. This document will assist the the Stanardized level of the Business Productivity Infrastructure

Optimization (BPIO) model for the Enterprise Content Management capability.


Page 2

an appropriate information architecture for SharePoint Server goals, such as document

effectively met. For example, using a consistent organisation will help facilitate better communications, enable

and provide the basis for consistent processes.

2007 Office system include many features, such as content types and site collections, which help support the implementation of a well designed information

rchitects, IT professionals, information standards professionals, developers and site designers to ensure these are fully utilised. A successful information architecture project will result in the planning and design of:

divided into a set of subsites. This worksheets

. This should be recorded in

. This should be recorded in the Plan Content Pages (Article), Plan Content Pages (Welcome), Plan a

will be authored, what approval process , and what types of content can appear in specific areas of a site.

Plan Content

How information will be targeted to groups of users. This should

How documents will be classified and tagged. This der, Analyse Document Usage, Site Columns worksheets

The quality of the planning and design of an information architecture will also impact how Office system is. For example,

pages and navigation will ensure users can find the information they need. Failure to consider these elements during the planning phase, will result in

solution after deployment.

IT professional with the knowledge to effectively plan, Microsoft Office

and proposed scenario. By information

accomplish their goals with minimal effort.

Ensure the most effective management of shared documents and information.

categorised.

Enable an information architecture to be implemented quickly and effectively according to

SharePoint Server 2007 This document will assist the healthcare

the Stanardized level of the Business Productivity Infrastructure


1.4 Assumptions Use of this guidance to design and plan a information architecture is based on the assumption that the

� The organisational goals to be achieved by Office system solution.

� The vision and scope of the solution

� The users, or user representatives, that will assist in the planning and design of an appropriate information architecture

1.5 Prerequisites

1.5.1 Knowledge Prerequisites

The reader of this guide should have a and Web based portal solutions. This includes awareness of Office system, as well as an understanding of Experience of designing and planning an information architecture is advantageousessential.

More information on SharePoint Server 20072007 product guide4.

1.5.2 Infrastructure Prerequisites

Two or more server farms should be used to provide separate staging and production environments when planning, developing, stabilising and deploying Where possible, the server farms should be already configured, with each server farm fulfilling one of two roles:

� Staging – The farm contains a site collection (a hierarchical set of sites that can be managed together) that is a copy of the production site collection; so be reviewed and tested before it is published.

� Production – The farm contains the site collection that presents the content to its intended audience, and it usually has tightened security.

Section 6 of this document includes informationa production environment.

1.6 Audience The guidance contained in this document is targeted at organisation:

� Information Architects and information standards professionals

� Solution Architects

� IT professionals, developers and site designers SharePoint Server 2007

4 Microsoft Office SharePoint Server 2007 product guidehttp://office.microsoft.com/en-us/sharepointserver/HA101680161033.aspx

5 Information on deploying and configuring a SharePoint Server 2007 {R5}: http://go.microsoft.com/fwlink/?LinkID=79589


this guidance to design and plan a SharePoint Server 2007 and Microsoftinformation architecture is based on the assumption that the healthcare organisation has defined:

The organisational goals to be achieved by SharePoint Server 2007 and Office system solution.

The vision and scope of the solution, including the business and user requirements.

The users, or user representatives, that will assist in the planning and design of an appropriate information architecture

Knowledge Prerequisites

of this guide should have a basic understanding of rich desktop software applications based portal solutions. This includes awareness of SharePoint Server 2007

as well as an understanding of Web pages, metadata, documents and records. Experience of designing and planning an information architecture is advantageous

SharePoint Server 2007 can be found in Microsoft Office Sh

Infrastructure Prerequisites

should be used to provide separate staging and production when planning, developing, stabilising and deploying SharePoint Server 2007

server farms should be already configured, with each server farm fulfilling one

The farm contains a site collection (a hierarchical set of sites that can be managed together) that is a copy of the production site collection; so that the content can be reviewed and tested before it is published.

The farm contains the site collection that presents the content to its intended audience, and it usually has tightened security.

includes information on migrating content from a staging

The guidance contained in this document is targeted at the following roles within

Information Architects and information standards professionals

IT professionals, developers and site designers who are planning a solution based on SharePoint Server 2007 and the Microsoft Office system.

Microsoft Office SharePoint Server 2007 product guide {R4}: us/sharepointserver/HA101680161033.aspx

nformation on deploying and configuring a SharePoint Server 2007 environment can be found in http://go.microsoft.com/fwlink/?LinkID=79589


Page 3

Microsoft Office system organisation has defined:

and the Microsoft

the business and user requirements.

The users, or user representatives, that will assist in the planning and design of an

basic understanding of rich desktop software applications SharePoint Server 2007 and the 2007

pages, metadata, documents and records. Experience of designing and planning an information architecture is advantageous, but not

Microsoft Office SharePoint Server

should be used to provide separate staging and production SharePoint Server 20075.

server farms should be already configured, with each server farm fulfilling one

The farm contains a site collection (a hierarchical set of sites that can be that the content can

The farm contains the site collection that presents the content to its intended

content from a staging environment to

roles within a healthcare IT

who are planning a solution based on

environment can be found in Deployment for Office

http://office.microsoft.com/en-us/sharepointserver/HA101680161033.aspx

http://technet2.microsoft.com/Office/en-us/library/8a911115-de8a-4cf3-9701-f5ba78fa8bfc1033.mspx?mfr=true


2 USING THIS D

2.1 Document StructureThis document contains four sections that deal with the project lif

� Plan

� Develop

� Stabilise

� Deploy

Each section is based on the Microsoft IT Project Lifecycle as defined in the Microsoft Solutions Framework (MSF) Process Model, and the Microsoft Operations FrLifecycle is described in more detail in Overview7. The MSF Process Model and MOF describe a highbuilding, deploying and managing IT solutionsrange of IT projects.

Plan

Develop

Plan and Design Site Hierarchy

Plan and Design Content

Authoring and Approval

StabiliseTesting

Considerations

DeployBackup and Restore

Develop a Site Collection

Develop Document Libraries

Figure 1: MSF Process Model Phases and Document Structure

6 Microsoft Solutions Framework Core Whitepapershttp://www.microsoft.com/downloads/details.aspx?FamilyID=e481cb0b

7 MOF Executive Overview {R7}: http://www.microsoft.com/technet/itsolutions/cits/mo/mof/mofeo.mspx


DOCUMENT

Document Structure sections that deal with the project lifecycle, as illustrated in

Each section is based on the Microsoft IT Project Lifecycle as defined in the Microsoft Solutions Framework (MSF) Process Model, and the Microsoft Operations Framework (MOF). The IT Project Lifecycle is described in more detail in MSF Process Model Whitepaper6 and MOF Executive

The MSF Process Model and MOF describe a high-level sequence of activities for building, deploying and managing IT solutions and are flexible enough to accommodate a broad


Plan the Structure of Site Collections and

Sites

Plan and Design Web Pages

Plan and Design Navigation



Testing Considerations

Backup and Restore

Other Migration Tools

Plan Audiences

Develop a Site Collection

Develop Site Hierarchy

Develop Navigation Develop Pages

Using Test Computers Test Procedures Supporting

Documents

Plan Document Taxonomy and

Metadata


Develop Content Types

Develop Audiences

: MSF Process Model Phases and Document Structure

s Framework Core Whitepapers {R6}: http://www.microsoft.com/downloads/details.aspx?FamilyID=e481cb0b-ac05-42a6-bab8-fc886956790e&DisplayLang=en

http://www.microsoft.com/technet/itsolutions/cits/mo/mof/mofeo.mspx


Page 4

ecycle, as illustrated in Figure 1:

Each section is based on the Microsoft IT Project Lifecycle as defined in the Microsoft Solutions amework (MOF). The IT Project

MOF Executive level sequence of activities for

flexible enough to accommodate a broad


Develop Pages

Supporting Documents

fc886956790e&DisplayLang=en


http://www.microsoft.com/downloads/details.aspx?FamilyID=e481cb0b-ac05-42a6-bab8-fc886956790e&DisplayLang=en



Note

Although Figure 1 illustrates a sequential series of steps, it is possible to take an iterative approach to development. For example, once site navigation has been planned, it may be appropriate to experiment with creating navigation elements in more thorough planning process.

Within this document, each section considerations. Where appropriate, worksheets Empty Workbook {R2} are referencedconsiderations and assist in planningSharePoint Server 2007 information aworksheets can also be used during and after development to inform future IT professionals, developers, site designers and site completed example of each worksheet has also been made available Architecture Worksheets – Sample Data

2.2 Getting Started Before using this guidance, the fo

1. Define the scope Understand the goals of the project and the potential users of the and Microsoft Office system information architecture. This should have involved discussions with all the key stakeholders.

2. Analyse existing contentUnderstand what content is present within the who uses it.

To get started using this guidance

Task

1. Group the content Plan how the content will be organised. This includes considering what content can be grouped together, what site taxonomies should be used to help classify content2007.

2. Structure the content Plan how the items and groups of content relate to each other.users. This includes considering how users will navigate to find the content they require and whether orwill be able to add their own links to content.

3. Design content presentation Plan and design how Web pages across a considering what branding elements are needed, what navigation should be consistent across the organisationand how pages should be laid out.

4. Plan content creation Decide and record if users can author content, if content approval is required andwill occur.

5. Plan document taxonomy and metadataPlan how the documents used within a This includes considering what documenstore these groups of documents, and what metadata is needed to assist in document classification. It also includes considering what document based templates should be available across docum

6. Develop the Information ArchitectureDevelop the planned site hierarchies, navigation, site directories, Web pages and contenvironment.

7. Test the Information ArchitectureTest the developed site hierarchies, navigation, site directories, Web pages and content types.


illustrates a sequential series of steps, it is possible to take an iterative approach to development. For example, once site navigation has been planned, it may be appropriate to experiment with creating navigation elements in SharePoint Server 2007. The lessons learnt frommore thorough planning process.

section of the Plan phase includes a description of the Where appropriate, worksheets within the Information Architecture Worksheets

referenced, and they should be used to record the resultand assist in planning decisions. This aims to ensure the fundamentals of a

information architecture are properly planned prior to development. worksheets can also be used during and after development to inform future IT professionals, developers, site designers and site administrators of the key decisions that have been made. completed example of each worksheet has also been made available in the Information

Sample Data {R1} workbook to act as an illustration.

the following tasks should have been completed:

Understand the goals of the project and the potential users of the SharePoint Server 2007Office system information architecture. This should have involved discussions y stakeholders.

Analyse existing content Understand what content is present within the healthcare organisation,

this guidance:

content will be organised. This includes considering what content can be grouped together, what site taxonomies should be used to help classify content, and how this will be implemented in SharePoint Server

n how the items and groups of content relate to each other. Think about how they will be made available to users. This includes considering how users will navigate to find the content they require and whether or

to content.

Plan and design how Web pages across a healthcare organisation will display content to users. This includes considering what branding elements are needed, what navigation should be consistent across the organisation

Decide and record if users can author content, if content approval is required and, if so, how content approval

Plan document taxonomy and metadata Plan how the documents used within a healthcare organisation will be organised and made available to users. This includes considering what documents can be grouped together, what document libraries are needed to

and what metadata is needed to assist in document classification. It also includes considering what document based templates should be available across document libraries.

Develop the Information Architecture Develop the planned site hierarchies, navigation, site directories, Web pages and content types in a staging

Test the Information Architecture Test the developed site hierarchies, navigation, site directories, Web pages and content types.


Page 5

illustrates a sequential series of steps, it is possible to take an iterative approach to development. For example, once site navigation has been planned, it may be appropriate to experiment

lessons learnt from this can enable a

a description of the relevant Information Architecture Worksheets –

record the results of the he fundamentals of a

rchitecture are properly planned prior to development. The worksheets can also be used during and after development to inform future IT professionals,

the key decisions that have been made. A Information

workbook to act as an illustration.

SharePoint Server 2007 Office system information architecture. This should have involved discussions

organisation, how it is used and

See Section

content will be organised. This includes considering what content can be grouped together, what SharePoint Server

3.1 and 3.2

Think about how they will be made available to users. This includes considering how users will navigate to find the content they require and whether or not they

3.3

organisation will display content to users. This includes considering what branding elements are needed, what navigation should be consistent across the organisation,

3.4

if so, how content approval 3.5

organisation will be organised and made available to users. ts can be grouped together, what document libraries are needed to

and what metadata is needed to assist in document classification. It also

3.7

ent types in a staging 4

5


Task

8. Deploy the Information ArchitectureDeploy the tested site hierarchies, navigation, site directories, Web pages and content types environment.

Where possible, perform the following key activities

Plan if content should be targeted to groups of usersThis includes considering how to categorise users into groups (or audiences) and how content should be targeted to such groups.

Develop a sample set of audiences in a staging environmentThis step should be performed after planning if content should be targeted to groups of users (section

Implement audiences into a production environmentThis step should be performed after implementing a sample set of audiences into a staging environment (section 4.7).

Table 1: Getting Started

Links to related SharePoint Server 2007 topicsin APPENDIX B.


the Information Architecture Deploy the tested site hierarchies, navigation, site directories, Web pages and content types to a production

key activities alongside those described above:

Plan if content should be targeted to groups of users This includes considering how to categorise users into groups (or audiences) and how content should be

sample set of audiences in a staging environment This step should be performed after planning if content should be targeted to groups of users (section

Implement audiences into a production environment This step should be performed after implementing a sample set of audiences into a staging environment

related SharePoint Server 2007 topics, such as the Business Data Catalog, can be found


Page 6

See Section

a production 6

This includes considering how to categorise users into groups (or audiences) and how content should be 3.6

This step should be performed after planning if content should be targeted to groups of users (section 3.6). 4.7

This step should be performed after implementing a sample set of audiences into a staging environment 6

, such as the Business Data Catalog, can be found


3 PLAN

Planning and designing an information architecture for Office system involves considering site hierarchy, navigation, approval, and personalised contentare discussed in greater detail

Figure 2 illustrates the sequence of events required when planning and designing an information architecture.


Organisational Unit

Plan and Design Web

PagesMaster Pages

Plan and Design

Navigation

Global , Current and Breadcrumb

Navigation



Content Authoring and

Approval Process

Plan Audiences Key Audiences

Plan Document Taxonomy

and Metadata

Record Stakeholders and

Existing Documents

The Benefits of Using Site Collections

Plan the Structure of

Site Collections and Sites

Properties Integration with the 2007 Office

Release

Figure 2: Sequence for Planning Information Architecture for


Planning and designing an information architecture for SharePoint Server 2007involves considering site hierarchy, navigation, Web pages, content authoring and personalised content, as well as document taxonomies and metadata.

detail in the following sections.

the sequence of events required when planning and designing an information

Organisational Topics Personalised Views

Projects

Master Pages

Current and Breadcrumb

Navigation

Web Parts and Navigation Controls

Key Considerations

Content Pages Layout Pages

Content Authoring and

Approval Process

Where and How Content Can

Appear

Key AudiencesContent

Targeting to Audiences

Stakeholders and Existing

Documents

Document Libraries

Document Library Name and Purpose

Determine Metadata


Site Collection Structure

Site Name and Purpose

Properties Integration with

Office Release

ormation Architecture for SharePoint Server 2007 and the Microsoft Office System


Page 7

SharePoint Server 2007 and the Microsoft pages, content authoring and

taxonomies and metadata. Each of these

the sequence of events required when planning and designing an information

Decision

Recommendation


3.1 Plan and Design S

Site Hierarchy

Structure of Site

Collections and Sites

Once the vision and scope of the solution, including the project goals, has been definedimportant to decide how sites is known as a site hierarchy, taxonomy or site topology.

A site hierarchy should be based on organisationprojects. These are discussed further in the sections below.

3.1.1 Organisational Unit

A hierarchy mapped to organisational provides a logical approach for users when browsing existing security groups within the organisdelegated control of their own site structures, they can also assume the management burdenProviding organisational units with the ability departmental and user acceptance.

Figure 3 illustrates a departmentalised collections which store information related to a particular department.subsites.

Finance

Balance Sheets

Annual Reports

Figure 3: Departmental Site Collections

Rollup portal sites could also be used to aggregate and present summary information about related organisational units.

3.1.2 Topics

A hierarchy based on topics, or subject matterlogical navigation. Structuring sites around topics also ensures that related information is easy to find. For example, if site collections were used to group information by areas of the body, it would be poinformation on ‘ankle conditions

This site structure may be well suited to a field collaborate.



PLAN

Web Pages NavigationContent


Audiences

Once the vision and scope of the solution, including the project goals, has been definedsites will aggregate information and how these sites will be

site hierarchy, taxonomy or site topology.

based on organisational units, topics, personalised views and/are discussed further in the sections below.

Organisational Unit

hierarchy mapped to organisational units is the most common way of classifying sitesa logical approach for users when browsing a portal site for content, but curity groups within the organisation. If organisational units, such as departments, are

delegated control of their own site structures, they can also assume the management burdentional units with the ability to customise their own environment also assists in

departmental and user acceptance.

illustrates a departmentalised hierarchy. In this scenario, one portal contains several ation related to a particular department. Each site c

Healthcare Organisation Portal

Balance Sheets

SharePoint Site

Human Resources

Payroll

Site Collection

Rollup portal sites could also be used to aggregate and present summary information about related

A hierarchy based on topics, or subject matter (for example, medical condition)on. Structuring sites around topics also ensures that related information is easy to

find. For example, if site collections were used to group information by conditionsit would be possible to easily navigate from information on ‘foot conditions

ankle conditions’.

This site structure may be well suited to a healthcare organisation in which experts in a particular


Page 8

AudiencesDocument

Taxonomy and Metadata

Once the vision and scope of the solution, including the project goals, has been defined, it is will be classified. This

units, topics, personalised views and/or

ying sites. It not only portal site for content, but may also mirror ational units, such as departments, are

delegated control of their own site structures, they can also assume the management burden. e their own environment also assists in

one portal contains several site Each site collection has three

Human Resources

Policies

Rollup portal sites could also be used to aggregate and present summary information about related

), provides users with on. Structuring sites around topics also ensures that related information is easy to

conditions that affect certain foot conditions’ to

organisation in which experts in a particular


3.1.3 Personalised Views

It is also possible to base sites on personalised views. In this scenario, a site collection, or a site could be used to target information to a particular audience based on user preferences and memberships. For example, a site could be used solely to targ

The advantage of this approach is users only receive information pertinent to them. This should not only help to increase user productivity but should also

Note

It is also possible to target content within page could show different information to users depending on their job role. Audiences are discussed further in section 3.6.

3.1.4 Projects

Creating a hierarchy based on the projects carried out by an organisation has the obvious benefit of making all project related information available to project team members. Site used to group together similar projects, perhaps by size, in terms of staff resources, or the nature of the work taking place. Rollup portal sites could also be used to aggregate and present summary information about similar projects.

However, the disadvantage of this approach is that it may require lots of security related configuration each time a project site is created. This is because projects are likely to have team members who belong to different security groups.

3.1.5 Recommendation

There are numerous ways to classify sites

� If the organisational hierarchy is well structured and unlikely to changeclassified by organisational units.

� If teams from different organisational units sites should be classified by topics.

� If individuals tend to collaborate with others in a similar job roleroles, sites should be classified by personalised views.

� If teams from different organisational units collaborate oclassified by projects.

It is also possible to classify sites in more than one way. For example, it is possible to have site collections and/or sites for each organisational unit and for each project.

Action

Using the Site Classificationpreviously created business and user requirements, record the list of the sites required.

3.2 Plan the Structure of Site C

Site Hierarchy

Structure of Site


Once a site hierarchy has been chosen and a list of the sites to include has been determinedpossible to map this to SharePoint Server 2007set of sites that can be managed together


Personalised Views

It is also possible to base sites on personalised views. In this scenario, a site collection, or a site could be used to target information to a particular audience based on user preferences and

a site could be used solely to target information to paediatricians.

The advantage of this approach is users only receive information pertinent to them. This should not increase user productivity but should also help to reduce network traffic.

It is also possible to target content within a Web page to multiple audiences. For example, a portal home page could show different information to users depending on their job role. Audiences are discussed

Creating a hierarchy based on the projects carried out by an organisation has the obvious benefit of making all project related information available to project team members. Site collections can be used to group together similar projects, perhaps by size, in terms of staff resources, or the nature of the work taking place. Rollup portal sites could also be used to aggregate and present summary information about similar projects.

wever, the disadvantage of this approach is that it may require lots of security related configuration each time a project site is created. This is because projects are likely to have team members who belong to different security groups.

Recommendations

here are numerous ways to classify sites:

he organisational hierarchy is well structured and unlikely to change,classified by organisational units.

eams from different organisational units regularly collaborate on specific subjectsites should be classified by topics.

tend to collaborate with others in a similar job role, rather than sites should be classified by personalised views.

eams from different organisational units collaborate on specific projects

It is also possible to classify sites in more than one way. For example, it is possible to have site collections and/or sites for each organisational unit and for each project.

Site Classification worksheet, record how sites should be classified. Based on the previously created business and user requirements, record the list of the sites required.

the Structure of Site Collections and Sites

PLAN



Audiences

Once a site hierarchy has been chosen and a list of the sites to include has been determinedSharePoint Server 2007 site collections. A site collection is a hierarchical

set of sites that can be managed together and consists of a top-level site, and one or more


Page 9

It is also possible to base sites on personalised views. In this scenario, a site collection, or a site could be used to target information to a particular audience based on user preferences and

et information to paediatricians.

The advantage of this approach is users only receive information pertinent to them. This should not reduce network traffic.

Web page to multiple audiences. For example, a portal home page could show different information to users depending on their job role. Audiences are discussed

Creating a hierarchy based on the projects carried out by an organisation has the obvious benefit of collections can be

used to group together similar projects, perhaps by size, in terms of staff resources, or the nature of the work taking place. Rollup portal sites could also be used to aggregate and present summary

wever, the disadvantage of this approach is that it may require lots of security related configuration each time a project site is created. This is because projects are likely to have team

, sites should be

collaborate on specific subject matters,

, rather than across job

n specific projects, sites should be

It is also possible to classify sites in more than one way. For example, it is possible to have site

lassified. Based on the previously created business and user requirements, record the list of the sites required.

AudiencesDocument


Once a site hierarchy has been chosen and a list of the sites to include has been determined, it is site collections. A site collection is a hierarchical

and one or more


subsites. Top-level Web sites can have multiple subsites, and subsites themselves can have multiple subsites, down as many levels as required. The entire structure of a topall of its subsites is called a site collection.

Using top-level Web sites and subsites it is possible to divide content into distinmanageable site collections.

Recommendation

A separate site collection should be planned for each of the site types listed in templates available with SharePoint Server 2007 should be used to create site collections, as they have been designed to address a ra

Site Type Description

Portal site This can aggregate information based on the structure and size of the healthcare Portal site is a single location, visited by most people once or more per day, but probably only at a read

Internet site Customer-facing site which style elements, such as fonts, colours and images.

Team site related to a Portal or Internet site

A site for a team to quickly organise, author, and share information related to a specific portal or Internet site. In comparison to a Portal site, a visited by only certain groups. It is likely to have lots of readwith people uploading documents and making changes to information.

Document Center site A site to centrally manage documents.

Records Center site A site designed for records management.

Table 2: Site Collection Recommendations

Action

Using the Site Classificationin Table 2 are required.

Note

The Collaboration Portal site templateServer 2007, includes a Site Directory siteclassification (defined in the Site Classificationnavigation and the future creation of sites. which allow sites to be groupedsite categories are Division or Region. However, these categories can be removed and custom categories can be added to reflect the planned site classification. be found in the Microsoft Office SharePoint Server 2007 product gu

If a site template other than a Collaboration Portal for a Site Directory site one level below the top

The Collaboration Portal will also automatically activate libraries, content types, master pages, page layouts site template without the Publishing feature, features8 for information on how to do this

Business requirements should be analysed For example, if it has been decided that sites will be classified by organisation unit, the next step is

8 Enable publishing features {R8}: http://office.microsoft.com/en-us/sharepointserver/HA101577721033.aspx?pid=CH1017829


level Web sites can have multiple subsites, and subsites themselves can have multiple subsites, down as many levels as required. The entire structure of a top

ed a site collection.

level Web sites and subsites it is possible to divide content into distin

A separate site collection should be planned for each of the site types listed in Tabletemplates available with SharePoint Server 2007 should be used to create site collections, as they have been designed to address a range of needs.

Description

can aggregate information based on the structure and size of the organisation (for example, a roll-up site or main home page). A

Portal site is a single location, visited by most people once or more per day, but probably only at a read-only level.

facing site which is usually branded and characterised by consistent style elements, such as fonts, colours and images.

A site for a team to quickly organise, author, and share information related to portal or Internet site. In comparison to a Portal site, a Team site is

visited by only certain groups. It is likely to have lots of read-write operations with people uploading documents and making changes to information.

site to centrally manage documents.

A site designed for records management.

Site Classification worksheet as a starting point, decide how many of each site type listed are required.

he Collaboration Portal site template, available by default when creating a site collection a Site Directory site one level below the top-level site. This will enable the site

Site Classification worksheet) to be made visible to usersnavigation and the future creation of sites. This is made possible by the use of Site Directory

sites to be grouped according to their purpose. During the site creation process, Division or Region. However, these categories can be removed and custom categories

can be added to reflect the planned site classification. More information on Site DirectorMicrosoft Office SharePoint Server 2007 product guide {R4}.

other than a Collaboration Portal is planned to be used at the site collection level, plan one level below the top-level site.

will also automatically activate the Publishing feature, enabling libraries, content types, master pages, page layouts and multilingual sites. If a site collection

ublishing feature, it will have to be manually activated. See on how to do this.

should be analysed to help determine how best to separate site collections. For example, if it has been decided that sites will be classified by organisation unit, the next step is

us/sharepointserver/HA101577721033.aspx?pid=CH101782971033


Page 10

level Web sites can have multiple subsites, and subsites themselves can have multiple subsites, down as many levels as required. The entire structure of a top-level Web site and

level Web sites and subsites it is possible to divide content into distinct, separately

Table 2. The default site templates available with SharePoint Server 2007 should be used to create site collections, as they have

Recommended Site Template

Collaboration Portal

usually branded and characterised by consistent Publishing Portal

A site for a team to quickly organise, author, and share information related to eam site is

Team Site

Document Center

Records Center

worksheet as a starting point, decide how many of each site type listed

when creating a site collection in SharePoint . This will enable the site

to be made visible to users, assisting in Site Directory categories,

site creation process, the default Division or Region. However, these categories can be removed and custom categories

More information on Site Directory categories can

used at the site collection level, plan

Publishing feature, enabling centralised and multilingual sites. If a site collection is based on a

See Enable publishing

to help determine how best to separate site collections. For example, if it has been decided that sites will be classified by organisation unit, the next step is

71033

http://office.microsoft.com/en-us/sharepointserver/HA101577721033.aspx?pid=CH101782971033


to decide what size of organisational unit (own site collection. If the business requirements state that each subcontrol of navigation, content types, for each sub-department.

3.2.1 The Benefits of Using Site Coll

Site collections provide a number of benefits that subsites do not:

� A portal site and site collections things, this allows data to be baresilience.

� The size of sites can be limited Without a quota, users can build sites that adversely affect performance.

� Scalability can be enhancedthe system might have performance problems as the number of subsites increases. By using site collections, up to 1 million sites performance.

Using site collections to group intranet or

� Site designers. A unified user experienceuser interface elements, such as and managed at the site

� Administrators. A site collection provides a unified mechanism for administration. For example, site security, policies, and features can be managed for an entire site collection. Site collection usage reports, audit log reports, and other data can help administrators track site security and performance.

� Authors. A site collection hasand other features which

� Users. A site collection's unified navigation, branding, and search tools provide a Web site experience.

A level of consistency across site collections also makes the to manage. For example, it will reduce the chances of exposing sensitive internal information that exists within non

3.2.2 Site Collection

When planning site collections, plan how planned to be five levels deepbottom-level site of the site collectionhttp://moss.contoso.com/subsite/subsite2/subsite3/subsite4/subsite5

In contrast, if information within a site collection can be easily grouped, users are more likely to find the content they require if a hierarchy two levels deep subsites below it), than if no hierarchy is created at all.

Recommendation

Plan site hierarchies to be no more than three levels deep (also has a subsite). This will elogical navigation whilst at the same time not being too linearof content.


to decide what size of organisational unit (for example, department, sub-department) requires own site collection. If the business requirements state that each sub-department requires tight control of navigation, content types, Web Parts and workflows, consider creating a site collection


ite collections provide a number of benefits that subsites do not:

portal site and site collections can be separated into two databases. Amongst other data to be backed up on different schedules and will

can be limited by assigning a quota (in MB) to every site collection. Without a quota, users can build sites that adversely affect performance.

can be enhanced. Although the main portal site can hold up to 2,000 subsites, system might have performance problems as the number of subsites increases. By

using site collections, up to 1 million sites can be built without adversely affecting

collections to group intranet or Internet sites content and features provide benefits for:

A unified user experience can be created for all sites in ainterface elements, such as master pages and site collection images, can be modified

ite collection level.

. A site collection provides a unified mechanism for administration. For example, site security, policies, and features can be managed for an entire site collection.

collection usage reports, audit log reports, and other data can help administrators track site security and performance.

. A site collection has shared content types, Web Parts, page layoutswhich provide a consistent authoring experience across a site collection

. A site collection's unified navigation, branding, and search tools provide a

A level of consistency across site collections also makes the SharePoint Server 2007to manage. For example, it will reduce the chances of Internet facing site collections exposing sensitive internal information that exists within non-Internet facing site collections.

Structure

ions, plan how hierarchical they will be. If a site collections’ hierarchy is planned to be five levels deep, users would struggle to navigate from the top-level site to the

of the site collection, for example, http://moss.contoso.com/ to subsite/subsite2/subsite3/subsite4/subsite5.

In contrast, if information within a site collection can be easily grouped, users are more likely to find the content they require if a hierarchy two levels deep is created (with a top-level site and distinct subsites below it), than if no hierarchy is created at all.

to be no more than three levels deep (that is, a top-level site with a subsite. This will ensure that sites are hierarchically organised enough to provide users with

logical navigation whilst at the same time not being too linear. It will also help to ensure


Page 11

department) requires its department requires tight

s and workflows, consider creating a site collection

Amongst other cked up on different schedules and will also help improve

to every site collection. Without a quota, users can build sites that adversely affect performance.

. Although the main portal site can hold up to 2,000 subsites, system might have performance problems as the number of subsites increases. By

without adversely affecting

nternet sites content and features provide benefits for:

for all sites in a site collection as ges, can be modified

. A site collection provides a unified mechanism for administration. For example, site security, policies, and features can be managed for an entire site collection.

collection usage reports, audit log reports, and other data can help administrators track

page layouts, workflows, across a site collection.

. A site collection's unified navigation, branding, and search tools provide a consistent

SharePoint Server 2007 portal easier nternet facing site collections accidentally

nternet facing site collections.

If a site collections’ hierarchy is level site to the to

In contrast, if information within a site collection can be easily grouped, users are more likely to find level site and distinct

level site with a subsite, which tes are hierarchically organised enough to provide users with

ensure efficient crawling


The Site Structure worksheet can be used to record site planning decisworksheet are:

� Site – The name of the site.

� Parent Site – The site directly above the current site in the site collection's hierarchy.

� Purpose – The purpose of the current site. For example, for a site based on the Report Center site template, ‘a site to record status information for current research projects being conducted by neurologists.

� Template – The site template to use when creating the site, such as PART I of APPENDIX A

Note

Once a site has been other areas of a portal. Where appropriate, in the templates will be used. More information on custom site templates can be found in site template9.

� Primary Users – The group(s) of users the site is primarily intended for, such as ‘biomedical scientists’.

� Site Owner – The individual or team responsible for administering the site.

Action

For each planned site collection,planning decisions. Enter each site on a separate row of the rollup sites, make sure they are recorded. worksheet for each site collection. Add other columns where appropriate. To assist in conceptualising the structure of site collections and sites, consider creating a hierarchical diagram that complimebrainstorming and the development andcategories that will be created in the Site Directory to help users find the sites that have been planned. If a site template other thacollection level, plan for a Site Directory site one level below the topworksheet.

3.2.3 Recommended

Sites should be named consistently across a be named after a department, such as ‘Neurology’, name other sites in the same way, for example, ‘Pathology’ and not ‘Pathologist Informationwhat content is likely to reside within it. It also simplifie

Site names should:

� Be concise. Names should ‘Neurology central sitenavigation elements longer and more confusing.

� Adequately describe the content of the site

� Not include special characters such as

� Not use abbreviations or acronymsmay confuse the user.

� Be no more than 30 characters

9 Save a site as a site template {R9}:


worksheet can be used to record site planning decisions. The columns in this

he name of the site.

he site directly above the current site in the site collection's hierarchy.

he purpose of the current site. For example, for a site based on the Report a site to record status information for current research projects being

conducted by neurologists.’

he site template to use when creating the site, such as ‘Record CenterAPPENDIX A for a description of site templates.

Once a site has been created and customised, it can be saved as a site template and reother areas of a portal. Where appropriate, in the Template column, record what custom site templates will be used. More information on custom site templates can be found in

The group(s) of users the site is primarily intended for, such as .

The individual or team responsible for administering the site.

For each planned site collection, use the Site Structure worksheet to record site and subsite planning decisions. Enter each site on a separate row of the Site Structure worksheet.

make sure they are recorded. If planning multiple site collections, use a separate worksheet for each site collection. Add other columns where appropriate. To assist in conceptualising the structure of site collections and sites, consider creating a hierarchical diagram that compliments the Site Structure worksheet(s). This will assist in

development and implementation of the chosen site hierarchy.will be created in the Site Directory to help users find the sites that have been

If a site template other than the Collaboration Portal site template is planned to be used at the site collection level, plan for a Site Directory site one level below the top-level site in the

Recommended Site Name and Purpose

Sites should be named consistently across a healthcare organisation. For example, if each site will be named after a department, such as ‘Neurology’, name other sites in the same way, for example,

Pathologist Information’. This will ensure users know the purpose of a site and what content is likely to reside within it. It also simplifies site administration.

Names should not contain superfluous words, for example,‘Neurology central site’. The additional words are unlikely to add value and will make navigation elements longer and more confusing.

describe the content of the site.

ot include special characters such as ‘&’, ‘%’, ‘-’ or ‘$’.

bbreviations or acronyms (unless they are universally or locally may confuse the user.

no more than 30 characters.

: http://office.microsoft.com/en-us/help/HA101577791033.aspx


Page 12

ions. The columns in this

he site directly above the current site in the site collection's hierarchy.

he purpose of the current site. For example, for a site based on the Report a site to record status information for current research projects being

Record Center’. See,

it can be saved as a site template and re-used in column, record what custom site

templates will be used. More information on custom site templates can be found in Save a site as a

The group(s) of users the site is primarily intended for, such as


worksheet to record site and subsite worksheet. If planning

If planning multiple site collections, use a separate

To assist in conceptualising the structure of site collections and sites, consider creating a worksheet(s). This will assist in

implementation of the chosen site hierarchy. Also record the will be created in the Site Directory to help users find the sites that have been

the Collaboration Portal site template is planned to be used at the site level site in the Site Structure

organisation. For example, if each site will be named after a department, such as ‘Neurology’, name other sites in the same way, for example,

will ensure users know the purpose of a site and

for example, use ‘Neurology’, not The additional words are unlikely to add value and will make

unless they are universally or locally understood). This

us/help/HA101577791033.aspx

http://office.microsoft.com/en-us/help/HA101577791033.aspx


� Be understood by the users. Where possible, conduct research within organisation to ensure the suggested site names correlate, to a certain extent, with the terms currently used.

� Be consistent not only in wording (as above) but also in format. For example, ensure that upper case and lower case wording is used consistentl

Table 3 below provides examples of site names that do and dorecommendations. The examples given are for illustrative purposes only.

Conforming Site Names

Cardiology

Haematology

Pathology

Radiology

Neurology

Occuptational Health

Table 3: Examples of Conforming and Non-Conforming Site Names

Action

In the Site Structure worksheet, fill in the that will be used to makeentering the description of the site, as outlined in section

3.3 Plan and Design

Site Hierarchy

Structure of Site


Within a SharePoint Server 2007 site, Web pages can be created to present content. For example, Web pages can be created within able to add content to such pages. T

The planning and design of Webcontent, determining where authors features are available.

The elements that are used to form a

� Master pages

� Content pages

� Layout pages

� Style sheets

� Web Parts

� Server field controls.

Separating a SharePoint Server 2007 Web greater control over design andseparately from the design of the site's content pages.


understood by the users. Where possible, conduct research within theorganisation to ensure the suggested site names correlate, to a certain extent, with the

consistent not only in wording (as above) but also in format. For example, ensure that upper case and lower case wording is used consistently.

examples of site names that do and do not conform to the recommendations. The examples given are for illustrative purposes only.

Non-Conforming Site Names

Cardiology Main Website

Haematology-Home

PTH

Radiology&RelatedInformation

Nervous System Site

Occupation health


worksheet, fill in the Purpose column appropriately to record the information that will be used to make the site discoverable in SharePoint, This information will be used when entering the description of the site, as outlined in section 4.2.4.

Plan and Design Web Pages

PLAN



Audiences

Within a SharePoint Server 2007 site, Web pages can be created to present content. For example, Web pages can be created within a News site to display separate news articles. able to add content to such pages. Thus, Web pages act as an alternative to documents.

Web pages therefore includes designing the appearance of published authors can add content on pages, and controlling which authoring

that are used to form a SharePoint Server 2007 Web page are:

SharePoint Server 2007 Web page into these elements provides site designers with over design and navigation. For example, a site's branding can be designed

separately from the design of the site's content pages.


Page 13

the healthcare organisation to ensure the suggested site names correlate, to a certain extent, with the

consistent not only in wording (as above) but also in format. For example, ensure that

to the

record the information information will be used when

AudiencesDocument


Within a SharePoint Server 2007 site, Web pages can be created to present content. For example, news articles. Authors are then

hus, Web pages act as an alternative to documents.

includes designing the appearance of published can add content on pages, and controlling which authoring

provides site designers with navigation. For example, a site's branding can be designed


This section of the guide will only consider three types of page record decisions for each of the

� Master Pages

� Content Pages

� Layout Pages

These are discussed further in the sections

Recommendation

When planning and designing

� Design pages that have clearly distinct areas of page and page specific content in the centre.page to focus on.

� Make the more important information more prominent on the page. For example, the most important text (such as an article title), should either be larger, bolder, in a more distinct colour or nearer the top of the page.

� For long or complex pages, ensure thdown the page. This helps users locate relevant content if following several search results.

� Use a simple and consistent colour scheme throughout the distinguish between different types of content (for example, which text is a hyperlink).

� Do not add unnecessary content. Users may become distracted or struggle to find what they are looking for.

� Where possible, conduct research within page designs look usable from the users’ perspective.

3.3.1 Master Pages

The master page defines the outer frame of the Web page and contains thepages in a SharePoint Server 2007illustrates the outer frames of a page

Figure 4: Master Page with the Outer Frames


This section of the guide will only consider three types of page element and thereforeeach of these:

These are discussed further in the sections below.

When planning and designing Web pages:

Design pages that have clearly distinct areas of content. For example, navigation at the top of the page and page specific content in the centre. This will allow users to quickly decide which areas of the

Make the more important information more prominent on the page. For example, the most important text (such as an article title), should either be larger, bolder, in a more distinct colour or nearer the top

For long or complex pages, ensure the user is able to read a summary of the content without scrolling This helps users locate relevant content if following several search results.

Use a simple and consistent colour scheme throughout the Web pages to make it easier for users todistinguish between different types of content (for example, which text is a hyperlink).

Do not add unnecessary content. Users may become distracted or struggle to find what they are

Where possible, conduct research within the healthcare organisation to ensure the suggested page designs look usable from the users’ perspective.

The master page defines the outer frame of the Web page and contains the componentsSharePoint Server 2007 site, or site collection, share. The example below,

illustrates the outer frames of a page.

Indicated


Page 14

herefore you should

For example, navigation at the top of the This will allow users to quickly decide which areas of the

Make the more important information more prominent on the page. For example, the most important text (such as an article title), should either be larger, bolder, in a more distinct colour or nearer the top

e user is able to read a summary of the content without scrolling This helps users locate relevant content if following several search results.

pages to make it easier for users to distinguish between different types of content (for example, which text is a hyperlink).

Do not add unnecessary content. Users may become distracted or struggle to find what they are

anisation to ensure the suggested Web

components that all example below, in Figure 4,


In SharePoint Server 2007 there are:

� Site master pages – Theseand visitors when viewing published pages.

� System master pagesauthors. They are also used in some team site templates, such as the Wiki Site and the Document Workspace.

Recommendation

Use the same site master page across all sites in a site collection to provide consistent branding and user interface.

Use the same master page style for site and system master pages. For example, if default.master is used for site master pages, use it for system master pages also. This will provide a consistent experience for users.

Master pages for all sites in a sitsite in the site collection. Typically, master pages include:

� Branding elements, such as corporate logos and colour schemes.

� Shared navigation elements.

� Shared features, such as search

� Links to Cascading Style fonts.

Action

Using the information that was recorded in the the Site column of the Plan Master Pagesinformation for each site:

1. In the Master Page column, list the name of the site master page and system master page to use in the site, such as ‘BlueBand.MasterAPPENDIX A.

2. In the Custom? column:

� If the master page will be customised for the current site, select

� If an existing template will be used for the master page, type the name of the template intothe Based on section

� If a new custom template will be used for the master page, section.

� If the master page will not be custom for the current site, select

� If master page section.

� If the master page will be applied at the current siteblank.

3. Optionally, in the Notessuch as which CSS file to use


there are:

These are used on published Web pages and are and visitors when viewing published pages.

System master pages – These supply the layout of pages visible to site designers and also used in some team site templates, such as the Wiki Site and the

Document Workspace.

Use the same site master page across all sites in a site collection to provide consistent branding and user

Use the same master page style for site and system master pages. For example, if default.master is used for site master pages, use it for system master pages also. This will provide a consistent experience for

Master pages for all sites in a site collection are stored in the Master Page Gallery in the topsite in the site collection. Typically, master pages include:

Branding elements, such as corporate logos and colour schemes.

Shared navigation elements.

Shared features, such as search commands and Help commands.

tyle Sheets (CSS). These control page appearance, colo

Using the information that was recorded in the Site Structure worksheet, list the name of each site in Plan Master Pages worksheet. Using this worksheet, fill in the following

information for each site:

column, list the name of the site master page and system master page to use BlueBand.Master’. The master pages available are shown in

column:

If the master page will be customised for the current site, select Yes.

If an existing template will be used for the master page, type the name of the template intosection.

If a new custom template will be used for the master page, type None

If the master page will not be custom for the current site, select No.

will be inherited from its parent site, type Parent into the

If the master page will be applied at the current site level, leave the Inherits from

Notes column, record instructions about how to customise the master page, such as which CSS file to use.


Page 15

are visible to site users

the layout of pages visible to site designers and also used in some team site templates, such as the Wiki Site and the

Use the same site master page across all sites in a site collection to provide consistent branding and user

Use the same master page style for site and system master pages. For example, if default.master is used for site master pages, use it for system master pages also. This will provide a consistent experience for all

e collection are stored in the Master Page Gallery in the top-level

control page appearance, colours, and

worksheet, list the name of each site in worksheet. Using this worksheet, fill in the following

column, list the name of the site master page and system master page to use . The master pages available are shown in PART II of

If an existing template will be used for the master page, type the name of the template into

None into the Based on

into the Inherits from

Inherits from section

instructions about how to customise the master page,


3.3.2 Content Pages

A content page is also known as ‘page content type’. consists of text, images and other content, all of which are stored as an entry in a Pages library. Each content page (for example,example, Figure 5 illustrates the columns that

Figure 5: Example Columns for an Article Page

When creating a page, it is possible to inherit a data structure (a series of columns) from a page content type, for example an Article Page. It

1. What columns should be added to default content pages

2. What columns should be used for each type of page (Page).

3. Whether or not the default content pages are suitable,types that may be required.

SharePoint Server 2007 includes three page conten

� Article Page – The primary content page type. This page is designed for generalWeb page content. It includes:

� Columns for images and image captions

� A column for page content

� Columns for links to display with the page

� A byline column


A content page is also known as ‘page content type’. Each content page in SharePoint Server 2007consists of text, images and other content, all of which are stored as an entry in a Pages library.

for example, an Article Page) will have columns associated with it.illustrates the columns that an Article Page may contain.

Article Page

it is possible to inherit a data structure (a series of columns) from a page Article Page. It is therefore important to plan:

hat columns should be added to default content pages.

columns should be used for each type of page (for example, a Department Article

the default content pages are suitable, and if not, the custom page content required.

includes three page content types:

he primary content page type. This page is designed for generalWeb page content. It includes:

Columns for images and image captions

A column for page content

Columns for links to display with the page


Page 16

SharePoint Server 2007 consists of text, images and other content, all of which are stored as an entry in a Pages library.

columns associated with it. For

it is possible to inherit a data structure (a series of columns) from a page

a Department Article

custom page content

he primary content page type. This page is designed for general-purpose


� Welcome Page – This is usually

� Columns for images to display

� A column for page content

� Columns for links to display with the page

� Redirect Page – A page to redirect the reader to another page.content within a SharePoint Server 2007planning at this stage.

As all three page content types inherit from the generic

� Columns to schedule the page's start and end dates

� Columns describing contact information for the author

� An image to display with the page when it is listed in a table of contents or other list

� Audience targeting information

Recommendation

Use the default page content types wand Welcome Page content tauthors and site designers can control the appearance of their content by using HTML and the framework. By doing so, completely new

Action

Use the Plan Content Pages (Article)needed. Enter each type of page into the heading section of each column. For each page, place a tick next to each column that is required. If a column Confidential?), add it in the first colum

If creating a new page content type, use the information about the custom content type.

Follow the same process for planning types of pUse the Plan Content Pages (Page Content Type worksheet


his is usually the home page of a publishing site. It includes:

Columns for images to display

A column for page content

Columns for links to display with the page

page to redirect the reader to another page. This is SharePoint Server 2007 portal has moved and, therefore

planning at this stage.

As all three page content types inherit from the generic page content type, they all also include:

the page's start and end dates

Columns describing contact information for the author

An image to display with the page when it is listed in a table of contents or other list

Audience targeting information

Use the default page content types where possible. The primary content column in both content types is the Page Content column. As this can hold any HTML content,

uthors and site designers can control the appearance of their content by using HTML and the completely new custom content types are not required.

Plan Content Pages (Article) worksheet to plan the types of Article Pages that will be needed. Enter each type of page into the heading section of each column. For each page, place a tick next to each column that is required. If a column is needed that is not available (for example,

add it in the first column of the Plan Content Pages (Article) worksheet.

If creating a new page content type, use the Plan a Page Content Type worksheet to record information about the custom content type.

Follow the same process for planning types of pages based on the Welcome Page content type. Plan Content Pages (Welcome) worksheet to record this information. Also use the

worksheet to record any custom content types that are needed.


Page 17

the home page of a publishing site. It includes:

typically created if therefore, may not require

age content type, they all also include:

An image to display with the page when it is listed in a table of contents or other list

he primary content column in both the Article Page any HTML content,

uthors and site designers can control the appearance of their content by using HTML and the CSS

ages that will be needed. Enter each type of page into the heading section of each column. For each page, place a

that is not available (for example, worksheet.

worksheet to record

ages based on the Welcome Page content type. worksheet to record this information. Also use the Plan a

to record any custom content types that are needed.


3.3.3 Layout Pages

A layout page is an Active Server Page (providing field controls into which the contents are displayed. The two examples below, and Figure 7, illustrate two different layouts for the default Article Page:

Figure 6: Article Page with Image on Left

Figure 7: Article Page with Image on Right

Important

Layout pages are only available if the Publishing feature is activated. This will be done automatically if certain site templates (for example, Collaboration Portal) are used. It is possibfeature manually; more information on how to do this can be found in


Active Server Page (.aspx file) that defines the layout for a content page by providing field controls into which the contents are displayed. The two examples below,

, illustrate two different layouts for the default Article Page:

Layout pages are only available if the Publishing feature is activated. This will be done automatically if certain site templates (for example, Collaboration Portal) are used. It is possible to activate the Publishing feature manually; more information on how to do this can be found in Enable publishing features


Page 18

layout for a content page by providing field controls into which the contents are displayed. The two examples below, Figure 6

Layout pages are only available if the Publishing feature is activated. This will be done automatically if le to activate the Publishing

Enable publishing features {R8}.


Because a layout page must display content that is stored in the columns of a page content type (or ‘content page’), it must be designed for a particular content type. For example, a layoutassociated with the Article Page content type would have several field controls, including:

� A Page Content field control to hold the contents of the Page Content column

� A Page Image field control to hold the image from the Page Image column

Although a layout page must be designed for a single content type, a content type can be associated with multiple layouts.

SharePoint Server 2007 includes a set of page layouts for tcontent types. The layouts include

Page Layout

Article Page with body only

Article Page with image on left

Article Page with image on right

Article Page with summary links

Welcome Page with summary links

Welcome Page with table of contents

Welcome splash page

Table 4: Page Layouts

If the page content types and layouts that are included with there are no additional planning steps needed. Authors will be able to choose page types and associated layouts when they create new pages. However, if new fields are added to a page content type or if custom content types are created for publishing pageplanned to reflect the new or changed content types. column to the default Article Page content type, a ‘Confidential?’ field control will need to be added to the associated layout pages

Action

To plan layouts for Article Pages, Welcome Pages and othLayout Pages worksheet. Create a separate worksheet for each page content type, such as Article Page. For each page type, list its associated layout pages, provide descriptions of the layouts, and add notes on customising or creating the layout pages. Where appropriate, create diagram(s) to illustrate the planned layout page(s). This will assist in design as well as development and

As it is possible to modify a layout page by adding CSS(such as, Web Parts and Web Part zones

� Level of control given to

� Restrictions to impose on


Because a layout page must display content that is stored in the columns of a page content type (or ‘content page’), it must be designed for a particular content type. For example, a layoutassociated with the Article Page content type would have several field controls, including:

A Page Content field control to hold the contents of the Page Content column

A Page Image field control to hold the image from the Page Image column

Although a layout page must be designed for a single content type, a content type can be associated with multiple layouts.

includes a set of page layouts for the Welcome Page and Article Page content types. The layouts include those listed in Table 4:

Page Elements

A basic page with a title and page content area.

A page with a title, page content, a page image on the left, and areas for a byline, article date, and image caption.

A page with a title, page content, a page image on the right, and areas for a byline, article date, and image caption.

A page with a title, page content, article date, byline, and a Summary Links Web Part, in which site authors can add a list of hyperlinks.

A welcome page with content and image areas, along with two Summary Links Web Parts.

A welcome page with content and image areas, along with a Table of Contents Web Part to display a hyperlinked table of contents of the site.

A simple welcome page with an image and two Summary Links Web Parts in which authors can add hyperlinks.

the page content types and layouts that are included with SharePoint Server 2007there are no additional planning steps needed. Authors will be able to choose page types and associated layouts when they create new pages. However, if new fields are added to a page content type or if custom content types are created for publishing pages, layout pages should be planned to reflect the new or changed content types. For example, after adding a ‘Confidential?’ column to the default Article Page content type, a ‘Confidential?’ field control will need to be added to the associated layout pages. This allows display of the contents of that column.

To plan layouts for Article Pages, Welcome Pages and other page content types, use the worksheet. Create a separate worksheet for each page content type, such as Article

Page. For each page type, list its associated layout pages, provide descriptions of the layouts, and add notes on customising or creating the layout pages.

te, create diagram(s) to illustrate the planned layout page(s). This will assist in development and implementation.

As it is possible to modify a layout page by adding CSS files and Microsoft ASP.NET 2.0 controls Web Part zones) it is important to consider the:

given to authors of page layouts

impose on authors of page layouts.


Page 19

Because a layout page must display content that is stored in the columns of a page content type (or ‘content page’), it must be designed for a particular content type. For example, a layout page that is associated with the Article Page content type would have several field controls, including:

A Page Content field control to hold the contents of the Page Content column

A Page Image field control to hold the image from the Page Image column

Although a layout page must be designed for a single content type, a content type can be

he Welcome Page and Article Page

A page with a title, page content, a page image on the left, and areas for a byline, article

A page with a title, page content, a page image on the right, and areas for a byline, article

A page with a title, page content, article date, byline, and a Summary Links Web Part, in

A welcome page with content and image areas, along with two Summary Links Web Parts.

Table of Contents Web Part to

A simple welcome page with an image and two Summary Links Web Parts in which authors

SharePoint Server 2007 are to be used, there are no additional planning steps needed. Authors will be able to choose page types and associated layouts when they create new pages. However, if new fields are added to a page

s, layout pages should be For example, after adding a ‘Confidential?’

column to the default Article Page content type, a ‘Confidential?’ field control will need to be added the contents of that column.

er page content types, use the Plan worksheet. Create a separate worksheet for each page content type, such as Article

Page. For each page type, list its associated layout pages, provide descriptions of the layouts, and

te, create diagram(s) to illustrate the planned layout page(s). This will assist in

and Microsoft ASP.NET 2.0 controls


Table 5 shows layout restriction recommendations for high, moderate and low control of authoring environments:

Level of Control Typical Site

High Internet presence

Medium Intranet portal site

Low Divisional or team portal site

Table 5: Layout Restrictions

Having a high level of control will restrict authors from customising pages. In contrast, a low level of control will provide authors with the ability to customise pages as they see fit. A medium level of control sits in between these and providing authors with the ability to customise a page.

Recommendation

The business and user requirements should be reviewed to decide which type of control is most suitable. Where appropriate, key stakeholders within the ensure an appropriate level of control is defined.

Action

In the Restrictions column of the will be placed on layout pages. Edit the worksheet for each page content type on which restrictions must be placed.

Note

It is often too difficult tprocess. It is usually more appropriate to allow site administrators or authors to choose the appropriate page layout when they create a page. For this reason, which pages will use thplanned page layouts do not need to be recorded.

3.4 Plan and Design Navigation

Site Hierarchy

Structure of Site


Navigation planning and design includes planning and designing the user experience for SharePoint Server 2007 portal sitesnavigation elements directly onto their pages. Navigation decisions are a key component of any SharePoint Server 2007 information architecture and are closely related to decisions about the structure of sites. These are discussed further in the sections below.


shows layout restriction recommendations for high, moderate and low control of authoring

ite Restriction Recommendations

Internet presence � Strict limitations on editing field controls� Other field control limitations, such as no hyperlinks from image

field controls � Web Parts are placed directly on the layout page and not in Web

Part zones

ntranet portal site � Moderate or no limitations on editing field controls� Web Part zones containing Web Parts, but authors are restricted

from adding/removing Web Parts

Divisional or team portal site � No limitations on editing field controls � Web Part zones allowed

Having a high level of control will restrict authors from customising pages. In contrast, a low level of control will provide authors with the ability to customise pages as they see fit. A medium level of control sits in between these and can enable site administrators to control layout pages whilst providing authors with the ability to customise a page.

The business and user requirements should be reviewed to decide which type of control is most suitable. Where appropriate, key stakeholders within the healthcare organisation should be consulted to help ensure an appropriate level of control is defined.

column of the Plan Layout Pages worksheet, record what authoring restrictions will be placed on layout pages. Edit the worksheet for each page content type on which restrictions

It is often too difficult to plan all the Web pages that are required at this stage in the planning process. It is usually more appropriate to allow site administrators or authors to choose the appropriate page layout when they create a page. For this reason, which pages will use thplanned page layouts do not need to be recorded.


PLAN



Audiences

Navigation planning and design includes planning and designing the user experience for portal sites, and deciding whether or not authors will be able to insert

navigation elements directly onto their pages. Navigation decisions are a key component of any information architecture and are closely related to decisions about the

These are discussed further in the sections below.


Page 20

shows layout restriction recommendations for high, moderate and low control of authoring

limitations on editing field controls ther field control limitations, such as no hyperlinks from image

Web Parts are placed directly on the layout page and not in Web

editing field controls ones containing Web Parts, but authors are restricted

Having a high level of control will restrict authors from customising pages. In contrast, a low level of control will provide authors with the ability to customise pages as they see fit. A medium level of

can enable site administrators to control layout pages whilst

The business and user requirements should be reviewed to decide which type of control is most suitable. organisation should be consulted to help

record what authoring restrictions will be placed on layout pages. Edit the worksheet for each page content type on which restrictions

o plan all the Web pages that are required at this stage in the planning process. It is usually more appropriate to allow site administrators or authors to choose the appropriate page layout when they create a page. For this reason, which pages will use the

AudiencesDocument


Navigation planning and design includes planning and designing the user experience for and deciding whether or not authors will be able to insert

navigation elements directly onto their pages. Navigation decisions are a key component of any information architecture and are closely related to decisions about the


3.4.1 Global, Current

3.4.1.1 Global Navigation

Global navigation typically provides links to the primary sites in a portal site and appears at the top of each page. This allows users to switch from one primary site to anotherthe portal. Figure 8 shows an example:

Figure 8: Global Navigation

By default, all subsites one level below the topnavigation. However, this can be fully customised to meet the needs of the In addition, a subsite's owners can ovedefine different global navigation settings for their subsite and the sites below it.

Recommendation

A consistent global navigation scheme This will ensure a consistent user experienceregardless of which subsite they are in.

Do not customise global navigation to reflect the security level of each user, or groups of users.SharePoint Server 2007 does this automatically by only providing users with navigation links to the areas they are authorised to access.

If customising global navigation, ensure it includes:

� A Site Title that informs the user

� A way to navigate back to the home pageof how lost they may get within a subsite

� A way to navigate to other important areas of the portmuch longer to find content in other subsites.

� A way to search. This provides users with a way page design.

Action

Using the Site Structurewhether each site will have unique global navigation (that is, it will be customised for that particular site) or will inherit its global navigation from its parent. If the site has unique globspecify which subsites and additional sites to display.

It is possible to customise global navigation by modifying master pages, see section 3.3.1


Current and Breadcrumb Navigation

Global Navigation

Global navigation typically provides links to the primary sites in a portal site and appears at the top This allows users to switch from one primary site to another, from any location

shows an example:

By default, all subsites one level below the top-level site of a portal site are added to the global navigation. However, this can be fully customised to meet the needs of the healthcareIn addition, a subsite's owners can override the global navigation settings of the topdefine different global navigation settings for their subsite and the sites below it.

consistent global navigation scheme should be developed and implemented across a consistent user experience, and allow users to navigate to other sites within the portal

regardless of which subsite they are in.

Do not customise global navigation to reflect the security level of each user, or groups of users.does this automatically by only providing users with navigation links to the areas

they are authorised to access.

If customising global navigation, ensure it includes:

the user about the site they are visiting.

back to the home page. Amongst other things, this reassures users that regardless of how lost they may get within a subsite, they can always go to a logical starting point.

A way to navigate to other important areas of the portal site. Without this, users are likely to take much longer to find content in other subsites.

A way to search. This provides users with a way to quickly find content and is therefore key to

Site Structure worksheet as a starting point, in the Plan Navigation worksheet, record site will have unique global navigation (that is, it will be customised for that particular

site) or will inherit its global navigation from its parent. If the site has unique globspecify which subsites and additional sites to display.

It is possible to customise global navigation by modifying master pages. For more information on 3.3.1.


Page 21

Global navigation typically provides links to the primary sites in a portal site and appears at the top from any location within

level site of a portal site are added to the global healthcare organisation.

rride the global navigation settings of the top-level site and define different global navigation settings for their subsite and the sites below it.

across a SharePoint site. and allow users to navigate to other sites within the portal

Do not customise global navigation to reflect the security level of each user, or groups of users. does this automatically by only providing users with navigation links to the areas

this reassures users that regardless they can always go to a logical starting point.

al site. Without this, users are likely to take

find content and is therefore key to Web

worksheet, record site will have unique global navigation (that is, it will be customised for that particular

site) or will inherit its global navigation from its parent. If the site has unique global navigation,

For more information on


3.4.1.2 Current Navigation

Current navigation, which is called to important content in the current site and in related sites. This sitewith links to related content and compliments global navigation. It is common for current navigatito appear on the left of each page in a portal site.

Figure 9: Current Navigation

By default, current navigation shows a site's pages and its sibling sites; the sites that share the same parent site. This enables users to easily navigate to content in the current site or to a site on the same level in the site hierarchy. Portal site administrators can fully custonavigation.

Recommendation

Implement a consistent approach to current navigation across a portal site. This will provide a consistent user experience and allow users to visit. A recommended approach is to have no more than Discussions) within current navigation. Providing clear and simple navigation will help userinformation efficiently.

Do not customise current navigation toSharePoint Server 2007 does this automatically by only providing users with navigation links to the areas they are authorised to access.

It is also recommended that if customisation occurs:

� Items that are related logicallyarticle). This will increase the chances of users finding the content they require.

� Site links use a larger or bolder font than lists, libraries and other will maintain a sense of hierarchy for the user

Action

Using the Site Structurewhether each site will have unique from its parent. If the site will have unique current navigation, specify whether to display its subsites, its peer sites, or additional sites. Also specify whether

It is also possible to customise current navigation by modifying on master pages, see section


Current Navigation

Current navigation, which is called ‘Quick Launch’ in default site templates, typically provides links to important content in the current site and in related sites. This site-level navigation provides users with links to related content and compliments global navigation. It is common for current navigatito appear on the left of each page in a portal site. Figure 9 shows an example:

ion shows a site's pages and its sibling sites; the sites that share the same parent site. This enables users to easily navigate to content in the current site or to a site on the same level in the site hierarchy. Portal site administrators can fully customise current

Implement a consistent approach to current navigation across a portal site. This will provide a consistent user experience and allow users to easily navigate to a site’s pages and sibling sites in each site they

proach is to have no more than five links below each heading (within current navigation. Providing clear and simple navigation will help user

Do not customise current navigation to reflect the security level of each user, or groups of users. does this automatically by only providing users with navigation links to the areas

they are authorised to access.

It is also recommended that if customisation occurs:

ms that are related logically, are also related visually (for example, a news site and a sample news . This will increase the chances of users finding the content they require.

Site links use a larger or bolder font than lists, libraries and other items that reside within them. This will maintain a sense of hierarchy for the user, and assist in navigation.

Site Structure worksheet as a starting point, in the Plan Navigation worksheet, record site will have unique current navigation settings or will inherit its current navigation

from its parent. If the site will have unique current navigation, specify whether to display its subsites, its peer sites, or additional sites. Also specify whether or not to include links to the site's Web pages.

possible to customise current navigation by modifying master pages. For more information on master pages, see section 3.3.1.


Page 22

in default site templates, typically provides links level navigation provides users

with links to related content and compliments global navigation. It is common for current navigation

ion shows a site's pages and its sibling sites; the sites that share the same parent site. This enables users to easily navigate to content in the current site or to a site on

mise current

Implement a consistent approach to current navigation across a portal site. This will provide a consistent navigate to a site’s pages and sibling sites in each site they

below each heading (for example, within current navigation. Providing clear and simple navigation will help users find

reflect the security level of each user, or groups of users. does this automatically by only providing users with navigation links to the areas

site and a sample news . This will increase the chances of users finding the content they require.

items that reside within them. This

worksheet, record current navigation settings or will inherit its current navigation

from its parent. If the site will have unique current navigation, specify whether to display its subsites, to the site's Web pages.

For more information


3.4.1.3 Breadcrumb Navigation

Breadcrumb navigation displays a dynamically generated set of links at the top of Web pages, to show users their current position in the site hierarchy. Most master pages have a single breadcrumb navigation control. 11 show examples of breadcrumb navigation:

Figure 10: Breadcrumb Navigation Control in Design Mode

Recommendation

When developing and implementing custom

� Place it at the top of the page to ensure users see it. Just like a page number in a book, it helps the user understand where they are in relation to other areas. It also helps distinguish it from the core content of the page.

� Use a small font (for example,them too much from the main content of the page.

� Bolden the last item. Making the current page more obvious to the user will increase the chances of them acknowledging their current location.

� Use a simple separator between each level. Recommended separators are

Action

Using the Site Structurewhether each site will have default or customised breadcrumb navigation. If the site is to have custom breadcrumb navigation, record what customisations are required

3.4.2 Web Parts and Navigation Controls

Using Microsoft® Office SharePointadded to a layout page. The following are available as Web Parts or Navigation Controls:

� Summary Links

� Table of Contents

� Content Query

When a user creates a page within SharePoint Server 2007 using a customised layout pageWeb Parts added to the layout page a Table of Contents Web Part to add links to other sites. However, Content Query Navigation Control is added to a layout page and able to customise the control.

Note

Layout Pages are only available if the Publishing information.

Action In the Plan Layout PagesControls each layout page will have:

� Summary Links

� Table of Contents

� Content Query Record any customisations that are required. Each of these will now be discussed in the sections below.


eadcrumb Navigation

displays a dynamically generated set of links at the top of Web pages, to show users their current position in the site hierarchy. Most master pages have a single breadcrumb navigation control. Breadcrumb navigation is enabled by default. Figure

amples of breadcrumb navigation:

: Breadcrumb Navigation Control in Design Mode Figure 11: Breadcrumb Navigation Control in Preview Mode

implementing custom breadcrumb navigation:

it at the top of the page to ensure users see it. Just like a page number in a book, it helps the user understand where they are in relation to other areas. It also helps distinguish it from the core

for example, size 8-10 point). This will ensure the user can see it without distracting them too much from the main content of the page.

Bolden the last item. Making the current page more obvious to the user will increase the chances of them acknowledging their current location.

Use a simple separator between each level. Recommended separators are ‘>’,

Structure worksheet as a starting point, in the Plan Navigation worksheet,site will have default or customised breadcrumb navigation. If the site is to have

custom breadcrumb navigation, record what customisations are required

and Navigation Controls

SharePoint® Designer 2007, Web Parts and Navigation Controls The following are available as Web Parts or Navigation Controls:

When a user creates a page within SharePoint Server 2007 using a customised layout pageadded to the layout page can also be customised. For example, the user

Web Part to add links to other sites. However, if a Table of Contents or ontrol is added to a layout page and then configured, users will not be

Layout Pages are only available if the Publishing feature is activated; see section 3.3.3

Plan Layout Pages worksheet(s), record which of the following Web Partsut page will have:

Record any customisations that are required. Each of these will now be discussed in the sections


Page 23

displays a dynamically generated set of links at the top of Web pages, to show users their current position in the site hierarchy. Most master pages have a single

Figure 10 and Figure

: Breadcrumb Navigation Control in Preview Mode

it at the top of the page to ensure users see it. Just like a page number in a book, it helps the user understand where they are in relation to other areas. It also helps distinguish it from the core

10 point). This will ensure the user can see it without distracting

Bolden the last item. Making the current page more obvious to the user will increase the chances of

‘/’ and ‘:’.

worksheet, record site will have default or customised breadcrumb navigation. If the site is to have

and Navigation Controls can be The following are available as Web Parts or Navigation Controls:

When a user creates a page within SharePoint Server 2007 using a customised layout page, the . For example, the user can customise

if a Table of Contents or configured, users will not be

3.3.3 for more

of the following Web Parts or Navigation

Record any customisations that are required. Each of these will now be discussed in the sections


3.4.2.1 Summary Links

The Summary Links Web Part include a Summary Links Web Partinclude links to portal pages appearing as secondfor example, a Document CenterDesign Mode within Office SharePoint Designer

Figure 12: Summary Links Web Part in Design

More information on Summary Links Link Web Part or a Summary Link field contro

3.4.2.2 Table of Contents

The Table of Contents Web Partinclude a Table of Contents Web Partinclude a set of hierarchical links relating to key areas of a site collection. example of a Table of Contents Web Part in Design

Figure 13: Table of Contents Web Part in Design Mode

3.4.2.3 Content Query

The Content Query Web Part a Content Query Web Part. Typically, the pages or other items based on a custom query. For example, if it is desirable to present medical articles within a news site, it would be possible to add a Content Query Welcome Page layout so that new articles are highlighted on

Figure 14 shows an example of a ContentSharePoint Designer 2007:

Figure 14: Content Query Web Part in Design Mode

10 Use and configure a Summary Link Web Part or a Summary Link field controlhttp://office.microsoft.com/en-gb/sharepointserver/HA101551681033.aspx?pid=CH101782981033


Summary Links

Web Part can be added to a layout page, so that pages using that layout include a Summary Links Web Part. Typically, the Summary Links Web Part is customised to

portal pages appearing as second-level and third-level menu items inside a center, Document Center. Figure 12 shows an example of a Summary Links Web Part in

Office SharePoint Designer 2007:

: Summary Links Web Part in Design Mode

More information on Summary Links Web Parts can be found in Use and configure a Summary Link Web Part or a Summary Link field control10.

Table of Contents

Web Part can be added to a layout page, so that pages using that layout Web Part. Typically, the Table of Contents Web Part

a set of hierarchical links relating to key areas of a site collection. Figure example of a Table of Contents Web Part in Design Mode within Office SharePoint Designer

: Table of Contents Web Part in Design Mode

nt Query

can be added to a layout page so that pages using that layout include . Typically, the Content Query Web Part is customised

pages or other items based on a custom query. For example, if it is desirable to present medical articles within a news site, it would be possible to add a Content Query Web Part Welcome Page layout so that new articles are highlighted on that page.

example of a Content Query Web Part in Design Mode within

Query Web Part in Design Mode

Use and configure a Summary Link Web Part or a Summary Link field control {R10}: gb/sharepointserver/HA101551681033.aspx?pid=CH101782981033


Page 24

using that layout is customised to

level menu items inside a center, a Summary Links Web Part in

Use and configure a Summary

a layout page, so that pages using that layout Typically, the Table of Contents Web Part is customised to

Figure 13 shows an Office SharePoint Designer 2007.

layout page so that pages using that layout include is customised to provide links to

pages or other items based on a custom query. For example, if it is desirable to present medical Web Part to the sites’

within Office

gb/sharepointserver/HA101551681033.aspx?pid=CH101782981033

http://office.microsoft.com/en-gb/sharepointserver/HA101551681033.aspx?pid=CH101782981033


3.4.3 Recommendations

If planning to add navigation controls to a layout page and clinks), there are several points

� Number of links. Too many navigation make it hard for site users to locate critical information. a SharePoint portal which are relevant for the visitors of the current pageincorporate ideas from the

� Inheriting parent site's navigation or customisingworkers to easily navigate to the other sites in the site collection. However, it could distract them, or provide links they may neremove all links which are unlikely to be needed by the future incorporate ideas from the potential users

� Showing or hiding peer siteshierarchy. For example, are peers. Showing peer sites on the current navigation can imply they have a similar purpose as the current site. However, if users of a site are not likely to want to visit peer sites, do not display them.

� Allowing or preventing authors to insert navigthis privilege reduces the control portal administrators have over the portal site's navigation. However, it facilitates collaborative working and may increase user adoption. use the business and user requirbe able to insert navigation Web Parts or not. potential users of the site

� Security sensitive navigation linksthat is linked from the site navigation, the user will not see the link.planning navigation links,

� Customised master pages. customise the appearance and functionality of navigation elements within master pages. However, this will require a basic understanding of Web pages. Therefore, before committing to customising master pages, read Custom Master Page and Page Layouts for a Web Content Management

3.5 Plan and Design C

Site Hierarchy

Structure of Site


The first step in planning content content. The second step is tothird step is to determine what content can appear in

11 How to Create a SharePoint Server 2007 Custom Master Page and Page Layouts for a{R11}: http://msdn2.microsoft.com/en


Recommendations

If planning to add navigation controls to a layout page and configure them (for examplepoints that must be considered, including:

. Too many navigation links could make a site confusingmake it hard for site users to locate critical information. Therefore, only add links to areas of a SharePoint portal which are relevant for the visitors of the current page

from the potential users of the site.

Inheriting parent site's navigation or customising. Inheriting navigation will enable workers to easily navigate to the other sites in the site collection. However, it could distract

or provide links they may never need to use. Therefore, when inheriting navigation, remove all links which are unlikely to be needed by the future users of the site.incorporate ideas from the potential users of the site.

Showing or hiding peer sites. A peer site is one which is in the same level in the site hierarchy. For example, http://moss.contoso.com/site1 and http://moss.are peers. Showing peer sites on the current navigation can imply they have a similar purpose as the current site. However, if users of a site are not likely to want to visit peer

not display them.

Allowing or preventing authors to insert navigation Web Parts. Providing users with this privilege reduces the control portal administrators have over the portal site's navigation. However, it facilitates collaborative working and may increase user adoption. use the business and user requirements of the project to determine whether authors should be able to insert navigation Web Parts or not. Gather and incorporate ideas from

of the site.

avigation links. If a user does not have permissions to a site othat is linked from the site navigation, the user will not see the link. Therefore, when planning navigation links, do not record which users or groups will need to

Customised master pages. Office SharePoint Designer 2007 can be used customise the appearance and functionality of navigation elements within master pages. However, this will require a basic understanding of Web pages. Therefore, before

to customising master pages, read How to Create a SharePoint ServeCustom Master Page and Page Layouts for a Web Content Management

Plan and Design Content Authoring and Approval

PLAN



Audiences

in planning content authoring and approval is to determine if users o plan if, and how, content will go through an approval process. The

third step is to determine what content can appear in specific areas of a site.

How to Create a SharePoint Server 2007 Custom Master Page and Page Layouts for a Web Content Management Site microsoft.com/en-us/library/bb727372.aspx#MOSS2007CustomMasterPageWCM_MasterPages


Page 25

for example, by adding

links could make a site confusing, but too few could only add links to areas of

a SharePoint portal which are relevant for the visitors of the current page. Gather and

. Inheriting navigation will enable workers to easily navigate to the other sites in the site collection. However, it could distract

when inheriting navigation, users of the site. Gather and

ich is in the same level in the site http://moss.contoso.com/site2

are peers. Showing peer sites on the current navigation can imply they have a similar purpose as the current site. However, if users of a site are not likely to want to visit peer

. Providing users with this privilege reduces the control portal administrators have over the portal site's navigation. However, it facilitates collaborative working and may increase user adoption. Therefore,

ements of the project to determine whether authors should Gather and incorporate ideas from the

f a user does not have permissions to a site or page Therefore, when need to see each link.

can be used to further customise the appearance and functionality of navigation elements within master pages. However, this will require a basic understanding of Web pages. Therefore, before

How to Create a SharePoint Server 2007 Custom Master Page and Page Layouts for a Web Content Management Site11.

pproval

AudiencesDocument


if users need to author ow, content will go through an approval process. The

Web Content Management Site us/library/bb727372.aspx#MOSS2007CustomMasterPageWCM_MasterPages

http://msdn2.microsoft.com/en-us/library/bb727372.aspx#MOSS2007CustomMasterPageWCM_MasterPages


3.5.1 Content Authoring and Approval P

By default, users with Contributeapproval process, in the form of content moderation or an approval workflow, can be created to allow these modifications to be controlled

The amount of control required type of content being published, who the content will become visible towill be published.

The control levels are:

� None – After an author submits content for publishing it will immediatelyothers. Also, if a document library is configured to support major and minor versions of content and no content moderation is used, users who have Read permissions will be able to see minor versions of the content.

� Simple moderation –Approver group after an author submits it for publishing.

� Approval workflow –of the built-in workflow features, such as automaapproval tasks to approvers' task lists and letting authors track the status of the approval process.

Consideration should be given regarding the likely visitors to the site collection, site or page when planning content authoring approval. For example, an Internet facing site should have tighter content authoring control than an intranet site.

Note

IT professionals, developers or site designersinformation about creating custom workflows can be found in

Action

Taking the above factors into account, uswhich level of control is most appropriate for each site collection, site, or page (where necessary). other types of control are in the Notes column.

3.5.2 Where and How

It is also possible to control where and how content willThis is achieved by configuring site settings for the site templates or page layouts use. For example, it is possiblethem from using a Meeting templateinformation pertinent to meetingstext always appears in the centre

Action

Use the Plan Content Restrictionshave restrictions applied to them.

12 Introduction to workflows {R12}: http://office.microsoft.com/en-gb/sharepointdesigner/HA101005871033.aspx?pid=CH100


Content Authoring and Approval Process

ontribute permissions will be able to modify the content of a page.approval process, in the form of content moderation or an approval workflow, can be created to

modifications to be controlled.

The amount of control required in the approval process depends on many factors, including the type of content being published, who the content will become visible to, and how often the content

fter an author submits content for publishing it will immediatelyothers. Also, if a document library is configured to support major and minor versions of content and no content moderation is used, users who have Read permissions will be able to see minor versions of the content.

– This requires content to be manually approved by a member of the Approver group after an author submits it for publishing.

This workflow automates the approval process and takes advantage in workflow features, such as automatically sending e-mail to approvers, adding

approval tasks to approvers' task lists and letting authors track the status of the approval

Consideration should be given regarding the likely visitors to the site collection, site or page when g content authoring approval. For example, an Internet facing site should have tighter

content authoring control than an intranet site.

IT professionals, developers or site designers can also develop their own custom approval workflow. More information about creating custom workflows can be found in Introduction to workflows

Taking the above factors into account, use the Content Authoring and Approvalhich level of control is most appropriate for each site collection, site, or page (where necessary).

are required, such as approving/rejecting sites on the site directory, record this

ow Content Can Appear

It is also possible to control where and how content will appear on a site by introducing restrictions. configuring site settings for the site templates or page layouts is possible to allow authors to use a publishing site template

template; a template designed to help plan, record and share information pertinent to meetings. Similarly, it is possible to force users to use a page layout w

centre of the page, as opposed to the left or right side.

Plan Content Restrictions worksheet to record which site templates and page layouts will have restrictions applied to them.

gb/sharepointdesigner/HA101005871033.aspx?pid=CH100667661033


Page 26

permissions will be able to modify the content of a page. An approval process, in the form of content moderation or an approval workflow, can be created to

depends on many factors, including the and how often the content

fter an author submits content for publishing it will immediately become visible to others. Also, if a document library is configured to support major and minor versions of content and no content moderation is used, users who have Read permissions will be able

content to be manually approved by a member of the

This workflow automates the approval process and takes advantage mail to approvers, adding

approval tasks to approvers' task lists and letting authors track the status of the approval

Consideration should be given regarding the likely visitors to the site collection, site or page when g content authoring approval. For example, an Internet facing site should have tighter

can also develop their own custom approval workflow. More Introduction to workflows12.

Content Authoring and Approval worksheet to record hich level of control is most appropriate for each site collection, site, or page (where necessary). If

required, such as approving/rejecting sites on the site directory, record this

site by introducing restrictions. configuring site settings for the site templates or page layouts that authors will

to allow authors to use a publishing site template whilst restricting plan, record and share

a page layout where right side.

record which site templates and page layouts will

667661033

http://office.microsoft.com/en-gb/sharepointdesigner/HA101005871033.aspx?pid=CH100667661033


3.6 Plan Audiences

Site Hierarchy

Structure of Site


An information architecture should include information about users and groups of users (audiences). By planning for audiencesas relevant as possible to users

In SharePoint Server 2007, it is possible to create and manage up to 10,000 audiencescontent to them, in all of the site collections that use that shared service.

3.6.1 Key Audiences

Audiences can be based on one or more rules. This includes

� Active Directory user informationis a member of

� SharePoint property information, such as hire date, first name and work phonedefined in the user’s My

As an example, it would be possible to which has:

� An Active Directory rule specifying that the user must be a member of the group

� A SharePoint property rule specifynumber

� A SharePoint property rule specifying that the user must have a hire date

Users could be added to this audience if they satisfy one, two

More information on configuring user information in Directory How To...13.

Using the example, consider how best to important groups within a healthcarethere should be a list of audiences that meet the needs of the groups of users who are using each site collection.

Recommendation

Consult other members of the planned adequately reflect the

Action

Use the Audience and Audience audiences.

13 Active Directory How To... {R13}: http://technet2.microsoft.com/windowsserver/en/library/89a2508a


udiences

PLAN



Audiences

An information architecture should include information about users and groups of users (audiences). By planning for audiences, it is possible to personalise information to ensure that it is

to users.

, it is possible to create and manage up to 10,000 audiencesin all of the site collections that use that shared service.

udiences

Audiences can be based on one or more rules. This includes rules based on:

user information, such as who the user reports to and what

SharePoint property information, such as hire date, first name and work phoneMy Site section of a SharePoint Server 2007 portal

As an example, it would be possible to plan an audience called ‘New Paediatricians

rule specifying that the user must be a member of the

SharePoint property rule specifying that the user must have 0118 in their work telephone

SharePoint property rule specifying that the user must have a hire date

Users could be added to this audience if they satisfy one, two, or all of the above rules.

mation on configuring user information in Active Directory can be found in

Using the example, consider how best to plan a small number of audiences that reflect the healthcare organisation. By the end of the audience planning process,

there should be a list of audiences that meet the needs of the groups of users who are using each

Consult other members of the healthcare organisation to ensure the sample set of audiences that are adequately reflect the way the organisation works and the way it is organised

Audience Rules columns in the Plan Audiences worksheet

http://technet2.microsoft.com/windowsserver/en/library/89a2508a-8446-4d61-9cd9-d274578558991033.mspx?mfr=true


Page 27

AudiencesDocument


An information architecture should include information about users and groups of users it is possible to personalise information to ensure that it is

, it is possible to create and manage up to 10,000 audiences, and target

and what group the user

SharePoint property information, such as hire date, first name and work phone. These are portal

aediatricians in Reading’

rule specifying that the user must be a member of the paediatricians

must have 0118 in their work telephone

SharePoint property rule specifying that the user must have a hire date later than 2007

or all of the above rules.

can be found in Active

a small number of audiences that reflect the organisation. By the end of the audience planning process,

there should be a list of audiences that meet the needs of the groups of users who are using each

e sample set of audiences that are the way it is organised.

worksheet to record planned

d274578558991033.mspx?mfr=true

http://go.microsoft.com/fwlink/?LinkID=73268&clcid=0x409



3.6.2 Content Targeting to

Using audiences, it is possible to target content

� A List item or Web Part

� Links published to Office client applications

� My Site navigation bar

� Trusted My Site host locations

This ensures that users receive information that is pertinent to them. pages used by more than one group of users, for exampleare discussed in the sections below

3.6.2.1 List Item or Web Part

A List Item is an item (such as a document or spreadsheet) which resides in a list. Web Part can be targeted to a specific set of audiences

Action

Use the Plan Audienceswhich audiences.

See PART III of APPENDIX Atotal amount of Web Parts available.

The Web Parts built into the Tpreconfigured Web Part templates to create their unique layout and design.

3.6.2.2 Links Published to Office

It is possible to target one or more of an audience. This list of links, available from the Services Administration page, is used to provide links to Office Server sites from within Office client applications. For example, it is possible for sites, document libraries and data coto be added to this list and appear as a choice whenever someone within a specific audience shares a document from an Office client application.

This enables:

� Users to use the same personal site from multiple client computers

� Data collection libraries to be added to the list and appear in Microsoft

� Document libraries to be visible whenever saving documents froapplication

When planning the initial deployment of information on links published to Office client applications can be found in content14.

Action

Use the Plan AudiencesOffice Applications’ page

14 Configure targeted content {R14}: http://technet.microsoft.com/en


argeting to Audiences

it is possible to target content through:

List item or Web Part

Links published to Office client applications

My Site navigation bar

host locations

This ensures that users receive information that is pertinent to them. Targeting contentmore than one group of users, for example, a home page. Each of the above itemsin the sections below.

tem or Web Part

tem is an item (such as a document or spreadsheet) which resides in a list. Web Part can be targeted to a specific set of audiences.

Plan Audiences worksheet to record which List Items and Web Parts will target content to

APPENDIX A for a list of standard SharePoint Web Parts. This list is a subset of the total amount of Web Parts available.

Team Site template are derived from the List View Web PartWeb Part templates to create their unique layout and design.

ublished to Office Client Applications

one or more of the links on a ‘Links Published to Office Applications’ page to , available from the User Profiles and My Site section of the Shared

Services Administration page, is used to provide links to Office Server sites from within Office client applications. For example, it is possible for sites, document libraries and data co

list and appear as a choice whenever someone within a specific audience shares a document from an Office client application.

Users to use the same personal site from multiple client computers

ction libraries to be added to the list and appear in Microsoft®

Document libraries to be visible whenever saving documents from any Office client

When planning the initial deployment of SharePoint Server 2007, consider each information on links published to Office client applications can be found in Configure targeted

Plan Audiences worksheet to record the links that will be added to the ‘Links Published to page, and the relevant audience for each link.

http://technet.microsoft.com/en-us/library/cc262334.aspx


Page 28

Targeting content is useful on age. Each of the above items

tem is an item (such as a document or spreadsheet) which resides in a list. Any List Item or

Parts will target content to

This list is a subset of the

are derived from the List View Web Part, and use

the links on a ‘Links Published to Office Applications’ page to section of the Shared

Services Administration page, is used to provide links to Office Server sites from within Office client applications. For example, it is possible for sites, document libraries and data connection libraries

list and appear as a choice whenever someone within a specific audience

® Office Excel® 2007

m any Office client

, consider each of the above. More Configure targeted

will be added to the ‘Links Published to



3.6.2.3 My Site Navigation

It is possible to add My Site links to personalipersonalization site is used to target content toon which one or more links can be added. relevant for one group of users others (for example, nurses). Athat they appear only for users for whom the personali

Figure 15: My Site Navigation Bar

For more information on personali

Action

Use the Plan Audiencesaudience for each link.

3.6.2.4 Trusted My Site

In some scenarios, such as when there can have access to one or more My Site host locations. In these scenarios, SSP administrators are required to manage a list of Trusted My Site host locations across all SSPs, and target each location to the audiences who need

Action

Use the Plan Audiencesanticipated SSPs and the need for users to see personali

More information on planning

3.6.2.5 Recommendations

To ensure content is targeted to audiences effectively:

� Do not filter out content fromnot be able to navigate to sites without the rifilter out such groups.

� Only target content on sites or pages that

� Consider the likely traffic each site will attract and plan appropriately. For example, be worthwhile targeting content on In contrast, it may not be worthwhile targeting content on small audiences infrequently

15 Configure personalization sites {R15

16 Plan Shared Services Providers {R16


avigation Bar

It is possible to add My Site links to personalization sites in the My Site navigation bar. used to target content to audiences and includes a My Site navigatilinks can be added. In some scenarios, a personalization site might be of users (for example, doctors) within a healthcare organi

A Shared Service Provider (SSP) administrator can target links so that they appear only for users for whom the personalised content in the site is relevant

on personalization sites, see Configure personalization sites

Plan Audiences worksheet to record each of the personalization site links and the relevant

Trusted My Site Host Locations

In some scenarios, such as when there are geographically distributed shared servicescan have access to one or more My Site host locations. In these scenarios, SSP administrators are required to manage a list of Trusted My Site host locations across all SSPs, and target each location to the audiences who need to view those locations.

Plan Audiences worksheet to record Trusted My Site host locations based on the number of anticipated SSPs and the need for users to see personalised information across SSPs.

planning SSPs is available in Plan Shared Services Providers

Recommendations

To ensure content is targeted to audiences effectively:

content from audiences that are unable to access a site not be able to navigate to sites without the right permissions, thus, it is not necessary to

Only target content on sites or pages that are accessed by more than one audience.

Consider the likely traffic each site will attract and plan appropriately. For example, worthwhile targeting content on a home page used by lots of users, several times a day.

it may not be worthwhile targeting content on a page that will beaudiences infrequently.

R15}: http://technet.microsoft.com/en-us/library/cc262716.aspx

R16}: http://technet.microsoft.com/en-us/library/cc263276.aspx


Page 29

ation sites in the My Site navigation bar. A audiences and includes a My Site navigation bar,

ation site might be organisation but not

administrator can target links so ed content in the site is relevant.

personalization sites15.

ation site links and the relevant

shared services, some users can have access to one or more My Site host locations. In these scenarios, SSP administrators are required to manage a list of Trusted My Site host locations across all SSPs, and target each

worksheet to record Trusted My Site host locations based on the number of ed information across SSPs.

Plan Shared Services Providers16.

site anyway. Users will hus, it is not necessary to

more than one audience.

Consider the likely traffic each site will attract and plan appropriately. For example, it would a home page used by lots of users, several times a day.

a page that will be used by two

us/library/cc263276.aspx




3.7 Plan Document

Site Hierarchy

Structure of Site


Planning document taxonomy and metadata includes deciding how documents will be classifiedand how metadata can be applied to documents to assist in classification. classifying documents include:

� Ensures records are named in a consistent manner over time

� Assists in the retrieval of all documents relating to a particular function or activity

� Helps determine appropriate security and access

� Helps distribute responsibility for management of a particular set of documents

� Helps determine appropriate retention and disposition periods

The steps involved in planning document taxonomies and metadata are:

1. Recording stakeholders and existing documents.

2. Planning document libraries

3. Planning metadata and content types.

4. Properties integration with the 2007 Office release.

3.7.1 Recording Stakeholders and

The first step in planning document taxonomies and metadata is to uare currently being used.

Action

Use the Document Management Stakeholders and Participantsstakeholders. Record each stakeholderinformation in the Notes

Use the Analyse Document Usagecurrently use. The information to record includes:

� Document type, such as

� Purpose of each document type, such as

� Author role of each document type, such as

� Format of the document (for example, docto another, record that in

� User role of each document type, such as

� Other roles that apply to the document's life cycle, such as

� How readers view the document, such as from a Web page or a file share

� Location of the document, such as

The location question could have multiple answers, such asclient computer or when it is


ocument Taxonomy and Metadata

PLAN



Audiences

Planning document taxonomy and metadata includes deciding how documents will be classifiedand how metadata can be applied to documents to assist in classification. The classifying documents include:

named in a consistent manner over time

Assists in the retrieval of all documents relating to a particular function or activity

Helps determine appropriate security and access

Helps distribute responsibility for management of a particular set of documents

elps determine appropriate retention and disposition periods

The steps involved in planning document taxonomies and metadata are:

Recording stakeholders and existing documents.

Planning document libraries, including document library name(s) and purpose(s)

Planning metadata and content types., including document content types and site columns

roperties integration with the 2007 Office release.

takeholders and Existing Documents

The first step in planning document taxonomies and metadata is to understand what documents

Document Management Stakeholders and Participants worksheet to determine key stakeholders. Record each stakeholder’s name, role and contact details. Add any supporting

otes column.

Analyse Document Usage worksheet to ask each stakeholder about the documents they currently use. The information to record includes:

Document type, such as ‘medical research note’, ‘patient record’, ‘internal memo

Purpose of each document type, such as ‘stores patient data’

Author role of each document type, such as ‘doctor’, or ‘paediatrician’

Format of the document (for example, doc or pdf). If the document is transformed from one format to another, record that information

User role of each document type, such as ‘nurse‘ or ‘general practitioner’

Other roles that apply to the document's life cycle, such as ‘medical record reviewer

How readers view the document, such as from a Web page or a file share

Location of the document, such as ‘client computer’, ‘Web server’, or ‘file server

The location question could have multiple answers, such as, when a document is authored on a or when it is published to a Web server.


Page 30

AudiencesDocument


Planning document taxonomy and metadata includes deciding how documents will be classified, benefits of

Assists in the retrieval of all documents relating to a particular function or activity

Helps distribute responsibility for management of a particular set of documents

, including document library name(s) and purpose(s).

document content types and site columns.

nderstand what documents

worksheet to determine key s name, role and contact details. Add any supporting

worksheet to ask each stakeholder about the documents they

internal memo’

pdf). If the document is transformed from one format

medical record reviewer’

file server’

when a document is authored on a


3.7.2 Planning Document

Using the completed Analyse Document Usagewill be classified and in which document libraries thecollection of files on SharePoint Server 2007

Table 6 lists typical uses of document libraries in

Library

Library in a team site

Library in a portal area

Library in a Document Center site

Library in a Records Repository

Library in an Internet site (HTML)

Library in an Internet site (hybrid)

Translation management document library

Slide library

Table 6: Typical Document Library Uses

3.7.2.1 Recommendations

When deciding how to group documents togetherthat were made in section 3.1 Structure worksheet. For example, if sites are to be classified by depalibraries that will store document

In some circumstances, a document may need to be more than one site. For example, a need to be published to a document library in organisation, plan separate document librariesof such documents. More information on{R12}.

Where possible, try to minimise the amount of document libraries, whilst ensuring there is a separation between the distinct groups of documents. This document library views, which the All Documents view, which is provided by default, allows users to see all ofdocument library. In the same document library, users to see only those documenttwo separate libraries. More information on document library views can be found in the change a view17.

17 Create or change a view{R17}: http://office.microsoft.com/en-gb/sharepointserver/H


ocument Libraries

Analyse Document Usage worksheet, it is possible to define how documents will be classified and in which document libraries they will be stored. A document library is a

SharePoint Server 2007 that enables sharing amongst site users.

lists typical uses of document libraries in SharePoint Server 2007.

Purpose

Facilitates easy sharing of content among medical-orientated as versioning and moderation) and searching of medical-related content

Facilitates storage of medical-related content that is intended for a wider audiis similar to a library in a team site, but is typically implemented with a morereview and approval process.

A large-scale library that typically acts as an organisation-widehistorical archive. It includes features to help users navigate, search, and manage a large number of medical-related documents in a deep hierarchy.

Facilitates specialised records management and can be useful for patientLibraries retain documents, metadata, and associated audits and are meant to be readonly.

Stores Web pages that are to be incorporated in a healthcaresite.

Stores content that is available for downloading from a healthcare

Translation management document library Translates documents if the healthcare organisation works in multiple languages. type of library includes a specialised translation workflow and views that show multiple language versions of the same document or all documents in a particular language.

Supports sharing, managing, and reusing of Microsoft Office PowerPoint 2007 slideswithin a healthcare organisation.

Recommendations

deciding how to group documents together, ensure it fits with the site classification and the planned site collections and sites recorded in the

For example, if sites are to be classified by department, plan document documents related to each department.

In some circumstances, a document may need to be stored in more than one document library, in . For example, a research paper stored in a team site document library

a document library in an Internet facing site. If this is applicable to document libraries. Consider using a workflow to automate the moving

More information on workflows can be found in Introduction to workflows

Where possible, try to minimise the amount of document libraries, whilst ensuring there is a separation between the distinct groups of documents. This can be facilitated by the use of

which allow users to group the documents on certain criteriawhich is provided by default, allows users to see all of

In the same document library, a Patient Records view could be only those documents pertaining to patient records. This would avoid the need to have

More information on document library views can be found in the



Page 31

it is possible to define how documents will be stored. A document library is a

haring amongst site users.

orientated peers, content control (such related content.

ontent that is intended for a wider audience. This typically implemented with a more stringent

wide knowledge base or includes features to help users navigate, search, and manage a large

and can be useful for patient-related records. retain documents, metadata, and associated audits and are meant to be read-

healthcare Internet or intranet Web

healthcare Web site.

works in multiple languages. This ed translation workflow and views that show multiple

language versions of the same document or all documents in a particular language.

PowerPoint 2007 slides

, ensure it fits with the site classification decisions site collections and sites recorded in the Site

rtment, plan document

more than one document library, in document library may

If this is applicable to the workflow to automate the moving Introduction to workflows

Where possible, try to minimise the amount of document libraries, whilst ensuring there is a can be facilitated by the use of

ain criteria. For example, which is provided by default, allows users to see all of the documents in a

could be created to allow This would avoid the need to have

More information on document library views can be found in the Create or

A100215771033.aspx?pid=CH101471921033



Action

Conduct research with the appropriate listed in each Analyse Document UsageServer 2007 document library. For example, some patient health information could be required to be managed centrally or be presented in Web Pages rather than as a document. For all documents that can be stored in SharePoint Server 2007, use the

� Which type of document library is most suitable

Note

Once a document library has library template for use in other areas of a portal. This can save recreating views, columns and other settings for each document library. Thus, in the Library column of the Plan Document Libraries worksheet, record which custom document library templates will be used.

� What the document library should be called

� What site the document library should reside in

� The document type to be used in the library

� Whether or not the document will require approv

� What type of document versioning is required

� If document check-in and check

� If Information Rights Management (IRM) is required. For more information on IRM, see Plan Information Rights Management

If a document needs to be stored in moreseparate document libraries in the

3.7.2.2 Document Library Name and Purpose

Document libraries should be named consistently across a each document library will be named after Files’, you should name other not ‘Mumps Information’. This will ensure users know the purpose of what content is likely to reside within it

Plan document library names that:

� Are concise. Do not contain superfluous wordsadd any value and will

� Adequately describe the content

� Do not include special characters such as

� Do include abbreviations or acronymsThis may confuse the user.

� Are no more than 30 characters

� Are understood by the users. Where possible, conduct research within organisation to ensure the suggestewith the terms currently used.

� Are consistent not only in wording (as above) but also in format. For example, ensure that upper case and lower case wording is used consistently. For simplicity, the first letter in each word and lower case for all other letters.

18 Plan Information Rights Managementhttp://technet2.microsoft.com/Office/f/?en


Conduct research with the appropriate healthcare representative to determine which documents Analyse Document Usage worksheet should and should not be stored in a SharePoint

Server 2007 document library. For example, some patient health information could be required to be y or be presented in Web Pages rather than as a document. For all documents that

can be stored in SharePoint Server 2007, use the Plan Document Libraries worksheet to record:

Which type of document library is most suitable

Once a document library has been created and customised, it can be saved as a document library template for use in other areas of a portal. This can save recreating views, columns and other settings for each document library. Thus, in the Library column of the Plan Document

worksheet, record which custom document library templates will be used.

What the document library should be called

What site the document library should reside in

The document type to be used in the library

Whether or not the document will require approval

What type of document versioning is required

in and check-out is required

If Information Rights Management (IRM) is required. For more information on IRM, see Plan Information Rights Management18

If a document needs to be stored in more that one document library in more than one site, plan separate document libraries in the Plan Document Libraries worksheet.

Document Library Name and Purpose

Document libraries should be named consistently across a healthcare organisation. For example, if will be named after the documents to be stored, such as ‘

name other libraries in the same way, for example, ‘Mumps Research Files’. This will ensure users know the purpose of each document library

what content is likely to reside within it, as well as simplifying site administration.

names that:

. Do not contain superfluous words, for example, ‘for use bywill make navigation elements longer and more confusing.

Adequately describe the content to be stored in the document library.

Do not include special characters such as ‘&’, ‘%’, ‘-’ or ‘$’.

bbreviations or acronyms (unless they are universally or locally understood)This may confuse the user.

Are no more than 30 characters.

Are understood by the users. Where possible, conduct research within organisation to ensure the suggested document library names correlate, to a certain extent, with the terms currently used.

Are consistent not only in wording (as above) but also in format. For example, ensure that upper case and lower case wording is used consistently. For simplicity, the first letter in each word and lower case for all other letters.

Plan Information Rights Management {R18}: http://technet2.microsoft.com/Office/f/?en-us/library/073bfc71-7b01-4b77-bdc3-ac018889d54b1033.mspx


Page 32

representative to determine which documents worksheet should and should not be stored in a SharePoint

Server 2007 document library. For example, some patient health information could be required to be y or be presented in Web Pages rather than as a document. For all documents that

worksheet to record:

been created and customised, it can be saved as a document library template for use in other areas of a portal. This can save recreating views, columns and other settings for each document library. Thus, in the Library column of the Plan Document

worksheet, record which custom document library templates will be used.

If Information Rights Management (IRM) is required. For more information on IRM, see Plan

that one document library in more than one site, plan

organisation. For example, if , such as ‘Measles Research Mumps Research Files’ and each document library and

site administration.

or use by’. This is unlikely to make navigation elements longer and more confusing.

(unless they are universally or locally understood).

Are understood by the users. Where possible, conduct research within the healthcare names correlate, to a certain extent,

Are consistent not only in wording (as above) but also in format. For example, ensure that upper case and lower case wording is used consistently. For simplicity, use upper case for

ac018889d54b1033.mspx

http://technet2.microsoft.com/Office/f/?en-us/library/073bfc71-7b01-4b77-bdc3-ac018889d54b1033.mspx


� Precede each document library name with the site name. For example, document libraries within a Pathology site could be called ‘Pathology Organ Research’, or ‘Pathology TisResearch’. This will aid users when they are saving files from Microsoft 2007 Office system applications to save them to t

For more information on document management, see

Table 7 below provides examples of recommendations. The examples given are for illustrative purposes only.

Conforming Library Names

Neurology Research Papers

Radiology Patient Notes

Cardiology Patient Complaints

Haemotology Staff Records

Pathology Expenditure Reports

Table 7: Examples of Conforming and Non-Conforming Site Names

Action

Record what document libraries are needed in the in the identifying which document libraries are needed, update the may be needed. For example, if documents are to be presented to external customers, it is advisable to have one site to author and review contentThe result of this exercise will be a clear pbe stored and who will access them.

3.7.3 Planning Metadata

After planning how documents will be classified into document librariesdetermine the metadata for eacinformation to a file or documentand retrieval of documents and information. metadata to store in a document library by:

� Creating document content types; document templates that have metadata fields defined, and associating them with easier to apply metadata as the content type only needs to be created once and can then be applied to several document librari

� Adding site columns for integrating metadata into the search process

� Adding columns to each document library

It is best practice to plan, developof these can be created once,productive approach, it also ensures consistencolumns to each document library can be very time consuming. For this reason, document content types and site columns are discussedto document libraries can be found

19 Document management roadmap {20 More information on an example metadata industry standardhttp://dublincore.org/documents/dces/This standard is available by default when making content types in

21 Add a column to a library {R21}: http://office.microsoft.com/en-gb/sharepointserver/HA101754741033.aspx?pid=CH102360031033#2


Precede each document library name with the site name. For example, document libraries within a Pathology site could be called ‘Pathology Organ Research’, or ‘Pathology Tis

This will aid users when they are saving files from Microsoft 2007 Office system save them to the correct site and document library.

For more information on document management, see Document management roadmap

examples of document library names that do and do norecommendations. The examples given are for illustrative purposes only.

Non-Conforming Library Names

Neurology Research Papers for Clinicians

Notes from Radiology Actions

CDY Patient Complaints

Haemotology Staff Records & Related Staff Information

Pathology expenditure Reports


Record what document libraries are needed in the in the Plan Document Librariesidentifying which document libraries are needed, update the Site Structure worksheet as new sites may be needed. For example, if documents are to be presented to external customers, it is advisable to have one site to author and review content, and a separate site to publish content.

exercise will be a clear picture of how documents will be classified, where they will be stored and who will access them.

etadata and Content Types

After planning how documents will be classified into document libraries, the next step is to determine the metadata for each library. Metadata20 allows a user to attach supplemental information to a file or document, without affecting its contents. This will help improve the storage and retrieval of documents and information. In SharePoint Server 2007, it is possible to

a document library by:

reating document content types; document templates that have metadata fields defined, with a document library or several document libraries

easier to apply metadata as the content type only needs to be created once and can then be applied to several document libraries.

Adding site columns for integrating metadata into the search process.

Adding columns to each document library.

, develop and implement site columns and document content types. Both and applied to multiple document libraries. Not only is this a

it also ensures consistency across document libraries. In contrast, adding columns to each document library can be very time consuming. For this reason, document content

discussed in the sections below. More information on adding columns to document libraries can be found in Add a column to a library21.

{R19}: http://technet.microsoft.com/en-us/library/cc263142.aspx

metadata industry standard, (Simple Dublin Core) can be found athttp://dublincore.org/documents/dces/ This standard is available by default when making content types in SharePoint Server 2007.

gb/sharepointserver/HA101754741033.aspx?pid=CH102360031033#2


Page 33

Precede each document library name with the site name. For example, document libraries within a Pathology site could be called ‘Pathology Organ Research’, or ‘Pathology Tissue

This will aid users when they are saving files from Microsoft 2007 Office system

Document management roadmap19.

ot conform to the

onforming Library Names

Neurology Research Papers for Clinicians

Haemotology Staff Records & Related Staff Information

Document Libraries worksheet. When worksheet as new sites

may be needed. For example, if documents are to be presented to external customers, it is and a separate site to publish content.

icture of how documents will be classified, where they will

the next step is to allows a user to attach supplemental

without affecting its contents. This will help improve the storage it is possible to define the

reating document content types; document templates that have metadata fields defined, y or several document libraries. This makes it

easier to apply metadata as the content type only needs to be created once and can then

and document content types. Both Not only is this a

In contrast, adding columns to each document library can be very time consuming. For this reason, document content

More information on adding columns


can be found at {R20}:

gb/sharepointserver/HA101754741033.aspx?pid=CH102360031033#2


http://dublincore.org/documents/dces/

http://office.microsoft.com/en-gb/sharepointserver/HA101754741033.aspx?pid=CH102360031033#2


3.7.3.1 Planning Document

It is possible to associate a content type with a list or library. of settings that can be appliedmanagement of the metadata and behaviour way.

Different document types may need to be memos, agendas and minutes documents)stored with each of these document types would be very different. In addition, very different workflows may need to be assigned for each type of document, metadata columns for use with each content type can be definedAmongst other things, this will the New command on the document library.Introduction to Content Types22

Figure 16 illustrates the metadata column, the user would be able to store metadata.

Figure 16: Content Type Based on Dublin Core

Document libraries and lists can contain multiple content types. For example, a library can contain both the documents and the graphics related to a project. When a list or library contains multiple content types:

� The New command in that list or library lets users create new items of all the associated content types.

� The columns associated with all available content typ

Recommendation

New content types should be based on makes development and implementation simpler. For example, columns is created, it would be possible to create a child custom content type, Leaflet’, based on this.

22 Introduction to Content Types {R22


ocument Content Types

It is possible to associate a content type with a list or library. A content type is a reusable collection ied to certain categories of content. Content types enable

the metadata and behaviour of a document or item type in a centrali

may need to be stored in the same document library memos, agendas and minutes documents). However, the metadata that may be

each of these document types would be very different. In addition, very different may need to be assigned to each type of document. By creating different content types

metadata columns for use with each content type can be definedAmongst other things, this will also allow users to create new memos, agendas or minutes

command on the document library. More information on content types can be found in 22.

metadata columns associated with one content type. Fthe user would be able to store metadata.

: Content Type Based on Dublin Core

Document libraries and lists can contain multiple content types. For example, a library can contain s and the graphics related to a project. When a list or library contains multiple

The New command in that list or library lets users create new items of all the associated

The columns associated with all available content types are displayed.

New content types should be based on appropriate existing content types. This provides consistency and implementation simpler. For example, if a custom content type

, it would be possible to create a child custom content type, ‘Patient Information

R22}: http://msdn2.microsoft.com/en-us/library/ms472236.aspx


Page 34

A content type is a reusable collection Content types enable the

a document or item type in a centralised, reusable

(for example, that may be gathered and

each of these document types would be very different. In addition, very different By creating different content types

metadata columns for use with each content type can be defined. memos, agendas or minutes using

More information on content types can be found in

For each metadata

Document libraries and lists can contain multiple content types. For example, a library can contain s and the graphics related to a project. When a list or library contains multiple

The New command in that list or library lets users create new items of all the associated

appropriate existing content types. This provides consistency and if a custom content type ‘Leaflet’ with 10

Patient Information

http://msdn2.microsoft.com/en-us/library/ms472236.aspx


Action

Use the Analyse Document Uplan document content types. First, review each document typDocument Usage worksheet to determine if there is an existing content type available for documents of that type. If a core content type (such as Docthe Content Type column of the

If a core content type is not sufficient,

Action

Fill in a separate Plan a Document C

1. Enter the document type from the

2. Using the completed worksheet, enter the site types are available in the site in which they are defined and in all subsites below that site.

3. Enter the parent content type. This will be either a core or custom content type. Where possible new content types shoCore Columns document. This will automatically populate the content type with useful columns, such as ‘Name’ and lines of text’. It will also reduce the chances of key columns, such as the creator of the document, not being added to the content type.

4. In the Plan Columns

a. Enter each column inherited from the each entry.

b. For each additional column, enter the name of a precreated. Keep in mind that the name of a column is important, because it can communicate the column's purpose. Along with the names of the additional columns, enter their types and indicate whether or not they are new.column is mandatory or not.

5. In the Plan Templateof the template to associate with this content type along with its type (such as .Docx) and a brief description of the purpose of the template. If the template is not inherited from the parent content type, in the New? field, type

6. If required, also determine the workflows and information management policies for each content type. Guidance on these areas is out of scope of this document. However, more information on workflows can be found in management policies can be found in

23 Introduction to information management policies http://office.microsoft.com/en-gb/sharepointserver/HA101


Document Usage worksheet(s) and Plan a Document Content plan document content types. First, review each document type listed in the completed

worksheet to determine if there is an existing content type available for documents of that type. If a core content type (such as Document) is sufficient, enter the content type name in

column of the Analyse Document Usage worksheet.

If a core content type is not sufficient, plan new document content types.

Plan a Document Content Type worksheet for each new content type:

ter the document type from the Analyse Document Usage worksheet.

Using the completed Site Structure worksheet as a guide, in the Plan a Document Content Typeenter the site for which the new content type will be defined. Keep in mind that content

types are available in the site in which they are defined and in all subsites below that site.

Enter the parent content type. This will be either a core or custom content type. Where possible new content types should be inherited from an existing core content type, for example, Dublin Core Columns document. This will automatically populate the content type with useful columns,

and ‘Contributor‘ as well as the appropriate column type, for example, . It will also reduce the chances of key columns, such as the creator of the document,

not being added to the content type.

Plan Columns table of the Plan a Document Content Type worksheet:

Enter each column inherited from the parent content type. In the New? column, type

For each additional column, enter the name of a pre-defined column or of a column that will be created. Keep in mind that the name of a column is important, because it can communicate the

umn's purpose. Along with the names of the additional columns, enter their types and indicate whether or not they are new. In the Required/Optional columns, specify if the column is mandatory or not.

Plan Template section of the Plan a Document Content Type worksheet, enter the name of the template to associate with this content type along with its type (such as .Docx) and a brief description of the purpose of the template. If the template is not inherited from the parent content

field, type Yes.

If required, also determine the workflows and information management policies for each content type. Guidance on these areas is out of scope of this document. However, more information on workflows can be found in Introduction to Workflows {R12} and more information on information management policies can be found in Introduction to information management policies

Introduction to information management policies {R23}:



Page 35

Plan a Document Content Type worksheet to e listed in the completed Analyse

worksheet to determine if there is an existing content type available for documents ument) is sufficient, enter the content type name in

worksheet for each new content type:

Plan a Document Content Type will be defined. Keep in mind that content

types are available in the site in which they are defined and in all subsites below that site.

Enter the parent content type. This will be either a core or custom content type. Where possible uld be inherited from an existing core content type, for example, Dublin

Core Columns document. This will automatically populate the content type with useful columns, as well as the appropriate column type, for example, ‘Multiple

. It will also reduce the chances of key columns, such as the creator of the document,

worksheet:

column, type No for

defined column or of a column that will be created. Keep in mind that the name of a column is important, because it can communicate the

umn's purpose. Along with the names of the additional columns, enter their types and columns, specify if the

worksheet, enter the name of the template to associate with this content type along with its type (such as .Docx) and a brief description of the purpose of the template. If the template is not inherited from the parent content

If required, also determine the workflows and information management policies for each content type. Guidance on these areas is out of scope of this document. However, more information on

more information on information Introduction to information management policies23.

735291033.aspx?pid=CH100948701033



3.7.3.2 Planning Site C

When a document content typemapped as columns in the destination library.defined in the document content type, a column of ‘Author

In some circumstances the document library may need additional desirable to have a ‘Notes’ column in the document libraryRather than manually adding asite column called ‘Notes’ which can be used across

Action

Use the Site Columns worksheetwhich document library(s) the columns will be added to.

3.7.3.3 Recommendation

When planning the metadata for each content type and document library, it is important to consider content storage and retrieval. For example, defining many content types, each with many columns is likely to ensure rapid retrieval. However, it may be very file and add the appropriate metadata. In contrast, by having too few content types and columns will make it easy for users to save the file, but difficult to retrieve. We therefore recommend:

� Use between 3 and 15 c

� Use the default columns of Name and Title where possible. Alternatively, a metadata standard such as Simple Dublin Core could be followed.

� Use a Comments or Notes column to allow users to add additional information that wouldotherwise not be captured.

� Use 2007 Microsoft Office system applications, such as Microsoft Word to bind the metadata to placeholders within the document. This will allow users to create a document as normal, whilst automatically adding metadata to the dofound in section 3.7.4.

When adding new columns to a custom content type, ensure they:

� Are unique

� Clearly describe the data to be en

� Are understood by the users. Where possible, conduct research within a organisation to ensure the suggested site names correlate, to a certain extent, with the terms currently used

� Have names that are:

� Concise

� Do not include special characters such as ‘&’, ‘%’, ‘

� Are no more than 30 characters

Examples of metadata columns that conform to these recommendations are:

� Creator

� Contributor

� Date Created

� Date Modified

� Subject


Columns

content type is sent to the destination document library, the metadata values are columns in the destination library. For example, if a metadata value of ‘Author’ is

defined in the document content type, a column of ‘Author’ will be automatically

document library may need additional columns. For example, it maycolumn in the document library, but not in the document content type.

Rather than manually adding a ‘Notes’ column to each document library, it is best practiceotes’ which can be used across multiple document libraries.

worksheet to record the name and type of each site column. Also specify document library(s) the columns will be added to.

Recommendation

When planning the metadata for each content type and document library, it is important to consider content storage and retrieval. For example, defining many content types, each with many columns is likely to ensure rapid retrieval. However, it may be very time consuming for the user to save the file and add the appropriate metadata. In contrast, by having too few content types and columns will make it easy for users to save the file, but difficult to retrieve. We therefore recommend:

Use between 3 and 15 columns for each content type.

Use the default columns of Name and Title where possible. Alternatively, a metadata standard such as Simple Dublin Core could be followed.

Use a Comments or Notes column to allow users to add additional information that wouldotherwise not be captured.

Use 2007 Microsoft Office system applications, such as Microsoft Word to bind the metadata to placeholders within the document. This will allow users to create a document as normal, whilst automatically adding metadata to the document. More information can be

When adding new columns to a custom content type, ensure they:

Clearly describe the data to be entered by users, for example, ‘Patient Forename’

Are understood by the users. Where possible, conduct research within a organisation to ensure the suggested site names correlate, to a certain extent, with the

Do not include special characters such as ‘&’, ‘%’, ‘-’ or ‘$’

Are no more than 30 characters

metadata columns that conform to these recommendations are:


Page 36

he metadata values are For example, if a metadata value of ‘Author’ is

automatically created.

columns. For example, it may be but not in the document content type.

best practice to plan a document libraries.

record the name and type of each site column. Also specify

When planning the metadata for each content type and document library, it is important to consider content storage and retrieval. For example, defining many content types, each with many columns

time consuming for the user to save the file and add the appropriate metadata. In contrast, by having too few content types and columns will make it easy for users to save the file, but difficult to retrieve. We therefore recommend:

Use the default columns of Name and Title where possible. Alternatively, a metadata

Use a Comments or Notes column to allow users to add additional information that would

Use 2007 Microsoft Office system applications, such as Microsoft Word to bind the metadata to placeholders within the document. This will allow users to create a document

cument. More information can be

tered by users, for example, ‘Patient Forename’

Are understood by the users. Where possible, conduct research within a healthcare organisation to ensure the suggested site names correlate, to a certain extent, with the


� Description

� Language

� Format

� Notes

It is important that a consistent approach to metadata is applied across a For example, if ‘Contributor’ is used for one content type, it should be used across all content types. This will:

� Make it clearer to users wha

� Reduce the amount of time required to find documents and information because indexing, searching and browsing content should be improved.

� Facilitate better information sharing

� Reduce the amount of document duplication

3.7.4 Properties Integration with the 2007 Office Release

In the 2007 Microsoft Office system, when a user is editing a document from a SharePoint Server 2007 document management server, a document, as shown in Figure reflects the document's properties on the server.is easily visible to the user.

Figure 17: Document Information Panel

Note

This feature is not available in earlier versions of Microsoft Office.


It is important that a consistent approach to metadata is applied across a healthcareFor example, if ‘Contributor’ is used for one content type, it should be used across all content types.

Make it clearer to users what metadata to enter

Reduce the amount of time required to find documents and information because indexing, searching and browsing content should be improved.

Facilitate better information sharing

Reduce the amount of document duplication

gration with the 2007 Office Release

In the 2007 Microsoft Office system, when a user is editing a document from a SharePoint Server 2007 document management server, a Document Information Panel is shown at the top of the

Figure 17. The Document Information Panel displays an editable form that reflects the document's properties on the server. Thus, the metadata associated with the document

This feature is not available in earlier versions of Microsoft Office.


Page 37

healthcare organisation. For example, if ‘Contributor’ is used for one content type, it should be used across all content types.

Reduce the amount of time required to find documents and information because indexing,

gration with the 2007 Office Release

In the 2007 Microsoft Office system, when a user is editing a document from a SharePoint Server is shown at the top of the displays an editable form that

Thus, the metadata associated with the document


Authors using Microsoft Office documents through the use of property controlssection 3.7.3, as well as the metadata values associated with the documentdocument’s body, as shown in

Figure 18: Property Control

Document properties can be inserted into multiple areas of a document. For example, if the document properties include a doctor’s name, this name can be inserted into the title page, the footer, or anywhere else the name particular patient, the Doctor Name property can be updated on the document management server; this updated doctor name will be reflected in every instance of this property that has been inserted into a document.

It is also possible to configure a document template that includes control properties that will be used as content type metadata. Microsoft® Office Word, Microsoftusers to exploit the metadata structure present in SharePoint Server 2007.

It is also possible to use the Document Information Panel to utilise other SharePoint Server 2007 functionality, including:

� Workflow

� Document check-in and check

� Integration between Excel 2007 and ExcelServer 2007


Authors using Microsoft Office Word 2007 can also insert properties defined on the server into their documents through the use of property controls. This allows the metadata columns, as planned in

, as well as the metadata values associated with the document, to be placed into the as shown in Figure 18 below.

Document properties can be inserted into multiple areas of a document. For example, if the document properties include a doctor’s name, this name can be inserted into the title page, the footer, or anywhere else the name is used in the document. If a new doctor is assigned to a particular patient, the Doctor Name property can be updated on the document management server; this updated doctor name will be reflected in every instance of this property that has been inserted

It is also possible to configure a document template that includes control properties that will be used as content type metadata. Thus, using 2007 Office system client applications, such as

Office Word, Microsoft® Office Excel® and Microsoft® Office InfoPathusers to exploit the metadata structure present in SharePoint Server 2007.

It is also possible to use the Document Information Panel to utilise other SharePoint Server 2007

in and check-out

Integration between Excel 2007 and Excel® Services in Microsoft® Office SharePoint


Page 38

Word 2007 can also insert properties defined on the server into their . This allows the metadata columns, as planned in

to be placed into the

Document properties can be inserted into multiple areas of a document. For example, if the document properties include a doctor’s name, this name can be inserted into the title page, the

is used in the document. If a new doctor is assigned to a particular patient, the Doctor Name property can be updated on the document management server; this updated doctor name will be reflected in every instance of this property that has been inserted

It is also possible to configure a document template that includes control properties that will be Thus, using 2007 Office system client applications, such as

Office InfoPath®, it is possible for

It is also possible to use the Document Information Panel to utilise other SharePoint Server 2007

Office SharePoint®


4 DEVELOP

The Develop phase involves developing the solution components that have been defined in the planning phase. This includes developing site hierarchies, navigation, pages, content types and audiences. sections. It is advised that a staging environment that mirrors the production environmefor development.

Figure 19 illustrates the critical components which an IT professional responsible for developing the SharePoint Server 2007 information architecture needs to

Create Site Collection

Develop Navigation

Develop Site Hierarchy

Add a Category to the Site Directory

Develop Pages

Master Pages


Create a Document Library

Develop Content Types

Create a Custom Document

Content Type

Develop Audiences

Import Profiles

Global Navigation

Delete Subsite

Figure 19: Sequence for Developing an Information Archi


The Develop phase involves developing the solution components that have been defined in the ncludes developing site hierarchies, navigation, pages, document libraries,

Each of these are discussed in greater detail in the following It is advised that a staging environment that mirrors the production environme

the critical components which an IT professional responsible for developing the SharePoint Server 2007 information architecture needs to follow.

Add a Category to the Site Directory

Master Pages Content Pages Page Layouts

Edit a Category in the Site Directory

Remove a Category from

the Site Directory

Create a Document Library

Configure Approval

Create a Custom Document

Content Type

Create Columns for the New

Custom Content Type

Import ProfilesCreate an Audience

Target Content

Global Navigation

Current Navigation

Breadcrumb Navigation Web Parts

Create Subsite

Delete SubsiteEdit Sites in the Site Directory

Approve or Reject Sites in

the Site Directory

Configure Check-Out

Configure Versioning

Associate a Content Type

with a Document Library

Implement and Update a Document Template

Remove a Site from the Site Directory

: Sequence for Developing an Information Architecture based on SharePoint Server 2007 and the 2007 Office S


Page 39

The Develop phase involves developing the solution components that have been defined in the document libraries,

Each of these are discussed in greater detail in the following It is advised that a staging environment that mirrors the production environment is used

the critical components which an IT professional responsible for developing the

Web Parts

Create Subsite Other Ways to Create Sites

Configure Versioning

Configure Information

Rights Management

Implement and

Document

Remove a Site from the Site

Configure Site Directory Settings

the 2007 Office System


Recommendation

Develop the elements described in staging environment should match the production environment as closely as possible. The use of virtualisation software can be useful in

The following sections assumeappropriately configured. More can be found in Deployment for Office SharePoint Server 2007

4.1 Create Site Collection

Site Collection Site Hierarchy

It is assumed that a Web application has been created. This option was chosen when installing SharePoint Server 2007 Standard or Enterprise Edition. More information on creating Web applications applications (Windows SharePoint Ser

Use the information contained in the in the creation of each planned site collection. Each site collection will have an individual worksheet.

To create a site collection:

1. Click Start > All ProgramsAdministration.

2. On the top navigation bar, click

3. On the Application ManagementCreate site collection

4. On the Create Site Collectionin which the site collection is to be created on the drop-down menu.

24 Create or extend Web applications (Windows SharePoint Services) http://technet.microsoft.com/en-us/library/cc287954.aspx


evelop the elements described in Figure 19 in a staging environment. To achieve beststaging environment should match the production environment as closely as possible. The use of virtualisation software can be useful in staging environments, and can significantly reduce costs.

The following sections assume a staged environment has SharePoint Server 2007More information on deploying and configuring SharePoint Server 2007

Deployment for Office SharePoint Server 2007 {R5}.

Create Site Collection

DEVELOP

Navigation Web PagesDocument Libraries

Content Types

It is assumed that a Web application has been created. This is done automatically if the basic setup option was chosen when installing SharePoint Server 2007 Standard or Enterprise Edition. More information on creating Web applications manually can be found in Create or extend Web applications (Windows SharePoint Services)24.

contained in the Site Structure worksheets, completed in section in the creation of each planned site collection. Each site collection will have an individual

Programs > Administrative Tools > SharePoint Central

On the top navigation bar, click Application Management.

Management page, in the SharePoint Site ManagementCreate site collection.

Create Site Collection page, in the Web Application section, if the Web application

in which the site collection is to be created is not specified, click Change Web Applicationmenu.

Create or extend Web applications (Windows SharePoint Services) {R24}: us/library/cc287954.aspx


Page 40

in a staging environment. To achieve best results, the staging environment should match the production environment as closely as possible. The use of

environments, and can significantly reduce costs.

SharePoint Server 2007 deployed and SharePoint Server 2007

Content Types Audiences

done automatically if the basic setup option was chosen when installing SharePoint Server 2007 Standard or Enterprise Edition. More

Create or extend Web

worksheets, completed in section 3.2, to assist in the creation of each planned site collection. Each site collection will have an individual

Central

SharePoint Site Management section, click

section, if the Web application Change Web Application



5. If presented with the Selectsite collection will be created.

6. On the Create Site Collection

a. In the Title and Description The title should match the information entereStructure worksheet.

b. In the Web Site Address

c. In the Template Selectionappropriate tab, and then select the desired site template. templates that are available are listed in selected, a description for that template appears in the

d. In the Primary Site Collection AdministratorDOMAIN\username) for the user who will be the site collection administrator.


Select Web Application page, click the Web application in which the site collection will be created.

Create Site Collection page:

Title and Description section, enter a title and description for the site collection. title should match the information entered in the Site Collection

worksheet.

Web Site Address section, enter a URL.

Template Selection section, select a language from the dropappropriate tab, and then select the desired site template. The common default site

are available are listed in PART I of APPENDIX A. When a template is selected, a description for that template appears in the Template Selection

Primary Site Collection Administrator section, enter the user name (in the form username) for the user who will be the site collection administrator.


Page 41

page, click the Web application in which the

section, enter a title and description for the site collection. Site Collection column of the Site

from the drop-down list, click the common default site

When a template is Template Selection section.

section, enter the user name (in the form username) for the user who will be the site collection administrator.


e. To identify a user as the secondary owner of the new top(recommended), in the user name for the secondary administrator of the site collection.

f. If quotas will be used to limit resource use for site collections, in the section, select a templa

7. Click OK. A top-level site will automatically be created.

8. Repeat this process until each site collection, as defined in the has been created.

4.2 Develop Site Hierarchy


A site hierarchy can be developed From the Site Actions menu, it is possible to create and delete subsite(s).

A Site Directory provides a central location from which administrators can view, manage, and access all of the Web sites that are associated with a portal site. From a Site Directory site, administrators can view both the portal structure and individual sitreject new sites, and edit or delete site links.

The Site Directory also enables administrators to the Site Classification and Site Structurecategories which group sites. site. It is possible to modify a site Directory.

4.2.1 Add a Category

When a new site is created, as outlined in section using the categorisation(s) that recorded in section 3.2 to assist in creating Site Directory categories. Directory categories can be found in{R4}.

To add a category to the Site Directory:

1. On the home page, click

2. On the Site Actions menu


To identify a user as the secondary owner of the new top-level Web site mended), in the Secondary Site Collection Administrator

user name for the secondary administrator of the site collection.

If quotas will be used to limit resource use for site collections, in the a template from the Select a quota template list.

level site will automatically be created.

Repeat this process until each site collection, as defined in the Site Structure

Hierarchy

DEVELOP


Content Types

developed through the Site Actions menu and the use of the Site Directory. it is possible to create and delete subsite(s).

Site Directory provides a central location from which administrators can view, manage, and access all of the Web sites that are associated with a portal site. From a Site Directory site, administrators can view both the portal structure and individual sites within the portal, approve or reject new sites, and edit or delete site links.

The Site Directory also enables administrators to develop the chosen site hierarchySite Structure worksheets. This is made possible through the use of

Categories allow users to easily navigate to all sites within a portal It is possible to modify a site hierarchy by adding, editing or deleting categories in the Site

a Category to the Site Directory

When a new site is created, as outlined in section 4.2.4, it will be possible to categorise the site that are added to the Site Directory. Use the information that was

to assist in creating Site Directory categories. More information on Site egories can be found in the Microsoft Office SharePoint Server 2007 product guide

To add a category to the Site Directory:

click the Sites link on the top navigation bar to open the Site Directory.

menu at the top-right of the page, click Edit Page.


Page 42

level Web site section, enter the

If quotas will be used to limit resource use for site collections, in the Quota Template

Site Structure worksheet,


through the Site Actions menu and the use of the Site Directory.

Site Directory provides a central location from which administrators can view, manage, and access all of the Web sites that are associated with a portal site. From a Site Directory site,

es within the portal, approve or

hierarchy, as recorded in ble through the use of

allow users to easily navigate to all sites within a portal by adding, editing or deleting categories in the Site

, it will be possible to categorise the site Use the information that was

More information on Site Microsoft Office SharePoint Server 2007 product guide

to open the Site Directory.

.


3. In the editable version of the Site Directory page, iNew Category.

4. On the Create Column

a. Type a name for the new category in the Organisation Unit/Department/Topic/Project/Personalised view). Also ensure that the Choice (menu to c

b. Type a description of the category into the

c. Specify whether or not (for example, the organisational units).

d. Use the options and text box to decide how the choices will be displayed, if choices can be filled in by the user

e. If the new category is to be added to the default view, select the option.

5. Click OK. The new category Site Directory page.

6. Repeat the above steps for all site classifications defined in the worksheet.


version of the Site Directory page, in the Categories section, click

Column page:

ype a name for the new category in the Column name text box (for example Organisation Unit/Department/Topic/Project/Personalised view). Also ensure that the

(menu to choose from) option is selected.

Type a description of the category into the Description text box.

whether or not the column contains information and enter the (for example, the organisational units).

and text box to decide how the choices will be displayed, if choices can by the user and what the default value is.

If the new category is to be added to the default view, select the Add to default view

. The new category (for example, Organisational Unit) will now be shown on t

Repeat the above steps for all site classifications defined in the Site Classification


Page 43

section, click Create

box (for example Organisation Unit/Department/Topic/Project/Personalised view). Also ensure that the

the column contains information and enter the desired choices

and text box to decide how the choices will be displayed, if choices can

Add to default view

ll now be shown on the

Site Classification


4.2.2 Edit a Category

Modifying a category in the Site Dirmade available to users when theorganisational unit, it would be possible to modify an existing category (named ‘Organisational Unit’ and Department’. Use the information that was recorded in section Directory categories.

To modify a category in the Site Directory:


2. On the Site Actions menu, click

3. In the editable version of the Site Directory page, and Categories.

4. On the Settings menu, click

5. On the Customize Sitesexample, Region).

6. On the Change Column:Sites

a. Type a new name for the category iUnit/Topic/Personalised view

b. Type a new description of the category into the


Edit a Category in the Site Directory

in the Site Directory allows the site hierarchy, as defined in section when they classify a site. For example, if sites are to be classified by

nit, it would be possible to modify an existing category (such as,‘Organisational Unit’ and to have values of ‘Cardiology Department’ and ‘Haematology

Use the information that was recorded in section 3.2 to assist in creating Site

To modify a category in the Site Directory:

On the home page, click the Sites link on the top navigation bar to open the Site Directory.

menu, click Edit Page.

version of the Site Directory page, in the Categories section,

menu, click List Settings.

Customize Sites page, in the Columns section, click the category to edit (for

Change Column:Sites page:

me for the category in the Column name box (for exampleUnit/Topic/Personalised view/Project).

iption of the category into the Description text box


Page 44

, as defined in section 3.2, to be if sites are to be classified by

such as, Region) to be have values of ‘Cardiology Department’ and ‘Haematology

to assist in creating Site


section, click Edit Sites

section, click the category to edit (for

box (for example, Organisation

text box.


c. Specify if the column contains inorganisational units Cardiology and Radiology

d. Use the options and text box to decide how the choices will be displayed, if choices can be filled in by the user

7. Click OK to save the changes.

4.2.3 Remove a Category

Removing a category in the Site Directory allows the site made available to users when they classify a site. For example, if sites are to be classified by organisational unit, it would be possible to remove any unwanted existing categories (Division). When a new site is created, remaining classifications. Use the information that was recorded in section Site Directory categories.

Note

Removing a category will not delete any sites. However, it may leave some sites unclassified. For more information on classifying existing sites by site25.

To remove a category from the Site Directory:



3. In the editable version of the Site Directory page, in the and Categories.

25 Add a link to an existing site {R25}:http://office.microsoft.com/en-us/sharepointserver/HA10090631


Specify if the column contains information and enter the choices (for example, organisational units Cardiology and Radiology)

and text box to decide how the choices will be displayed, if choices can by the user and what the default value is.

to save the changes.

Remove a Category from the Site Directory

Removing a category in the Site Directory allows the site hierarchy, as defined in section made available to users when they classify a site. For example, if sites are to be classified by

nit, it would be possible to remove any unwanted existing categories (When a new site is created, users will only be able to categorise sites according the

Use the information that was recorded in section 3.2

Removing a category will not delete any sites. However, it may leave some sites unclassified. For more classifying existing sites by adding them to the Site Directory, see Add a link to an existing

ove a category from the Site Directory:



version of the Site Directory page, in the Categories section, c



Page 45

formation and enter the choices (for example, the

and text box to decide how the choices will be displayed, if choices can

, as defined in section 3.2, to be made available to users when they classify a site. For example, if sites are to be classified by

nit, it would be possible to remove any unwanted existing categories (for example, e sites according the

to assist in creating

Removing a category will not delete any sites. However, it may leave some sites unclassified. For more Add a link to an existing


section, click Edit Sites

1033.aspx?pid=CH100963401033




5. On the Customize Sitesexample, Region).

6. On the Change Column: Sites

7. Repeat the above steps for all categoriesin the Site Classification

4.2.4 Create Subsite

Subsites are created within topCentral Administration. Use the subsites, including any rollup sites that have been plannedworksheet describes a subsite.

To create a subsite:

1. Navigate to the locationhttp://moss.contoso.com

2. Perform one of the following

� On the Site Actions

� Click View All Site Content

3. Under Web Pages, click

4. On the New SharePoint Site page, i

a. Type a title for the new site. The tisubsite Web page and in navigational elements that help users to find and open the site.


menu, click List Settings.

Customize Sites page, in the Columns section, click the category to delete (for

Change Column: Sites page, click Delete.

above steps for all categories that do not match the site classification recorded Site Classification worksheet.

Subsites are created within top-level sites and subsites and cannot be created within SharePoint Use the Site Structure worksheet created in section 3.2

, including any rollup sites that have been planned. Each row in the Site Structureworksheet describes a subsite.

Navigate to the location of the existing site, for example, the site collection URL of contoso.com/ as created in section 4.1.

one of the following actions:

Site Actions menu, click Create.

View All Site Content and then click Create.

, click Sites and Workspaces.

On the New SharePoint Site page, in the Title and Description section

ype a title for the new site. The title is a required field and appears at the top of the Web page and in navigational elements that help users to find and open the


Page 46

section, click the category to delete (for

match the site classification recorded

cannot be created within SharePoint 3.2 to assist in creating Site Structure

of the existing site, for example, the site collection URL of

section:

appears at the top of the Web page and in navigational elements that help users to find and open the


b. Enter information describing the the Purpose column from the at the top of the subsite site.

5. In the Web Site Addressautomatically provided.

Tip

To avoid potential problems with updating or modifying the site, do not enter any of the following special characters as part of the URL

6. In the Template Selectionselect the desired site template. listed in PART I of APPENDIX Atemplate appears in the

Note

If the required site template is not availablethe site collection level

7. In the Permissions section,

� Use same permissions as parent site new site.

� Use Unique Permissions

Note

Unique permissions can be configured after all on the New SharePoint Site

8. In the Navigation section, select whether Launch navigation area


Enter information describing the purpose of the new site in the Descriptioncolumn from the Site Structure worksheet to help. The description appears

subsite Web page and helps users understand the purpose of the new

Web Site Address section, type a URL for the new site. The first part of the URL iautomatically provided.

To avoid potential problems with updating or modifying the site, do not enter any of the following special characters as part of the URL: / \\ : * ? " < > | # \t { } %

Template Selection section, select a language, click the appropriate tab, and then select the desired site template. The common default site templates that

APPENDIX A. When a template is selected, a description for that template appears in the Template Selection section.

site template is not available, the Publishing feature may not havethe site collection level, see section 3.3.3 for more information.

section, select one of the following options:

Use same permissions as parent site if the users of the parent site are to access the

Use Unique Permissions to configure different permissions.

Unique permissions can be configured after all the appropriate information has been entered New SharePoint Site page.

section, select whether or not the new subsite will be visible in the area of the parent site or in the top link bar.


Page 47

Description box. Use The description appears

Web page and helps users understand the purpose of the new

section, type a URL for the new site. The first part of the URL is

To avoid potential problems with updating or modifying the site, do not enter any of the following

a language, click the appropriate tab, and then that are available are

. When a template is selected, a description for that

may not have been activated at

if the users of the parent site are to access the

appropriate information has been entered

ill be visible in the Quick


By default, the Quick Launch is displayed on the left side of most userbelow the View All Site Contenttabs across the top of all pages.

9. In the Navigation Inheritancefrom the parent site, or bar.

Note

This setting also affects whether of the parent site.

10. In the Site Categories Note

The options below will only be presented if a Site collection. The Division and Region categories Server 2007 and will be present if the Site Directory categories havein sections 4.2.1, 4.2.2

a. Specify whether or not on the Site Directory template.

b. If the new subsite will be listed in the site directory, use the Division and Region

11. Click Create. If the new subsite will have the same permission as its parent site, the new site will be created. If the new subsite will have unique permissions, the Set Up Groups for this Site page appears

12. If the Set Up Groups for this Site

a. Select whether to create new groups or use existing groups for visitors, members, and owners of this site

� If Create a new group the new SharePoint group, or type a new name, and add the appropriate people. Click the check mark icon to verify any names that are typed, or click the Address Book icon to browse more names.


By default, the Quick Launch is displayed on the left side of most user-facing pages directly View All Site Content link. The top link bar appears as one or more hyperlinked

tabs across the top of all pages.

Navigation Inheritance section, select Yes if the new site will inherit its top link bar or select No if the new site will have its own set of links on the top link

This setting also affects whether or not the new site appears as part of the breadcrumb navigation

Site Categories section:

The options below will only be presented if a Site Directory site was created when creating the site The Division and Region categories are example categories that come with SharePoint

will be present if the Site Directory categories have not been modified, as outlined 4.2.2 and 4.2.3.

or not the new subsite will be visible in the site directory; a site based on the Site Directory template.

If the new subsite will be listed in the site directory, use the options Region of the subsite.

. If the new subsite will have the same permission as its parent site, the new site will be created. If the new subsite will have unique permissions, the Set Up Groups for

pears, where it is possible to set up groups for the subsite.

Set Up Groups for this Site page appears:

to create new groups or use existing groups for visitors, members, and and complete the required information:

Create a new group is selected, either accept the automatically created name for the new SharePoint group, or type a new name, and add the appropriate people. Click the check mark icon to verify any names that are typed, or click the Address Book icon to browse more names.


Page 48

facing pages directly link. The top link bar appears as one or more hyperlinked

the new site will inherit its top link bar n set of links on the top link

the new site appears as part of the breadcrumb navigation

Directory site was created when creating the site are example categories that come with SharePoint

t been modified, as outlined

the new subsite will be visible in the site directory; a site based

to specify the

. If the new subsite will have the same permission as its parent site, the new site will be created. If the new subsite will have unique permissions, the Set Up Groups for

it is possible to set up groups for the subsite.

to create new groups or use existing groups for visitors, members, and

either accept the automatically created name for the new SharePoint group, or type a new name, and add the appropriate people. Click the check mark icon to verify any names that are typed, or click the Address


In the Visitors to this Siteto the Visitors group, which provides the group members with permission to read the content on the site, by default.

� If Use an existing group the list.

If there are several SharePoint groups, the list may be abbreviated. Click see the full list.

b. Click OK.

13. Repeat this process until each subbeen created.

A hierarchy will automatically be created depending on the location of the site in which the above steps are performed. For example, if within ‘newsitecollection > subsite’ and a new site is created it will create a three tiered hierarchy of ‘newsitecolle

When a new site is created, as outlined above it will be possible to categorise the site in the Directory. This will help with site classification.

4.2.5 Other Ways to Create Sites

Administrators or developers can create sit

� Using a command-line operationsites command and parameters. For more information, see or a Site Collection26.

� Programmatically. For more information, see the Microsoft(WSS) Developer Center

� With a compatible Web design programUsing a Web design program that is compatible with WSS allows the creation and customisation of sites. For more inform

26 How to: Create or Delete a Site or a Site Collect

27 Windows SharePoint Services Developer Center


tors to this Site section, it is also possible to add all authenticated users to the Visitors group, which provides the group members with permission to read the content on the site, by default.

Use an existing group is selected, select the appropriate SharePoint group from

If there are several SharePoint groups, the list may be abbreviated. Click see the full list.

Repeat this process until each subsite, as planned for in the Site Structure

omatically be created depending on the location of the site in which the above steps are performed. For example, if within ‘newsitecollection > subsite’ and a new site is created it will create a three tiered hierarchy of ‘newsitecollection > subsite > subsubsite’.

When a new site is created, as outlined above it will be possible to categorise the site in the This will help with site classification.

Other Ways to Create Sites

Administrators or developers can create sites:

line operation. Administrators can create sites by using the create sites command and parameters. For more information, see How to: Create or Delete a Site

. For more information, see the Microsoft Windows SharePoint Services (WSS) Developer Center27.

With a compatible Web design program, for example, Office SharePoint Designer 2007. Using a Web design program that is compatible with WSS allows the creation and customisation of sites. For more information, see Help in the program.

How to: Create or Delete a Site or a Site Collection {R26}: http://msdn2.microsoft.com/en-gb/library/ms448720.aspx

Windows SharePoint Services Developer Center {R27}: http://msdn2.microsoft.com/en-us/sharepoint/default.aspx


Page 49

section, it is also possible to add all authenticated users to the Visitors group, which provides the group members with permission to read

SharePoint group from

If there are several SharePoint groups, the list may be abbreviated. Click More... to

Site Structure worksheet, has

omatically be created depending on the location of the site in which the above steps are performed. For example, if within ‘newsitecollection > subsite’ and a new site is created it

ction > subsite > subsubsite’.

When a new site is created, as outlined above it will be possible to categorise the site in the Site

. Administrators can create sites by using the create How to: Create or Delete a Site

Windows SharePoint Services

SharePoint Designer 2007. Using a Web design program that is compatible with WSS allows the creation and

gb/library/ms448720.aspx

us/sharepoint/default.aspx

http://msdn2.microsoft.com/en-gb/library/ms448720.aspx

http://msdn2.microsoft.com/en-us/sharepoint/default.aspx


4.2.6 Delete Subsite

When a site collection is created, depending on the template used, one or more subsites may have been automatically created. Use the subsites that should be deleted.

To delete a subsite:

1. On the Site Actions menu, c

2. In the right-hand pane,

3. On the Actions menu, click

4. Repeat the above steps for all sites that are not required.

4.2.7 Edit Sites in the Site Directory

From the Site Directory, site administrators can edit a site by changing the site name, movingto another location, or changing permissions for a site.

The Template column of the Site Structurethe Site Directory template. The what links require editing.

To edit a site in a Site Directory:


2. In the Site Directory, click


When a site collection is created, depending on the template used, one or more subsites may have automatically created. Use the Site Structure worksheet created in section

subsites that should be deleted.

menu, click Manage Content and Structure.

hand pane, select the subsites to be deleted (for example, Document Center).

menu, click Delete.

steps for all sites that are not required.

in the Site Directory

From the Site Directory, site administrators can edit a site by changing the site name, movingto another location, or changing permissions for a site.

Site Structure worksheet will help determine which sites are based on the Site Directory template. The Notes column of the Site Structure worksheet will help determ

To edit a site in a Site Directory:

click the Sites link on the top navigation bar to open the Site Directory.

In the Site Directory, click View All Site Content.


Page 50

When a site collection is created, depending on the template used, one or more subsites may have worksheet created in section 3.2 to identify

(for example, Document Center).

From the Site Directory, site administrators can edit a site by changing the site name, moving a site

worksheet will help determine which sites are based on worksheet will help determine

open the Site Directory.


3. Click the Sites folder.

4. Point to the site that needs to the menu displays.

5. To make changes to the site name or location, click

6. On the Edit Sites page

� In the Title section

� In the Description

� Classify the site by selecting created.

� In the URL section, use the textthe site.

� In the Top Site section, specify

� In the Tasks and Tools

� In the Owner section

� From Link Status status:

� OK

� Broken

� Indeterminate

7. Click OK to save the changes.


needs to be edited and click the drop-down arrow that appears

To make changes to the site name or location, click Edit Item.

On the Edit Sites page, modify the site appropriately:

section, type a new name for the site.

Description section, type a new description for the site.

by selecting the appropriate categories that have previously

section, use the text boxes to specify the Web address and

section, specify whether or not the site is a top-level site

Tasks and Tools section, specify whether or not the site is a top task

section, type the user name of the owner of the site.

Link Status drop-down menu, select one of the following to categorise the

Indeterminate

to save the changes.


Page 51

arrow that appears so that

previously been

eb address and description for

level site.

the site is a top task.

one of the following to categorise the link


4.2.8 Approve or Reject Sites

Sites that are added by administrators are approved by default. Sites that are added by others are set to Pending and must be approved or rejected by a site administrator.

In the Content Authoring and Approvalapproved or rejected by administrators.

To approve or reject a site in the Site Directory:

1. On the home page, click the



4. Point to the site that needs to appears so that the menu displays.

5. On the menu, click Approve/reject

6. On the Approve/Reject

� To approve the site,

� To reject the site, select

� To leave the site pending, approved or rejected

4.2.9 Remove a Site

To remove a site from the Site Directory:

1. On the home page, click the




Approve or Reject Sites from the Site Directory

Sites that are added by administrators are approved by default. Sites that are added by others are and must be approved or rejected by a site administrator.

Content Authoring and Approval worksheet, use the Notes column to find out ifdministrators.

To approve or reject a site in the Site Directory:



folder.

needs to be approved or rejected, and click the dropappears so that the menu displays.

Approve/reject.

Reject page, in the Approval Status section, do one of the following

To approve the site, select the Approved option

select the Rejected option

To leave the site pending, select the Pending option. This will allow the site to be approved or rejected

Remove a Site from the Site Directory

To remove a site from the Site Directory:




Page 52

Sites that are added by administrators are approved by default. Sites that are added by others are

column to find out if sites will be

link on the top navigation bar to open the Site Directory.

drop-down arrow that

e of the following:

. This will allow the site to be

link on the top navigation bar to open the Site Directory.


4. Point to the site that is to menu displays.

5. On the menu, click Delete Item

6. When the confirmation message appears, click

4.2.10 Configure Site Directory

It is possible to configure Site Directadded to the Site Directory. It is also possible to force the site creator to describe the site by selecting at least one value from onecreated, it is correctly classified.

To configure Site Directory settings:

1. Navigate to the top-level site of the site collection (for example,

2. On the Site Actions menu, c

3. On the Site Settings page, under settings.

4. On the Site Directory Settings Enforce listing new sites in Site Directory


is to be deleted and click the drop-down arrow that appears so that the

Delete Item.

When the confirmation message appears, click OK to remove the site.

Site Directory Settings

It is possible to configure Site Directory settings so that every site that is addedadded to the Site Directory. It is also possible to force the site creator to describe the site by selecting at least one value from one, or all, categories. This will ensure that when a new s

it is correctly classified.

To configure Site Directory settings:

level site of the site collection (for example, http://moss.

menu, click Site Settings > Modify All Site Settings

page, under Site Collection Administration, click

Site Directory Settings page, in the Site Creation Metadata section, select the Enforce listing new sites in Site Directory option.


Page 53

arrow that appears so that the

ory settings so that every site that is added, is automatically added to the Site Directory. It is also possible to force the site creator to describe the site by

categories. This will ensure that when a new site is

http://moss.contoso.com/).

Modify All Site Settings.

click Site directory

section, select the


5. Specify how many categorisations users must apply when creating a site.

6. Click OK.

4.3 Develop Navigation


4.3.1 Global Navigation

Global navigation (or ‘top link bar’) SharePoint Server 2007 portal. By default, all subsites one level below the topsite are added to the global navigation. Thus to are required.

However, it is possible to configure global navigation. section 3.4.1.1 to assist.

Important

Depending on which site template the site collectionthe links described in the procedures in the sections below will vary.

For example, the Site Actions menu will be one of the following:

Figure 20: Site Actions Menu – Small Version

4.3.1.1 Add, Edit or Delete

Use the information that was recorded in section delete from global navigation on each site.

To add, edit or delete a site from the global navigation:

1. Navigate to the top-level site of the site created in section 4.1.


categorisations users must apply when creating a site.

avigation

DEVELOP


Content Types

Global Navigation

op link bar’) helps form the master page(s) that are used throughout a portal. By default, all subsites one level below the top-

site are added to the global navigation. Thus to develop and implement global navigation no steps

However, it is possible to configure global navigation. Use the information that was recorded in

Depending on which site template the site collection and site has been created from, the links described in the procedures in the sections below will vary.

For example, the Site Actions menu will be one of the following:

Small Version Figure 21: Site Actions Menu – Large Version

elete Site From Global Navigation

Use the information that was recorded in section 3.4.1.1 to help determine what sites to add, edit or delete from global navigation on each site.

To add, edit or delete a site from the global navigation:

level site of the site collection, for example, http://moss.


Page 54

categorisations users must apply when creating a site.


helps form the master page(s) that are used throughout a -level site of a portal

implement global navigation no steps

information that was recorded in

has been created from, the appearance of

help determine what sites to add, edit or

http://moss.contoso.com/ as


2. On the Site Actions menu, click Modify All Site Settings

3. Click the appropriate link:

� Under Look and Feel


4. If presented, do one of the following:

� To add a new link, click possible to link to specified external sites

� To edit a link, click the

� To delete a link, click the

Alternatively, in the Global Navigationbelow the current siteheading:

� To add a new link, Add Link. Type the Link dialog box.

� To add a new heading, click audience for the heading in the

� To edit a customised link, click Note

It is not possible to edit the links that are automatically created (for example, a News from the Site Navigation Settings page. Instead, navigate to the Site Settings page of the subsite (for example, description, and

� To hide a link, click the appropriate site and click

� To delete a custom link or heading, click Navigation (or top

5. Click OK.


menu, click Site Settings. If presented with a larger menu, Modify All Site Settings.

lick the appropriate link:

Look and Feel, click Top link bar

Look and Feel, click Navigation

If presented, do one of the following:

To add a new link, click New Link. Type the URL and a description for the link. It is possible to link to specified external sites, or pages that are anywhere in the portal site.

To edit a link, click the Edit button . Make any necessary changes to the description.

To delete a link, click the Edit button , and then click Delete.

Global Navigation section, select the Display the navigation items below the current site option. Then do one of the following under the Global Navigation

To add a new link, which will appear below any Headings that have been created,. Type the title, URL, description and audience for the link in the

To add a new heading, click Add Heading. Type the title, URL, description and audience for the heading in the Navigation Link dialog box.

To edit a customised link, click Edit.

It is not possible to edit the links that are automatically created (for example, a News from the Site Navigation Settings page. Instead, navigate to the Site Settings page of the subsite (for example, http://moss.contoso.com/subsite) and under Look and Feel

and icon.

To hide a link, click the appropriate site and click Hide.

To delete a custom link or heading, click Delete. When a link is deleted from the Global op link bar), any links contained under that link are also deleted.


Page 55

. If presented with a larger menu, also click

. Type the URL and a description for the link. It is or pages that are anywhere in the portal site.

. Make any necessary changes to the description.

Display the navigation items Global Navigation

any Headings that have been created, click iption and audience for the link in the Navigation

itle, URL, description and

It is not possible to edit the links that are automatically created (for example, a News subsite) from the Site Navigation Settings page. Instead, navigate to the Site Settings page of the

ok and Feel, click Title,

When a link is deleted from the Global that link are also deleted.


4.3.1.2 Configure Order of

The information recorded in section navigation for each site.

To manually configure the order of sites within global navigation:

1. Navigate to the top-level site of the site collection, for example, created in section 4.1.

2. On the Site Actions menu, clickModify All Site Settings




4. Do one of the following:

� If within a Top Link Bar page, cdrop-down lists to change the order in which the links appear on the top link bar.

� If within a Site Navigation Settings manually option. Use the the Global Navigation

5. Click OK.


rder of Sites In Global Navigation

he information recorded in section 3.4.1.1 will help determine the order of sites in global

To manually configure the order of sites within global navigation:

level site of the site collection, for example, http://moss.





Do one of the following:

If within a Top Link Bar page, click Change Order. In the Link Orderto change the order in which the links appear on the top link bar.

Site Navigation Settings page, in the Sorting section, select . Use the Move Up and Move Down buttons to organise links under

Global Navigation heading.


Page 56

tes in global

moss.contoso.com/ as

If presented with a larger menu, also click

Link Order section, use the to change the order in which the links appear on the top link bar.

select the Sort buttons to organise links under


4.3.1.3 Unique Global

The information recorded in section global navigation and what the unique global navigation should be

To allow unique global navigation

1. Navigate to the subsite, for example, 4.2.4.





4. If presented, click Stop Inheriting Links

� To add a new link, click possible to link to specified external sites

� To edit a link, click the

� To delete a link, click the

Alternatively, do one of the following under the




It is not possible to edit the links that are automatically created (for example, a News Subfrom the Site Navigation Settings navigate to the Site Settings page of the subsite (for example,


lobal Navigation

The information recorded in section 3.4.1.1 will help determine which subsite should have unique global navigation and what the unique global navigation should be.

To allow unique global navigation for a subsite:

Navigate to the subsite, for example, http://moss.contoso.com/site, as created in section

menu, click Site Settings. If presented with a larger menu, All Site Settings.




Stop Inheriting Links and do one of the following:

To add a new link, click New Link. Type the URL and a description for the link. It is possible to link to specified external sites, or pages that are anywhere in the portal site.

To edit a link, click the Edit button . Make any necessary changes to the description.

To delete a link, click the Edit button , and then click Delete.

Alternatively, do one of the following under the Global Navigation heading:

To add a new link, which will appear below any Headings that have been created, . Type the title, URL, description and audience for the link in the



It is not possible to edit the links that are automatically created (for example, a News Sube Navigation Settings page. To edit the links that are automatically created,

navigate to the Site Settings page of the subsite (for example,


Page 57

should have unique

, as created in section


. Type the URL and a description for the link. It is or pages that are anywhere in the portal site.

. Make any necessary changes to the description.

heading:

which will appear below any Headings that have been created, click itle, URL, description and audience for the link in the Navigation


It is not possible to edit the links that are automatically created (for example, a News Sub-site) To edit the links that are automatically created,


http://moss.contoso.comicon.


� To delete a custom link or heading, click Navigation (or top

5. Click OK.

By using Office SharePoint Designerfunctionality of global navigation. For example,

� Customise CSSs

� Modify the data sourceglobal navigation.

� Modify the menu style of the navigation. For example, fly

For more information, see Get started with basic site customizations

4.3.2 Current Navigation

Current navigation (or ‘Quick Launch’) helps form the master page(s) that are used throughout a SharePoint Server 2007 portal. By default, current navigation shows a site's pages and its sibling sites; the sites that share the same parent site. Thus tono steps are required.

However, it is possible to configure current navigation. section 3.4.1.2 to assist.

Note

Depending on which site template the site collection has been created from, the links described in the procedures in the sections below will vary.

4.3.2.1 Add, Edit or Delete a

Use the information that was recorded in section delete from current navigation on each site.

To add, edit or delete a site from the current navigation:

1. Navigate to the site which requires custom current navigation, for example, http://moss.contoso.com


28 Get started with basic site customizationshttp://office.microsoft.com/en-us/sharepointdesigner/HA101741431033.aspx?pid=CH100667691033


contoso.com/subsite) and under Look and Feel, click Title,


To delete a custom link or heading, click Delete. When a link is deleted from Global op link bar), any links contained under that link are also deleted.

arePoint Designer 2007, it is possible to further customise the appearance and functionality of global navigation. For example, it is possible to:

Modify the data source. For example, it is possible to trim the number of sites shown in

Modify the menu style of the navigation. For example, fly-out menus can be selected.

Get started with basic site customizations28.

Current Navigation

‘Quick Launch’) helps form the master page(s) that are used throughout a portal. By default, current navigation shows a site's pages and its sibling

sites; the sites that share the same parent site. Thus to develop and implement curr

However, it is possible to configure current navigation. Use the information that was recorded in

Depending on which site template the site collection has been created from, the links described in the procedures in the sections below will vary.

elete a Site from Current Navigation

Use the information that was recorded in section 3.4.1.2 to help determine what sites to add, edit or delete from current navigation on each site.

To add, edit or delete a site from the current navigation:

to the site which requires custom current navigation, for example, contoso.com/ as created in section 4.2.4.


Get started with basic site customizations {R28}: us/sharepointdesigner/HA101741431033.aspx?pid=CH100667691033


Page 58

, description, and

When a link is deleted from Global ar), any links contained under that link are also deleted.

e the appearance and

to trim the number of sites shown in

can be selected.

‘Quick Launch’) helps form the master page(s) that are used throughout a portal. By default, current navigation shows a site's pages and its sibling

implement current navigation

Use the information that was recorded in

Depending on which site template the site collection has been created from, the links described in the

to help determine what sites to add, edit or

to the site which requires custom current navigation, for example,


us/sharepointdesigner/HA101741431033.aspx?pid=CH100667691033

http://office.microsoft.com/en-us/sharepointdesigner/HA101741431033.aspx?pid=CH100667691033





4. If presented, do one of the following:

� To add a new link, New Link. Type the URL and a description for the link. Select the heading the new link will appear under from the

� To edit a link, click the and the heading under which the link w

� To remove a link, click the

� To add a new heading, click

� To edit a heading, click the description.

� To remove a heading, click the

Alternatively, do one of the following under the




It is not possible to edit the links that are automatically created (for example, a News from the Site Navigation Settings page. Instead, navigate tosubsite (for example, description, and


� To delete a custom link, click Navigation (or Quick Launch), any links contained under that heading are also deleted.

5. Click OK.



Look and Feel, click Quick Launch


If presented, do one of the following:

To add a new link, which will appear below any Headings that have been created, . Type the URL and a description for the link. Select the heading the new link

will appear under from the Heading drop-down box.

To edit a link, click the Edit button . Make any necessary changes to the description and the heading under which the link will appear.

To remove a link, click the Edit button , and then click Delete.

To add a new heading, click New Heading. Type the URL and a description for the link.

To edit a heading, click the Edit button . Make any necessary changes to the

To remove a heading, click the Edit button , and then click Delete

Alternatively, do one of the following under the Current Navigation heading:


To add a new heading, click Add Heading. Type the title, URL, description and e for the heading in the Navigation Link dialog box.


It is not possible to edit the links that are automatically created (for example, a News from the Site Navigation Settings page. Instead, navigate to the Site Settings page of the subsite (for example, http://moss.contoso.com/subsite) and under Look and Feel

and icon.


To delete a custom link, click Delete. When a heading is deleted from the Current Navigation (or Quick Launch), any links contained under that heading are also deleted.


Page 59

which will appear below any Headings that have been created, click . Type the URL and a description for the link. Select the heading the new link

. Make any necessary changes to the description

. Type the URL and a description for the link.

. Make any necessary changes to the

Delete.

heading:



It is not possible to edit the links that are automatically created (for example, a News subsite) the Site Settings page of the

Look and Feel, click Title,

heading is deleted from the Current Navigation (or Quick Launch), any links contained under that heading are also deleted.


4.3.2.2 Configure Order of

The information recorded in section navigation for each site.

To manually configure the order of sites within current navigation:

1. Navigate to the site which requires custom cur






� If within a Quick Launchdrop-down lists to change the order in which the links appear on the Quick Launch bar.


rder of Sites in Current Navigation

The information recorded in section 3.4.1.2 will help determine the order of sites in cur

To manually configure the order of sites within current navigation:

Navigate to the site which requires custom current navigation.





of the following:

If within a Quick Launch page, click Change Order. In the Link Orderto change the order in which the links appear on the Quick Launch bar.


Page 60

will help determine the order of sites in current


Link Order section, use the to change the order in which the links appear on the Quick Launch bar.


� If within a Site Navigation Settingsmanually option. Use the the Current Navigation

5. Click OK.

4.3.2.3 Unique Current

The information recorded in section current navigation.

To configure a subsite to not inherit current navigation settings from

1. Navigate to the subsite.





4. If presented with the Current Navigation

� To display the current site, its siblings and the items below the current site, select the Display the current site, the navigation items below the current, and the current site’s siblings option.

� To display only the navigation items below the current site, select the navigation items below the current site

Alternatively, if presented with the the Navigation Editing and Sor


Site Navigation Settings page, in the Sorting section, select . Use the Move Up and Move Down buttons to organise links under

Current Navigation heading.

urrent Navigation

The information recorded in section 3.4.1.2 will help determine which subsite should have unique

To configure a subsite to not inherit current navigation settings from the

Navigate to the subsite.





Current Navigation section, do one of the following:

To display the current site, its siblings and the items below the current site, select the Display the current site, the navigation items below the current, and the current

option.

play only the navigation items below the current site, select the navigation items below the current site option.

Alternatively, if presented with the Site Navigation Settings page, do one of the following in Navigation Editing and Sorting section:


Page 61

select the Sort buttons to organise links under

will help determine which subsite should have unique

parent site:

. If presented with a larger menu, also click

section, do one of the following:

To display the current site, its siblings and the items below the current site, select the Display the current site, the navigation items below the current, and the current

play only the navigation items below the current site, select the Display only the

do one of the following in




� To edit a link or heading, click

� To delete a link, click

As with global navigation, it is possible to further customicurrent navigation by using Office SharePoint Designerstarted with basic site customizations

4.3.3 Breadcrumb Navigation

By using Office SharePoint Designer 2007control on master pages. For example, breadcrumb navigation can be removed from a page.

The information recorded in section are required for breadcrumb navigation

To modify or delete breadcrumb navigation in Office SharePo

1. In Office SharePoint Designer 2007, on the that contains the master page with the breadcrumb navigation that requires modification or deletion (for example,

2. Click the plus sign (+) next to the masterpages folder.

3. Double-click the master page that requires modification.

Note

Master pages have a .master file extension.




To edit a link or heading, click Edit.

To delete a link, click Delete.

As with global navigation, it is possible to further customise the appearance and functionality ofcurrent navigation by using Office SharePoint Designer 2007. For more information, see started with basic site customizations {R28}.

Breadcrumb Navigation

using Office SharePoint Designer 2007, it is possible to configure the breadcrumb navigation control on master pages. For example, breadcrumb navigation can be removed from a

he information recorded in section 3.4.1.2 will help determine the modifications or deletionsbreadcrumb navigation elements on each sites’ master page.

To modify or delete breadcrumb navigation in Office SharePoint Designer 2007:

In Office SharePoint Designer 2007, on the File menu, click Open Site that contains the master page with the breadcrumb navigation that requires modification or

(for example, http://moss.contoso.com).

he plus sign (+) next to the _catalogs folder to expand it, and then expand

click the master page that requires modification.

Master pages have a .master file extension.


Page 62


tle, URL, description and

e the appearance and functionality of . For more information, see Get

it is possible to configure the breadcrumb navigation control on master pages. For example, breadcrumb navigation can be removed from a master

modifications or deletions that

int Designer 2007:

Open Site and select the site that contains the master page with the breadcrumb navigation that requires modification or

and then expand the


4. If presented with a dialog box, click

5. With the master page open in Office SharePoint Designer 2007, doublePlaceHolderBreadcrumb

6. In the Tag Properties

7. Right-click the master page in

8. If the Check In dialog box appears, click

All pages that use the customised master page will now display the new breadcrumb navigation.

For more information on customising breadcrumb navigation via Office SharePoint Designer see Modify the default SharePoint content placeholders

29 Modify the default SharePoint content placeholdershttp://office.microsoft.com/en-us/sharepointdesigner/HA101651201033.aspx?pid=CH100


If presented with a dialog box, click Yes to check out the master page for editing

With the master page open in Office SharePoint Designer 2007, doublePlaceHolderBreadcrumb placeholder.

task pane, modify the breadcrumb navigation.

click the master page in the Folder List navigation pane and click

dialog box appears, click OK.


For more information on customising breadcrumb navigation via Office SharePoint Designer Modify the default SharePoint content placeholders29.

Modify the default SharePoint content placeholders {R29}: us/sharepointdesigner/HA101651201033.aspx?pid=CH100667701033


Page 63

for editing.

With the master page open in Office SharePoint Designer 2007, double-click the

navigation pane and click Check In.


For more information on customising breadcrumb navigation via Office SharePoint Designer 2007,

667701033



4.3.4 Web Parts

A Content Query, Summary Links or Table of Contents You can also prevent authors from inserting navigation Web Parts by configuring permissions for navigation Web Parts. Do this by

1. Adding the Web Part to a Web Part

2. Finding the appropriate

3. Adding a Content Query, Summary Links or Table

4. Configuring permissions for

These actions are discussed below.Important

The site which hosts the page layout must havthese Web Parts to be added. ThiCollaboration Portal) are used. It is possible to activate on how to do this can be found in

4.3.4.1 Adding the Web

To insert a Content Query, Summary Links orlayout, the Web Part must be available in the Web Parts Gallery of the topcollection.

The information recorded in section Query, Summary Links or Table of Contents Web Parts

To add a Web Part to the Web Parts Gallery:

1. Navigate to the top-level site in the site collection, for example, as created in sect



Content Query, Summary Links or Table of Contents Web Part can be addedprevent authors from inserting navigation Web Parts by configuring permissions for

his by:

dding the Web Part to a Web Parts Gallery.

iate page layout

Adding a Content Query, Summary Links or Table of Contents Web Part

ermissions for navigation Web Parts.

are discussed below.

The site which hosts the page layout must have the SharePoint Publishing feature activated in order for s to be added. This will be done automatically if certain site templates (

used. It is possible to activate the Publishing feature manuallyon how to do this can be found in Enable publishing features {R8}.

eb Part to a Web Parts Gallery

a Content Query, Summary Links or Table of Contents Web Part into a publishing page must be available in the Web Parts Gallery of the top-level site in the site

The information recorded in section 3.4.2 will help determine which top-level sites require Content Query, Summary Links or Table of Contents Web Parts to be added to their Web Part galleries

to the Web Parts Gallery:

level site in the site collection, for example, as created in sect



Page 64

can be added to a page layout. prevent authors from inserting navigation Web Parts by configuring permissions for

of Contents Web Part.

SharePoint Publishing feature activated in order for s will be done automatically if certain site templates (for example,

eature manually; more information

into a publishing page level site in the site

level sites require Content added to their Web Part galleries.

level site in the site collection, for example, as created in section 4.1.



3. On the Site Settings page, u

4. Click New.


� If the Content Query Web Part is missing from the gallery,Microsoft.SharePoint.Publishing.WebControls.ContentByQueryWebPart

� If the Summary Link Web Part is missing from the gallery,Microsoft.SharePoint

� If the Table of Contents Web Part is missing from the gallery,Microsoft.SharePoint.Publishing.WebControls.SummaryLinkWebPart

6. Click Populate Gallery

4.3.4.2 Finding the Appropriate

Once the Web Parts have been added to the appropriate Web Parts Gallery, identify the page layout that will have the Web Parts added to it. Plan Layout Pages worksheetParts added to them.

To identify the appropriate page layout which will have the navigation Web Part added to it:

1. Browse to the publishing site


3. In the Page Layout section, scroll through the available page layouts for the site and make a note of the appropriate page layout.


page, under Galleries, click Web Parts.

one of the following:

If the Content Query Web Part is missing from the gallery, select the Microsoft.SharePoint.Publishing.WebControls.ContentByQueryWebPart

If the Summary Link Web Part is missing from the gallery, select the Microsoft.SharePoint.Publishing.WebControls.SummaryLinkWebPart

If the Table of Contents Web Part is missing from the gallery, select Microsoft.SharePoint.Publishing.WebControls.SummaryLinkWebPart

Populate Gallery.

Appropriate Page Layout

Once the Web Parts have been added to the appropriate Web Parts Gallery, identify the page layout that will have the Web Parts added to it. The information recorded in section

worksheet will help determine what page layouts will have navigation W


publishing site.

menu, click Create Page.

section, scroll through the available page layouts for the site and make a note of the appropriate page layout.


Page 65

the Microsoft.SharePoint.Publishing.WebControls.ContentByQueryWebPart option.

the .Publishing.WebControls.SummaryLinkWebPart option.

elect the Microsoft.SharePoint.Publishing.WebControls.SummaryLinkWebPart option.

Once the Web Parts have been added to the appropriate Web Parts Gallery, identify the page The information recorded in section 3.4.2 and in the

e layouts will have navigation Web


section, scroll through the available page layouts for the site and make


4.3.4.3 Adding a Content Query, Summary Links or Table of Contents Web Part

A layout page can contain one or more Content Query, Summary Links and Table of Contents Web Parts. This section describes how to add one or more of them to a page layout.

4.3.4.3.1 Adding a Conte

By adding a Content Query Webcustom query will appear on every publishing page that is created from that page layout.

The information recorded in section determine what page layouts will have Content Query Web Parts added

To add a Content Query Web Part

1. Follow the steps outlined in section

2. In Office SharePoint Designer 2007, on the that contains the page layout where the Content Query Web Part is to be displayedexample, http://moss.contoso.com


4. Double-click the page layout which will have the Content Query Web Part added to it.

Note

Page layouts have an .aspx file exbrowser. This can make it difficult to find the ‘Site Directory Home’ is right-clicking an .aspx appears in the browser

5. On the Task Panes menu, click


Adding a Content Query, Summary Links or Table of Contents Web

can contain one or more Content Query, Summary Links and Table of Contents Web Parts. This section describes how to add one or more of them to a page layout.

Adding a Content Query Web Part

Web Part to a page layout, links to pages or other items based on a custom query will appear on every publishing page that is created from that page layout.

The information recorded in section 3.4.2 and in the Plan Layout Pages worksheetdetermine what page layouts will have Content Query Web Parts added to them.

uery Web Part to a page layout:

Follow the steps outlined in section 4.3.4.1 and 4.3.4.2.

In Office SharePoint Designer 2007, on the File menu, click Open Site that contains the page layout where the Content Query Web Part is to be displayed

contoso.com).

Click the plus sign (+) next to the _catalogs folder to expand it, and then expand the

click the page layout which will have the Content Query Web Part added to it.

Page layouts have an .aspx file extension. The filename may differ to the title browser. This can make it difficult to find the correct .aspx file for a page layout‘Site Directory Home’ is displayed in a browser, the file is stored as TabViewPageLayout.aspx. By

file, and then selecting Properties on the shortcut menuappears in the browser can be seen in the Title box.

menu, click Web Parts.


Page 66

Adding a Content Query, Summary Links or Table of Contents Web

can contain one or more Content Query, Summary Links and Table of Contents Web Parts. This section describes how to add one or more of them to a page layout.

Part to a page layout, links to pages or other items based on a custom query will appear on every publishing page that is created from that page layout.

worksheet will help them.

Open Site and select the site that contains the page layout where the Content Query Web Part is to be displayed (for

and then expand the

click the page layout which will have the Content Query Web Part added to it.

name may differ to the title that is displayed in a for a page layout. For example, whilst

TabViewPageLayout.aspx. By on the shortcut menu, the name that


6. In the Web Parts task pane, browse the gallery for the appropriate Web site, such as Home Gallery, for the

Tip

If the Content Query Web Part is not visible, make sure that the Web are correct. To change the filtechange which Web Parts in the current gallery are displayed in the list.

7. Drag the Content Query Web Partin the page.

8. On the File menu, click

9. Click Yes when the Site Definition Page Warningcreated based on the customised page layout will include the Content Query Web Part.


task pane, browse the gallery for the appropriate Web site, such as , for the Content Query Web Part.

Web Part is not visible, make sure that the Web Part gallery and filter correct. To change the filter settings, click Filter, and then click an option in the

change which Web Parts in the current gallery are displayed in the list.

Content Query Web Part onto the content placeholder. The Web Part is inserted

, click Save.

Site Definition Page Warning dialog box appears.created based on the customised page layout will include the Content Query Web Part.


Page 67

task pane, browse the gallery for the appropriate Web site, such as

art gallery and filter settings , and then click an option in the Show list to

onto the content placeholder. The Web Part is inserted

dialog box appears. Any page that is created based on the customised page layout will include the Content Query Web Part.


4.3.4.3.2 Adding a Summary

By adding a Summary Links Web Part to a page layout, a list of hyperlinks will appear on every publishing page that is created from that page layout.

The information recorded in sectiondetermine what page layouts will have Summary Links Web Parts added

To add a Summary Link Web Part to a page layout:


2. In Office SharePoint Designer 2007, on the that contains t the page layout where the summary links is to be displayedhttp://moss.contoso.com


4. Double-click the page layout which will have the Summary Links Web Part added to it. The page layout opens for editing.

Note

Page layouts have an .aspx file extension.browser. This can make it difficult to find the correct ‘Site Directory Home’ is displayed in right-clicking an .aspx file, and thappears in the browser



Summary Links Web Part

By adding a Summary Links Web Part to a page layout, a list of hyperlinks will appear on every publishing page that is created from that page layout.

section 3.4.2 and in the Plan Layout Pages worksheet will help determine what page layouts will have Summary Links Web Parts added to them.

ink Web Part to a page layout:


ePoint Designer 2007, on the File menu, click Open Site that contains t the page layout where the summary links is to be displayed

contoso.com).

Click the plus sign (+) next to the _catalogs folder to expand it, and then

click the page layout which will have the Summary Links Web Part added to it. The page layout opens for editing.


aspx file, and then selecting Properties on the shortcut menu, the name that appears in the browser can be seen in the Title box.



Page 68

By adding a Summary Links Web Part to a page layout, a list of hyperlinks will appear on every

worksheet will help them.

Open Site and select the site that contains t the page layout where the summary links is to be displayed (for example,

then expand the

click the page layout which will have the Summary Links Web Part added to it. The


browser, the file is stored as TabViewPageLayout.aspx. By on the shortcut menu, the name that


6. In the Web Parts task pane, browse through the gallery for the appropriate Web site, such as Home Gallery, for the

Tip

If the Summary Link Web Part is not visible, make sure that the Web are correct. To change the filterchange which Web Parts in the current gallery are displayed in the list.

7. Drag the Summary Link Web Partin the page.

8. To modify the layout or appearance of the Summary Link Web Partin Design view, and then click

9. In the Summary Link Web Partthen click OK.


task pane, browse through the gallery for the appropriate Web site, such , for the Summary Link Web Part.

Web Part is not visible, make sure that the Web Part gallery and filter correct. To change the filter settings, click Filter, and then click an option in the

change which Web Parts in the current gallery are displayed in the list.

Summary Link Web Part onto the content placeholder. The Web Part is inserted

To modify the layout or appearance of the Summary Link Web Part, rightview, and then click Web Part Properties on the shortcut menu.

Summary Link Web Part dialog box, change the properties where appropriate, and


Page 69

task pane, browse through the gallery for the appropriate Web site, such

art gallery and filter settings , and then click an option in the Show list to

onto the content placeholder. The Web Part is inserted

right-click the Web Part on the shortcut menu.

dialog box, change the properties where appropriate, and



11. Click Yes when the Site Definition Page Warningcreated based on the customised page layout will include the Summary Links Web Part.

4.3.4.3.3 Adding a Table of C

The Table of Contents Web Part can be added to a page layout to allow the site map to appear on every publishing page that is created from that page layout.

The information recorded in section determine what page layouts will have Table of Contents Web Parts added to them.

Note

Typically, a Web Part is added to a Web Part zone. However, in the following proceduis not used. This is based on the assumption that every publishing page created from the page layout should show the same version of the Web Part.

To add a Table of Contents Web Part to a page layout:


2. In Office SharePoint Designer 2007, on the that contains the page layout where the Table of Contents Web Part is to be displayedexample, http://moss.contoso.com


4. Double-click the page layout which will have the Table of Contents Web Part added to it.

Note

Page layouts have an .aspx file extension. browser. This can make it difficult to find the correct ‘Site Directory Home’ is displayed inright-clicking an .aspx file, and then selecting appears in the browser


, click Save.

Site Definition Page Warning dialog box appears.created based on the customised page layout will include the Summary Links Web Part.

able of Contents Web Part

The Table of Contents Web Part can be added to a page layout to allow the site map to appear on every publishing page that is created from that page layout.

The information recorded in section 3.4.2 and in the Plan Layout Pages worksheet will help determine what page layouts will have Table of Contents Web Parts added to them.

Typically, a Web Part is added to a Web Part zone. However, in the following proceduis not used. This is based on the assumption that every publishing page created from the page layout should show the same version of the Web Part.

To add a Table of Contents Web Part to a page layout:


In Office SharePoint Designer 2007, on the File menu, click Open Site that contains the page layout where the Table of Contents Web Part is to be displayed

contoso.com).

Click the plus sign (+) next to the _catalogs folder to expand it, and then

click the page layout which will have the Table of Contents Web Part added to it.


aspx file, and then selecting Properties on the shortcut menu, the name that appears in the browser can be seen in the Title box.


Page 70

dialog box appears. Any page that is created based on the customised page layout will include the Summary Links Web Part.

The Table of Contents Web Part can be added to a page layout to allow the site map to appear on

worksheet will help determine what page layouts will have Table of Contents Web Parts added to them.

Typically, a Web Part is added to a Web Part zone. However, in the following procedure, a Web Part zone is not used. This is based on the assumption that every publishing page created from the page layout

Open Site and select the site that contains the page layout where the Table of Contents Web Part is to be displayed (for

then expand the

click the page layout which will have the Table of Contents Web Part added to it.


browser, the file is stored as TabViewPageLayout.aspx. By on the shortcut menu, the name that



6. In the Web Parts task pane, browse through the gallery for the appropriate Web sitas Home Gallery, for the

Tip

If the Table of Contents Web Part is not visible, make sure that the Web settings are correct. To change the filterlist to change which Web Parts in the current gallery are displayed in the list.

7. Drag the Table of Contents Web Partinserted in the page.

8. To preview the page layout with the Table of Contents Web Part in it, click Browser on the Common



task pane, browse through the gallery for the appropriate Web sit, for the Table of Contents Web Part.

If the Table of Contents Web Part is not visible, make sure that the Web Part gallery and filter correct. To change the filter settings, click Filter, and then click an option in the

list to change which Web Parts in the current gallery are displayed in the list.

Table of Contents Web Part onto the content placeholder. The Web Part is

To preview the page layout with the Table of Contents Web Part in it, click Common toolbar. The page is displayed in the browser.


Page 71

task pane, browse through the gallery for the appropriate Web site, such

art gallery and filter , and then click an option in the Show

list to change which Web Parts in the current gallery are displayed in the list.

onto the content placeholder. The Web Part is

To preview the page layout with the Table of Contents Web Part in it, click Preview in toolbar. The page is displayed in the browser.



10. Click Yes when the Site Definition Page Warning created based on the customised page layout will include the Table of Contents Web Part.

4.3.4.4 Configuring Permissions for

After Web Parts have been added to on them. This will allow Web Partyou also want to prevent authors gallery permissions.

The information recorded in theworksheet will help determine

To configure Web Parts gallery permissions:

1. Navigate to the top-level site in the site collection (for example,


3. On the Site Settings page, u


, click Save.

Site Definition Page Warning dialog box appears.created based on the customised page layout will include the Table of Contents Web Part.

ermissions for Navigation Web Parts

Web Parts have been added to layout pages, you may also want to include Web Part zones Web Parts to be added to a page at the time of provisioningauthors inserting navigation Web Parts, you must configure

The information recorded in the Restrictions and Notes column of the Plan Layout Pagesworksheet will help determine which restrictions to apply on navigation Web Part

To configure Web Parts gallery permissions:

level site in the site collection (for example, http://moss.


page, under Galleries, click Web Parts.


Page 72

dialog box appears. Any page that is created based on the customised page layout will include the Table of Contents Web Part.

include Web Part zones to be added to a page at the time of provisioning. However, if

you must configure Web Parts

Plan Layout Pages Web Parts.

moss.contoso.com/)




5. Under Permissions and Management,

6. On the Permissions: Web Part Gallery page, select the users or groupto configure permissions (

7. On the Actions menu, click

8. On the Edit Permissions: Web Part Gallery page in the select the permission level for the user

9. Click OK.

4.4 Develop Web Pages


4.4.1 Master Pages

Using the completed Plan Master Pwill use. By default, a site will inherit the master page from its parent site andis required. However, it is possible for a site to use a different outpage.


menu, click Gallery Settings.

Permissions and Management, click Permissions for this gallery

On the Permissions: Web Part Gallery page, select the users or groupsto configure permissions (for example, Approvers).

menu, click Edit User Permissions.

On the Edit Permissions: Web Part Gallery page in the Choose Permissions select the permission level for the users or groups (for example, Full Control).

Pages

DEVELOP


Content Types

Plan Master Pages worksheet, it is possible to define the master page a site will use. By default, a site will inherit the master page from its parent site and, therefore, is required. However, it is possible for a site to use a different out-of-the-box or custom master


Page 73

gallery.

s for whom you wish

Choose Permissions section, Full Control).


it is possible to define the master page a site therefore, no action

box or custom master


4.4.1.1 Out-of-the-Box

In the Plan Master Pages worksheet, if in the box master page is to be used. column of the Plan Master Pages

To use an out-of-the-box master page:

1. Navigate to the site which


3. Under Look and Feel, click

4. In the Site Master Page

� To specify that the site uses a different master page, select the page to be used by the site and all sites that inherit from it appropriate master page from the dr

� To specify that all subsites inherit the new setting, select the inherit this Site Master Page setting

5. To select the most appropriate CSS,

a. Do one of the following:

� To inherit a different CSS from the parent of the current site select the Alternate CSS URL from parent of this site

� To use a CSS file for the current publishing site and all subsites, select the a CSS file to be used by this publishing site and all sites that inherit from it option, and use the

b. To ensure all subsites inherit the new CSS, select the this alternate CSS URL

6. Click OK.

4.4.1.2 Custom Master Pages

In the Plan Master Pages worksheet, if in the master page is to be used. In the copy, paste and edit is specified.

This section outlines how to develop template.


ox Master Pages

worksheet, if in the Custom? column No is selected, then an outbox master page is to be used. The type of master page to use is specified in the

ages worksheet.

box master page:

Navigate to the site which is to have a different master page than its parent.

menu, click Site Settings.

, click Master page.

Site Master Page section, do one of the following:

To specify that the site uses a different master page, select the Specify as master page to be used by the site and all sites that inherit from it option, and appropriate master page from the drop-down list.

To specify that all subsites inherit the new setting, select the Reset all subsites to inherit this Site Master Page setting option.

To select the most appropriate CSS, in the Alternate CSS URL section:

o one of the following:

ifferent CSS from the parent of the current site select the Alternate CSS URL from parent of this site option.

To use a CSS file for the current publishing site and all subsites, select the a CSS file to be used by this publishing site and all sites that inherit from it

use the Browse button to find the CSS file.

To ensure all subsites inherit the new CSS, select the Reset all subsites to inherit this alternate CSS URL option.

Custom Master Pages

worksheet, if in the Custom? column Yes was selectedIn the Custom? column, in the Based on section, the master page to

and edit is specified.

develop and implement a custom master page based on an existing


Page 74

, then an out-of-the-specified in the Master Page

have a different master page than its parent.

Specify as master option, and choose the

Reset all subsites to

section:

ifferent CSS from the parent of the current site select the Inherit

To use a CSS file for the current publishing site and all subsites, select the Specify a CSS file to be used by this publishing site and all sites that inherit from it

Reset all subsites to inherit

was selected, then a custom section, the master page to

based on an existing


4.4.1.2.1 Create a Custom

To create a master page, it is advised that the site administrator saves existing master page, such as Default.master.

Recommendation

Store new master pages in the same folder as existing master pages. This makes master pages easy to find and manage.

Note

When a master page is copied, all content pages that are attached to the original master page (in tcase, Default.master), remain attached to the original master page and not to the copy.

If unwanted changes are made to master page to the site definition. For more information, see definition30.

To copy and paste an existing master page:

1. In Office SharePoint Designer 2007, on the which is to use a custom master page

2. In the Folder List, right

3. Right-click the masterpage

A new master page named default_copy(1).master appears.

4.4.1.2.2 Customise Styles

In the Plan Master Pages worksheet, the customisations. It is possible to customisSharePoint Designer 2007.

To customise the style of a master page


30 Reset a customized page to the site definitionhttp://office.microsoft.com/en-us/sharepointdesigner/HA101741451033.aspx


ustom Master Page

To create a master page, it is advised that the site administrator saves and edits s Default.master.

Store new master pages in the same folder as existing master pages. This makes master pages easy to

When a master page is copied, all content pages that are attached to the original master page (in tcase, Default.master), remain attached to the original master page and not to the copy.

unwanted changes are made to a master page (such as Default.master), it is possible to reset to the site definition. For more information, see Reset a customized page to the site

To copy and paste an existing master page:

In Office SharePoint Designer 2007, on the File menu, click Open Site use a custom master page (for example, http://moss.contoso.com

, right-click Default.master, and then click Copy.

masterpage folder, and then click Paste.

A new master page named default_copy(1).master appears.

Styles

worksheet, the Notes column will contain details of CSS style It is possible to customise the style of a master page using the CSS tools in Office

customise the style of a master page:

Follow the steps outlined in section 4.4.1.2.1.

Reset a customized page to the site definition {R30}: us/sharepointdesigner/HA101741451033.aspx


Page 75

and edits a copy of an

Store new master pages in the same folder as existing master pages. This makes master pages easy to

When a master page is copied, all content pages that are attached to the original master page (in this case, Default.master), remain attached to the original master page and not to the copy.

, it is possible to reset the eset a customized page to the site

Open Site and select the site contoso.com).

column will contain details of CSS style using the CSS tools in Office

http://office.microsoft.com/en-us/sharepointdesigner/HA101741451033.aspx


2. Click default_copy(1).master.

3. If the Apply Styles task pane is not visible, on the

4. In the Apply Styles task pane, Selection.

Each style applied to the area where the cursor is located is outlined in blue, and a preview of the style appears inside the outline.

In the example below, div.msApply Styles task pane, three styles that are applied to div.mstop style, Div.ms-titleareaframe, defines the background colour.

Note

Because styles are caselowercase div.ms-titleareaframe


Click default_copy(1).master.

task pane is not visible, on the Task Panes menu, click

In the Apply Styles task pane, on the Options menu, click Show Styles Used On

Each style applied to the area where the cursor is located is outlined in blue, and a preview of the style appears inside the outline.

, div.ms-titleareaframe has been selected in the Design view. In the Apply Styles task pane, three styles that are applied to div.ms-titleareaframe appear. The

titleareaframe, defines the background colour.

Because styles are case-sensitive, the uppercase Div.ms-titleareaframe is different from the titleareaframe.


Page 76

menu, click Apply Styles.

Show Styles Used On

Each style applied to the area where the cursor is located is outlined in blue, and a preview

Design view. In the titleareaframe appear. The

is different from the


5. Right-click the style that is to be modified, and then click is the number of instances in which the style is applied on the pag

6. After all instances of the style have been selected, rightModify Style.

7. In the Modify Style dialog box, make the desired changes, and then click

More information on applying custom style sheets can be found in SharePoint site31.

It is possible to reset the site definition to ignore any style customisee Reset a customized page to the site

4.4.1.2.3 Customise Content

By default, most of the content on master pages, such as Default.master, is not coded on the page but instead comes from ASP.NET SharePoint Web controls. For example, the text appears in the leftmost region of the default home page (defaulcontent placeholder control that retrieves the content from the server. The text appear inside HTML tags in Code view.

In the Plan Master Pages worksheet, the custom content for content placeholders.

31 Apply a custom style sheet to a SharePoint sitehttp://office.microsoft.com/en-us/sharepointdesigner/HA101691741033.aspx


click the style that is to be modified, and then click Select All X Instance(s)is the number of instances in which the style is applied on the page, for example,

After all instances of the style have been selected, right-click the style again, and then click

dialog box, make the desired changes, and then click

More information on applying custom style sheets can be found in Apply a custom style sheet to a

It is possible to reset the site definition to ignore any style customisations. For more information, Reset a customized page to the site definition {R30}.

ontent Placeholders

By default, most of the content on master pages, such as Default.master, is not coded on the page but instead comes from ASP.NET SharePoint Web controls. For example, the text appears in the leftmost region of the default home page (default.aspx), is supplied by an ASP.NET content placeholder control that retrieves the content from the server. The text appear inside HTML tags in Code view.

worksheet, the Notes column will contain the details necustom content for content placeholders.

Apply a custom style sheet to a SharePoint site {R31}: us/sharepointdesigner/HA101691741033.aspx


Page 77

Instance(s) (where X e, for example, 3).

click the style again, and then click

dialog box, make the desired changes, and then click OK.

Apply a custom style sheet to a

ations. For more information,

By default, most of the content on master pages, such as Default.master, is not coded on the page but instead comes from ASP.NET SharePoint Web controls. For example, the text ‘Team Site‘ that

is supplied by an ASP.NET content placeholder control that retrieves the content from the server. The text ‘Team Site’ does not

needed to create



To create custom content for content placeholders:

1. In Office SharePoint Designer 2007, on the appropriate site (for example,

2. In the Folder List task panedefault_copy(1).master,

3. To open the Master PageMaster Page.


o create custom content for content placeholders:

In Office SharePoint Designer 2007, on the File menu, click Open Site appropriate site (for example, http://moss.contoso.com).

task pane, right-click the appropriate master page, for example default_copy(1).master, and then click Open.

Master Page toolbar, on the View menu, point to Toolbars


Page 78

Open Site and select the

the appropriate master page, for example

Toolbars, and then click


4. To select the content placeholder that is to be modified

� Select the content placeholder from the design view of the master page.

� On the Master Pageand then click the appropriate content placeholder.

5. Right-click the content placeholder and use the shortcut menu to customise the content placeholder as appropriate.


7. Click Yes when the Site Definition Page Warning

More information on how to locate and modify default content placeholders can be found in the default SharePoint content placeholders

It is possible to reset the site definition to ignore any content placeholder customiinformation, see Reset a customized page to the site definition

4.4.1.2.4 Add a New Content

It is possible to add a new content region to a master page by adding a content placeholder in Office SharePoint Designer 2007. contain details of the master pages that require content regions to be added to them.

Note

Content placeholders cannot be inserted inside other content placeholders.


placeholder that is to be modified, do one of the following:

Select the content placeholder from the design view of the master page.

Page toolbar, click the drop-down arrow to the right of the and then click the appropriate content placeholder.

click the content placeholder and use the shortcut menu to customise the content placeholder as appropriate.

, click Save.

Site Definition Page Warning dialog box appears.

More information on how to locate and modify default content placeholders can be found in the default SharePoint content placeholders {R29}.

It is possible to reset the site definition to ignore any content placeholder customiReset a customized page to the site definition {R30}.

ontent Region to a Master Page

It is possible to add a new content region to a master page by adding a content placeholder in Office SharePoint Designer 2007. In the Plan Master Pages worksheet, the Notescontain details of the master pages that require content regions to be added to them.

Content placeholders cannot be inserted inside other content placeholders.


Page 79

do one of the following:

Select the content placeholder from the design view of the master page.

arrow to the right of the Region box,

click the content placeholder and use the shortcut menu to customise the content

alog box appears.

More information on how to locate and modify default content placeholders can be found in Modify

It is possible to reset the site definition to ignore any content placeholder customisations. For more

It is possible to add a new content region to a master page by adding a content placeholder in Notes column will

contain details of the master pages that require content regions to be added to them.


To add a content placeholder:

1. In Office SharePoint Designer 2007, on the appropriate site (for example

2. In the Folder List task panedefault_copy(1).master,

3. Right-click an empty area of the page in Design view, and then click ASP.NET Content Regions

4. In the Manage Content Regionsthe new content region, and then click

Note

If the Add button is not visibleMicrosoft ASP.NET Content Regions

5. Click Close. A new content pl

It is possible to reset the site definition to ignore any content region customiinformation, see Reset a customized page to the site definition


To add a content placeholder:


In the Folder List task pane, right-click the appropriate master page, for example default_copy(1).master, and then click Open.

click an empty area of the page in Design view, and then click Manage Microsoft ASP.NET Content Regions on the shortcut menu.

Manage Content Regions dialog box, in the Region name text the new content region, and then click Add.

button is not visible, make sure a placeholder was not selected before clicking Microsoft ASP.NET Content Regions on the shortcut menu.

. A new content placeholder appears.

It is possible to reset the site definition to ignore any content region customisations. Reset a customized page to the site definition {R30}.


Page 80


the appropriate master page, for example

Manage Microsoft

text box, type a name for

t selected before clicking Manage

ations. For more


4.4.1.2.5 Apply the New

After creating a custom master page, it is possible to make it the default master page for an entire site in Office SharePoint Designer 2007Custom? columns will contain details of

To apply a new custom master page:

1. In Office SharePoint Designer 2007, on the appropriate site (for example,

2. In the Folder List task pane, in the new default master, and then click

Note

The Set as Default Master Page

3. If the content regions in the new default master match the content regions in the site's content pages, when the Otherwise, click No.

More information on content regions and content placeholders can be found inSharePoint content placeholders

Note

When a new master page is set as the default master page, all of the pages that are attached to the current version of Default.master, including the pages that already exist in the sitpages that are attached to Default.master, will be attached to the new master page.


ew Custom Master Page

After creating a custom master page, it is possible to make it the default master page for an entire in Office SharePoint Designer 2007. In the Plan Master Pages worksheet, the

will contain details of which master page each site should use.

To apply a new custom master page:


task pane, in the masterpage folder, right-click the page that is to be the new default master, and then click Set as Default Master Page.

Master Page command is not available on the current default

If the content regions in the new default master match the content regions in the site's when the Set as Default Master Page dialog box displays,

More information on content regions and content placeholders can be found in SharePoint content placeholders {R29}.

When a new master page is set as the default master page, all of the pages that are attached to the current version of Default.master, including the pages that already exist in the site as well as any new pages that are attached to Default.master, will be attached to the new master page.


Page 81

After creating a custom master page, it is possible to make it the default master page for an entire worksheet, the Master Page and

master page each site should use.


click the page that is to be the

current default master page.

If the content regions in the new default master match the content regions in the site's dialog box displays, click Yes.

Modify the default

When a new master page is set as the default master page, all of the pages that are attached to the e as well as any new

pages that are attached to Default.master, will be attached to the new master page.


4.4.2 Content Pages

Use the Plan Content Pages (Article)modify content pages (also known as page content types).

To modify a content page:

1. Using the identity of an administrative user, open the SharePoint site that will host the page content type.

2. Click Site Actions, and then Modify All Site Settings

3. On the Site Settings page,

4. On the Site Content Type Gallery page, click the appropriate content page (Layout Content Typeavailable.

5. On the Site Content Type

6. In the Column name text box, enter a name for the column. specify the type of information.

7. Click OK.

8. Repeat steps 5 to 7 for all columns that are needed.

9. Repeat steps 1 to 8 for all content pages.


Plan Content Pages (Article) and Plan Content Pages (Welcome) worksheets to help content pages (also known as page content types).

Using the identity of an administrative user, open the SharePoint site that will host the page

, and then Site Settings. If presented with a larger menu, Modify All Site Settings.

page, under Galleries, click Site content types.

On the Site Content Type Gallery page, click the appropriate content page (Layout Content Types). By default, Article Page, Redirect Page and W

Site Content Type page, click Add from new site column.

text box, enter a name for the column. Select one of the options tospecify the type of information.

7 for all columns that are needed.

for all content pages.


Page 82

worksheets to help

Using the identity of an administrative user, open the SharePoint site that will host the page


On the Site Content Type Gallery page, click the appropriate content page (under Page Welcome Page are

Select one of the options to


4.4.3 Page Layouts

As outlined previously, a page content type Page content type can use the 'article page with body only' or 'article page with image on left' page layout.

Use the information recorded in the determine whether or not the page layouts in SharePoint Server 2007 is to be used News, Topics, Sites, or My Sites page 2007 and follow the steps below

Note

Layout Pages are only available if the Publishing information.

To edit a page layout in Office

1. In the browser, go to the site which requires the new page layout.


3. Click the Pages document library.

Note

It is also possible to browse directly tohttp://moss.contoso.com

The Pages document library is created automatically by the all of the pages in a site that are cdisplays which page layout was used for a specific page.


page content type can have several page layouts. For example, the Article Page content type can use the 'article page with body only' or 'article page with image on left' page

information recorded in the Notes column of the Plan Layout Pages worksheetpage layouts require customisation. If a page layout already included

is to be used without customisation, no steps are required. My Sites page requires customisation, use Office SharePoint Designer

follow the steps below.

Layout Pages are only available if the Publishing feature is activated; see section 3.3.3

Office SharePoint Designer 2007:

In the browser, go to the site which requires the new page layout.

menu, click View All Site Content.

document library.

also possible to browse directly to the pages document library, for example,contoso.com/pages/forms/allitems.aspx.

The Pages document library is created automatically by the Publishing feature and contains all of the pages in a site that are created from page layouts. The Page Layout column displays which page layout was used for a specific page.


Page 83

several page layouts. For example, the Article Page content type can use the 'article page with body only' or 'article page with image on left' page

worksheet to a page layout already included

no steps are required. If a Home, SharePoint Designer

3.3.3 for more

the pages document library, for example,

ublishing feature and contains reated from page layouts. The Page Layout column


4. Click the desired page layout, such as ArticleRightOffice SharePoint Designer

Alternatively, browse directly tohttp://your_top_level_site/_catalogs/masterpage/page_layout_file_namehttp://moss.contoso.com

It is then possible to customise the page layout by adding custom content, inserting a page and inserting a content field. These will now be discussed.

4.4.3.1 Insert a Page Field or Content Field

Details of the page field, or content fieldof the Plan Layout Pages worksheet.

Note

If a default page content type has been customisedeach new column. For example, if a new column called ‘page content type, the page layout should have a

To insert page fields or content fields into editable regions in a page layout:

1. With the page layout open in will have new content added to it

2. Click the arrow that appears, and then click placeholder for editing.

3. If the Toolbox is not visible, on the


Click the desired page layout, such as ArticleRight.aspx, and then click Office SharePoint Designer.

directly to: http://your_top_level_site/_catalogs/masterpage/page_layout_file_name

contoso.com/_catalogs/masterpage/articleright.aspx.

e the page layout by adding custom content, inserting a page These will now be discussed.

Insert a Page Field or Content Field

or content field, to add to a page layout are detailed in the worksheet.

ault page content type has been customised, a content field should be addedeach new column. For example, if a new column called ‘Healthcare Image’ has been added to the Article page content type, the page layout should have a ‘Healthcare Image’ content field to reflect this.


With the page layout open in Office SharePoint Designer 2007, click the placeholder which will have new content added to it.

ick the arrow that appears, and then click Create Custom Content to unlock the placeholder for editing.

is not visible, on the Task Panes menu, click Toolbox.


Page 84

, and then click Edit in Microsoft

http://your_top_level_site/_catalogs/masterpage/page_layout_file_name, for example,

e the page layout by adding custom content, inserting a page field

detailed in the Notes column

should be added to the page layout for Image’ has been added to the Article

Image’ content field to reflect this.


, click the placeholder which

to unlock the


4. From the Page Fieldspage field or contents field to be inserted into the editable region.onto the page.

Note

If the items in the Page Fieldsbeing edited. Page fields and content fields are available only for page layouts.

The columns that were added to a page content type in section will be displayed in the

5. From the File menu, click

4.4.3.2 Add Custom C

It is possible to edit a page layout like any other page that is attached to a master page. When custom content is added to a page layout, that content appears on all publishing pages that are subsequently created from that page layout.

Details of the custom content to add to a page layout Layout Pages worksheet.

To add custom content to a page layout:

1. With the page layout open in will have new content added to it.

2. Click the arrow that appears, and then click placeholder for editing.


Page Fields or Content Fields section of the SharePoint Controlspage field or contents field to be inserted into the editable region. The control is inserted

Page Fields section of the Toolbox are not visible, it is likely a page layout is not being edited. Page fields and content fields are available only for page layouts.

The columns that were added to a page content type in section 4.4.2 (for example, New Column A) will be displayed in the Content Fields section.

menu, click Save.

Content to a Page Layout

It is possible to edit a page layout like any other page that is attached to a master page. When custom content is added to a page layout, that content appears on all publishing pages that are subsequently created from that page layout.

tom content to add to a page layout are detailed in the Notes

To add custom content to a page layout:

With the page layout open in Office SharePoint Designer 2007, click the placeholder which t added to it.

Click the arrow that appears, and then click Create Custom Content to unlock the placeholder for editing.


Page 85

SharePoint Controls, drag the The control is inserted

are not visible, it is likely a page layout is not being edited. Page fields and content fields are available only for page layouts.

(for example, New Column A)

It is possible to edit a page layout like any other page that is attached to a master page. When custom content is added to a page layout, that content appears on all publishing pages that are

Notes column of the Plan

, click the placeholder which

to unlock the


3. Edit this section of the page by using the features that are commonly useFor example:

� Tables – Click Insert

� Graphics – Click and drag images from the

� Text – Click, and then type

� Web Part zone – Insert a Web Part zone to give visitor remove Web Parts, such as views of document libraries and lists.

� Web Parts – Insert views of document libraries, lists, and more

Recommendation

When creating a table that will be added to an existing page, first create the table on a blank page. This will allow the table


5. Click Yes when the Site Definition Pa

4.4.3.3 Associate a Page

It is sometimes necessary to associate a page layout with a different page content type. the page layouts to associate with a page content typeworksheet.

To associate the page layout with a content type:

1. On the Site Actions menu,


Edit this section of the page by using the features that are commonly use

Insert Table on the Table menu to create tables to help align content.

Click and drag images from the Images folder into this section of the page.

and then type, where text should appear.

Insert a Web Part zone to give visitors to the page the option to add or remove Web Parts, such as views of document libraries and lists.

Insert views of document libraries, lists, and more, into the page.

When creating a table that will be added to an existing page, first create the table on a blank page. will allow the table to be created without existing placeholders being modified

menu, click Save.

Site Definition Page Warning dialog box appears.

age Layout with a Page Content Type

It is sometimes necessary to associate a page layout with a different page content type. page layouts to associate with a page content type are detailed in the Plan Layout Pages

To associate the page layout with a content type:



Page 86

Edit this section of the page by using the features that are commonly used to edit pages.

menu to create tables to help align content.

folder into this section of the page.

ors to the page the option to add or remove Web Parts, such as views of document libraries and lists.

into the page.

When creating a table that will be added to an existing page, first create the table on a blank page. being modified.

dialog box appears.

It is sometimes necessary to associate a page layout with a different page content type. Details of Plan Layout Pages

Settings.


2. Under Galleries, click

3. Select Edit Properties

4. In the Associated Content Type

4.5 Develop Document Libraries


This section aims to describe how to worksheet created in section 3.7.2created, as outlined in section

4.5.1 Create a Document Library

Use the Plan Document Librarieseach planned document library

Note

To create a document library, is to be created.

To create a library in a Meeting Workspace site, follow the procedure for customising Meeting Workspace sites. More information can be found in

The e-mail options discussed in the procedure below are not available by default for wiki page libraries.Rather than adding content via e

To create a document library:

1. Navigate to the site which will have the document library (for example, http://moss.contoso.com

32 Customize a Meeting Workspace sitehttp://office.microsoft.com/en-us/sharepointserver/HA100663671033.aspx?pid=CH


, click Master pages and page layouts.

Edit Properties from the drop-down menu for the appropriate page layout.

Associated Content Type section, select the appropriate content type

Document Libraries

DEVELOP


Content Types

This section aims to describe how to develop document libraries. Use the Plan Document Libraries3.7.2 to assist. It is assumed that the appropriate sites have been

lined in section 4.1.

Document Library

Plan Document Libraries worksheet, as outlined in section 3.7.2, to assist in the creation of document library. Each library will have a separate row in the worksheet

To create a document library, the user must have permission to manage lists on the site where the library

To create a library in a Meeting Workspace site, follow the procedure for customising Meeting Workspace sites. More information can be found in Customize a Meeting Workspace site32.

discussed in the procedure below are not available by default for wiki page libraries.Rather than adding content via e-mail, users will be able to edit wiki library pages using a Web browser.

To create a document library:

Navigate to the site which will have the document library (for example, contoso.com/teamsite)

Customize a Meeting Workspace site {R32}: us/sharepointserver/HA100663671033.aspx?pid=CH101181631033#2


Page 87

the appropriate page layout.

section, select the appropriate content type


Plan Document Libraries the appropriate sites have been

to assist in the creation of in the worksheet.

lists on the site where the library

To create a library in a Meeting Workspace site, follow the procedure for customising Meeting Workspace

discussed in the procedure below are not available by default for wiki page libraries. mail, users will be able to edit wiki library pages using a Web browser.

101181631033#2

http://office.microsoft.com/en-us/sharepointserver/HA100663671033.aspx?pid=CH101181631033#2


2. Click View all Site Content

3. On the Site Content Type Gallery page, click Tip

In most circumstances, the

4. Under Libraries, click

5. In the Name text box, type a name for the document libraryInbound Patients.

Note

The name appears at the top of the library page, becomes part of theand appears in navigational elements that help users to find and open the library.

6. In the Description box, type a description of the purpose of the library. The description is optional.

Note

The description appears at the library is to be enabled tolibrary into the description, so that people can easily find it.

7. To add a link to this library on the Quick Launch

8. To enable people to add files to the library by sending them as attachments to emessages, in the Incoming Ethe E-mail address box

Note

The Incoming E-mail e-mail. For more information

33 Introduction to incoming e-mail {R33


View all Site Content.

On the Site Content Type Gallery page, click Create.

In most circumstances, the Site Actions menu can be used to complete the first two steps.

, click Document Library.

box, type a name for the document library, for example, Gastroenterology

The name appears at the top of the library page, becomes part of the address for the library page, and appears in navigational elements that help users to find and open the library.

box, type a description of the purpose of the library. The description is

The description appears at the top of the library page and underneath the name of the library. If the be enabled to receive content by e-mail, it is helpful to enter the e

description, so that people can easily find it.

this library on the Quick Launch, in the Navigation section

people to add files to the library by sending them as attachments to eIncoming E-mail section, click Yes and type the address for the library

box.

section only displays if the site has been enabled to receive content by For more information, see Introduction to incoming e-mail33.

R33}: http://office.microsoft.com/en-us/sharepointserver/HA100823061033.aspx


Page 88

complete the first two steps.

for example, Gastroenterology

address for the library page, and appears in navigational elements that help users to find and open the library.

box, type a description of the purpose of the library. The description is

underneath the name of the library. If the the e-mail address of the

section, select Yes.

people to add files to the library by sending them as attachments to e-mail and type the address for the library in

section only displays if the site has been enabled to receive content by

us/sharepointserver/HA100823061033.aspx



9. To create a version each time a file is checked into the libHistory section, click Yes

Later, it is possible to specify whetherstored, and how many versions of each

10. In the Document Templatetemplate for files that are created in the library

11. Click Create.

4.5.2 Configure Approval

Use the Require Approval column in the section 3.7.2, to assist in the configuration of approval.

To configure approval on a document library:

1. Navigate to the document library (for example, http://moss.contoso.com


3. On the Customise page, under

4. On the Document Library Versioning Settings page, in the select Yes.

5. Click OK. Each document added to the document library will have a Pending status until is approved or rejected


To create a version each time a file is checked into the library, in the DocumentYes.

Later, it is possible to specify whether both major and minor versions of documents are and how many versions of each are tracked.

Template section, select the default file type that is to be used as a template for files that are created in the library, from the drop-down list.

Configure Approval

column in the Plan Document Libraries worksheets, as outlined in , to assist in the configuration of approval.

To configure approval on a document library:

Navigate to the document library (for example, .com/Library1/Forms/Allitems.aspx).

menu, click Document Library Settings.

On the Customise page, under General Settings, click Versioning settings

On the Document Library Versioning Settings page, in the Content Approval

document added to the document library will have a Pending status until ed by an approver.


Page 89

Document Version

of documents are

to be used as a .

worksheets, as outlined in

Versioning settings.

Content Approval section,

document added to the document library will have a Pending status until it


4.5.3 Configure Check

Use the Require check-outs? section 3.7.2, to assist in the configuration of the check

To configure document check




4. On the Document Librclick Yes.

5. Click OK. When a user tries to open a document from the document libraryasked to check-out the document.

4.5.4 Configure Versioning

Use the Versioning Method column in the section 3.7.2, to assist in the configuration of

To configure document versio




Configure Check-Out

column in the Plan Document Libraries worksheets, as outlined in, to assist in the configuration of the check-out of documents.

To configure document check-out on a document library:

Navigate to the document library (for example, contoso.com/Library1/Forms/Allitems.aspx).



On the Document Library Versioning Settings page, in the Require Check Out

When a user tries to open a document from the document libraryout the document.

Versioning

column in the Plan Document Libraries worksheets, as outlined in , to assist in the configuration of document versioning.

To configure document versioning on a document library:




Page 90


Versioning settings.

Require Check Out section,

When a user tries to open a document from the document library, they will be




4. On the Document Library Versioning Settings page, in the section, decide whether to create major or minor versionsnumber of versions to retain.

5. Click OK. The document library will no

4.5.5 Configure Information Rights Management

Use the Require Information Rights Management?worksheets, as outlined in section management on the document library

To configure Information Rights Management

1. Navigate to the document library (http://moss.contoso.com

2. From the Settings menu, click

3. On the Customise page, under Management.

4. On the Information Rights Management (IRM) Settings page, permission to documents in this library on download



On the Document Library Versioning Settings page, in the Document Version History section, decide whether to create major or minor versions, and whether or not to number of versions to retain.

The document library will now have version control.

Configure Information Rights Management

Require Information Rights Management? column in the Plan Document Librariesworksheets, as outlined in section 3.7.2, to assist in the configuration of information rights management on the document library.

Information Rights Management on a document library:



On the Customise page, under Permissions and Management, click Information Rights

On the Information Rights Management (IRM) Settings page, select the permission to documents in this library on download option.


Page 91

settings.

Document Version History and whether or not to limit the

Plan Document Libraries information rights

Information Rights

the Restrict


5. Describe the IRM policy by typing a description.

6. Use the options and text boxes at the bottom of the (IRM) section to define

7. Click OK. The document library will now to it.

4.6 Develop Content


Content types are a reusable group of settings for a category of contentthe form of a Word document)handle content in a consistent way across a site collection. By defining content types for specific kinds of documents or information products, a these groups of content is managed in a consistent way.

Content types can be created for sites, or for lists and libraries. A content type is available to all those sites below it, but not to those above it. Thus, a content type created at the top level of a site collection is available to all sites in the site collection.

Using the Plan a Document Cfor document libraries.

4.6.1 Create a Custom

The following steps outline how to create a documcan be followed for alternative content types, including list, folder, page layout and publishing content types.

The Plan a Document Content Type

To create a document content type:

1. Using the identity of an administrative user, open the SharePoint site that will host the content type.


Describe the IRM policy by typing a permission policy title and permission

ext boxes at the bottom of the Information Rights Management section to define the restrictions that will be applied to documents in this library.

The document library will now enforce restrictions on documents that are added

ontent Types

DEVELOP


Content Types

Content types are a reusable group of settings for a category of content (for example, document) that will enable healthcare organisations to organise, manage, and

handle content in a consistent way across a site collection. By defining content types for specific kinds of documents or information products, a healthcare organisation can ensure that each of

t is managed in a consistent way.

Content types can be created for sites, or for lists and libraries. A content type is available to all those sites below it, but not to those above it. Thus, a content type created at the top level of a site

available to all sites in the site collection.

Content Type worksheet, it is possible to create custom content types

ustom Document Content Type

The following steps outline how to create a document content type at the site level. Similar steps can be followed for alternative content types, including list, folder, page layout and publishing

Content Type worksheets detail what sites require a content type.

create a document content type:

Using the identity of an administrative user, open the SharePoint site that will host the


Page 92

permission policy

Information Rights Management will be applied to documents in this library.

enforce restrictions on documents that are added


for example, a Memo in organisations to organise, manage, and

handle content in a consistent way across a site collection. By defining content types for specific organisation can ensure that each of

Content types can be created for sites, or for lists and libraries. A content type is available to all those sites below it, but not to those above it. Thus, a content type created at the top level of a site

it is possible to create custom content types

ent content type at the site level. Similar steps can be followed for alternative content types, including list, folder, page layout and publishing

worksheets detail what sites require a content type.

Using the identity of an administrative user, open the SharePoint site that will host the


2. On the Site Actions menuModify All Site Settings


4. On the Site Content Type Gallery page, click

5. On the New Site Content Type

6. In the Select Parent content type fromcategory, for example,

7. In the Parent Content Type example, Document.

Recommendation

Each document content type should type, or from a content type that is descended from the Document content type. This will ensure that the basic columns for the document types, such as Title and Created By, are present.

8. In the Put this site content type intoname.

9. Click OK to create the content type.


menu, click Site Settings. If presented with a larger menu, also click Modify All Site Settings.

page, under Galleries, click Site content type.

On the Site Content Type Gallery page, click Create.

New Site Content Type page, enter a Name and Description for the content type.

Select Parent content type from drop-down list, select the appropriate content type category, for example, Document Content Types.

Parent Content Type drop-down list, select the appropriate content type, for

Each document content type should inherit its settings directly from the core Document content or from a content type that is descended from the Document content type. This will ensure

that the basic columns for the document types, such as Title and Created By, are present.

t this site content type into section, select New group and enter an appropriate

to create the content type.


Page 93


for the content type.

down list, select the appropriate content type

down list, select the appropriate content type, for

inherit its settings directly from the core Document content or from a content type that is descended from the Document content type. This will ensure

that the basic columns for the document types, such as Title and Created By, are present.

and enter an appropriate


4.6.2 Create Columns

Using the Plan a Document Content Typeappropriate columns for use with the new document content type. Plan a Document Content Type

To create columns for a document content type:

1. On the Site Content Type page, which appears after creating a custom content type, click Add from new site column

2. On the New Site Column

3. In the Group section, select

4. Click OK.

5. To add additional columnsand use the drop-down menu to select the group that NewColumnGroup.

The columns that have been created for the content typein any associated document library.


olumns for the New Custom Content Type

Plan a Document Content Type worksheet, it is possible to create and assappropriate columns for use with the new document content type. The Plan Columns Plan a Document Content Type worksheet, details the columns to add for each content type.

To create columns for a document content type:

On the Site Content Type page, which appears after creating a custom content type, click Add from new site column.

Column page, enter a column name without any spaces.

section, select New group and enter an appropriate name in the text box.

To add additional columns, repeat steps 1 to 4. However, in step 3, selectdown menu to select the group that was previously created

created for the content type will appear as document library document library.


Page 94

ustom Content Type

it is possible to create and associate the Plan Columns section of the

details the columns to add for each content type.

On the Site Content Type page, which appears after creating a custom content type, click

page, enter a column name without any spaces.

and enter an appropriate name in the text box.

select Existing group created, for example,

document library columns


4.6.3 Associate a Content

The Document Libraries Required to UType worksheets detail what content

To associate an out-of-the-box

1. Navigate to the appropriate document library.

2. On the Settings menu, clic

3. Under Content Types

Note

If the list or library is not set up to allow multiple content types, the appear on the Customise page.

4. In the Select Content Typesfrom the Select Site content types from

5. In the Available Site Content TypesAdd to move the selected conte

6. To add additional content types, repeat steps 4 and 5.

7. When all of the content types that are to be added appear in the section, click OK.


ontent Type with a Document Library

Libraries Required to Use Content Type column in the Plan a Document what content types are to be associated with a document library.

box or custom content type with a document library:

Navigate to the appropriate document library.


Types, click Add from existing site content types.

If the list or library is not set up to allow multiple content types, the Content Typesappear on the Customise page.

Content Types section, select the appropriate group of site content types Select Site content types from drop-down list.

Available Site Content Types list, select the appropriate content type, and then click to move the selected content type to the Content types to add list.

To add additional content types, repeat steps 4 and 5.

When all of the content types that are to be added appear in the Content types to add


Page 95

ibrary

Document Content types are to be associated with a document library.

or custom content type with a document library:

Content Types section does not

select the appropriate group of site content types

the appropriate content type, and then click list.

Content types to add


4.6.4 Implement and

Once a content type has been associated with a document library and the appropriate columns have been configured, it is also possible to connect a document template to content type metadata. Three steps are required in order t

1. Create a document template

2. Associate the document template with the new content type

3. Update the document template and connect it to the appropriate metadata

These are described in the following sectionsand libraries described in sections

4.6.4.1 Create a Document

It is possible to create a document

The Plan Template section of the templates to use with the document libraries specified in the Content Type column.

Note

The procedure below details how to create a document template from a blank template. If creating document template from an existing document,

To create a template from a blank template:

1. In Microsoft Office Word 2007, c

2. Select Blank document

3. Make the appropriate changes to the margin settings, page size and orientation, styles, and other formats. It is also possible to add instructional text, content controls picker) and graphics. More information on adding instructional text,protection to a document template can be found in

4. Click the Microsoft Office Button

5. In the Save As dialog box, document template’), selthen click Save.

34 Add content controls to a template {


and Update a Document Template

content type has been associated with a document library and the appropriate columns it is also possible to connect a document template to content type metadata.

hree steps are required in order to do this:

Create a document template.

Associate the document template with the new content type.

Update the document template and connect it to the appropriate metadata

following sections. For simplicity, the example document content types and libraries described in sections 4.6.1 to 4.6.3 are referred to.

ocument Template

document template from a blank template or an existing document.

section of the Plan a Document Content Type worksheet, details the document templates to use with the document libraries specified in the Document Libraries Required to Use

The procedure below details how to create a document template from a blank template. If creating plate from an existing document, only follow steps 3 to7.

To create a template from a blank template:

Word 2007, click the Microsoft Office Button , and then click

Blank document and click Create.

Make the appropriate changes to the margin settings, page size and orientation, styles, and other formats. It is also possible to add instructional text, content controls

More information on adding instructional text, context controls and protection to a document template can be found in Add content controls to a template

Microsoft Office Button , and then click Save As.

dialog box, give the new template a file name (for example, ‘, select Word Template from the Save as type drop

{R34}: http://office.microsoft.com/en-us/word/HA100307541033.aspx#3


Page 96

content type has been associated with a document library and the appropriate columns it is also possible to connect a document template to content type metadata.

Update the document template and connect it to the appropriate metadata.

the example document content types

template from a blank template or an existing document.

details the document Document Libraries Required to Use

The procedure below details how to create a document template from a blank template. If creating a

, and then click New.

Make the appropriate changes to the margin settings, page size and orientation, styles, and other formats. It is also possible to add instructional text, content controls (such as, a date

context controls and Add content controls to a template34.

for example, ‘Memo drop-down list, and

us/word/HA100307541033.aspx#3

http://office.microsoft.com/en-us/word/HA100307541033.aspx#3


Note

It is possible to save the template as

� A Word 2007 Template (.dotx file)

� A Word Macro-Enabled Template

� A Word 97-2003 Template

6. Close the template.

4.6.4.2 Associate Document

The Plan Template section of the templates to use with specific

To associate a document template with a content type:

1. Navigate to the site which hosts the content type.

2. On the Site Actions menModify All Site Settings


4. Click on the appropriate content type, for example,

Note

If a link it not displayed for the appropriate content type, click the corresponding link in the column.

5. On the Site Content Type page, under

6. On the Site Content Type Advanced Settings page, in the select Upload a new document templatetemplate created previously.

7. Click OK.


It is possible to save the template as any of the following:

A Word 2007 Template (.dotx file)

Enabled Template (.dotm file)

2003 Template (.dot file)

ocument Template with a Content Type

section of the Plan a Document Content Type worksheet details the document specific content types.

ment template with a content type:

Navigate to the site which hosts the content type.


On the Site Settings page, under Galleries, click Site content types.

Click on the appropriate content type, for example, MyNewContentType

If a link it not displayed for the appropriate content type, click the corresponding link in the

On the Site Content Type page, under Settings, click Advanced settings

On the Site Content Type Advanced Settings page, in the Document TemplateUpload a new document template and click Browse to locate the document

template created previously.


Page 97

worksheet details the document


MyNewContentType.

If a link it not displayed for the appropriate content type, click the corresponding link in the Source

Advanced settings.

Document Template section, to locate the document


4.6.4.3 Update the Document Metadata

If following sections 4.6.4.1 to embedded in it. Because of this,section 4.6.2. To enable this, the next step is to properties to the document text

The Notes column, of the Plan Templatedetails the metadata binding for the document content type

To add new properties to the document:

1. Navigate to the All Documentsdrop-down menu appears, s

2. If prompted with a warning click OK.

3. When the Word document opens, enter values into the fields in the Panel, which appears above the body of the document.

Note

The fields that appear

� Columns inherited from the parent content type, as chosen in section

� Customised columns, as created in section

4. Click the Microsoft Office Button

5. In the Save As dialog box, give and then click Save

To add the new properties to the document

1. In Word 2007, click the

2. Click Quick Parts to access


ocument Template and Connect the Appropriate

to 4.6.4.2, the document currently will not have the content type embedded in it. Because of this, the document will not show the new columns that were added in

. To enable this, the next step is to add new properties to the document, to the document text, and upload the modified template to the site content type gallery.

Plan Template section, in the Plan a Document Content Typemetadata binding for the document content type.

properties to the document:

All Documents view of the appropriate document library and click down menu appears, select the appropriate content type.

warning message that indicates that some files can harm

When the Word document opens, enter values into the fields in the Document Information , which appears above the body of the document.

that appear in the Document Information Panel are determined by

inherited from the parent content type, as chosen in section 4.6.1

ustomised columns, as created in section 4.6.2

Microsoft Office Button , and then click Save As

dialog box, give the document a file name (for example, ‘

To add the new properties to the document text:

lick the Insert tab to display the Insert ribbon.

to access the drop-down menu.


Page 98

ppropriate

have the content type show the new columns that were added in

new properties to the document, add template to the site content type gallery.

Content Type worksheet

view of the appropriate document library and click New. If a

message that indicates that some files can harm your computer,

Document Information

are determined by:

4.6.1

for example, ‘Memo 1.docx’),


3. Point to Document PropertyThe property, for example,

4. Click the Microsoft Office Buttondrive.

To upload the modified document template to the site content type gallery:

1. Navigate to the site hosting the content type.

2. On the Site Actions menuModify All Site Settings


4. Click on the appropriate content type, for example,

Note

If a link is not displayed for the appropriate content type, click the corresponding link in the column.

5. On the Site Content Type page, under


Document Property and click the property to insert, for example, The property, for example, NewColumA, will be added to the document.

Microsoft Office Button , and then click Save to save the document to a hard


Navigate to the site hosting the content type.


On the Site Settings page, under Galleries, click Site content types.

Click on the appropriate content type, for example, MyNewContentType

not displayed for the appropriate content type, click the corresponding link in the

On the Site Content Type page, under Settings, click Advanced settings


Page 99

and click the property to insert, for example, NewColumnA. ded to the document.

to save the document to a hard



MyNewContentType.

not displayed for the appropriate content type, click the corresponding link in the Source

Advanced settings.


6. On the Site Content Type Advanced Settings page, in the select Upload a new document templatedocument template saved previously.

7. Click OK. The metadata from the content type is now connected to the document template. Thus, the text that is typed into the document.

4.7 Develop Audiences


Before developing audiences, user profiles must be imported.

4.7.1 Import Profiles

To import profiles:


2. In the Quick Launch, click the

3. Under User Profiles and

4. On the User Profiles and Properties page, click

5. On the Configure Profile Import page, in the imported from one of the following:

� Current domain

� Entire Forest

� Custom source


On the Site Content Type Advanced Settings page, in the Document TempUpload a new document template and click Browse to locate the modified

document template saved previously.

The metadata from the content type is now connected to the document template. Thus, the text that is typed into the Document Information Panel will now appear in the

udiences

DEVELOP


Content Types

audiences, user profiles must be imported.


In the Quick Launch, click the appropriate Shared Service, for example,

and My Sites, click User profiles and properties

On the User Profiles and Properties page, click Configure profile import

On the Configure Profile Import page, in the Source section, specify the data will be imported from one of the following:


Page 100

Document Template section, to locate the modified

The metadata from the content type is now connected to the document template. Document Information Panel will now appear in the


Central

Shared Service, for example, SharedServices1.

properties.

import.

section, specify the data will be


6. In the Default Access Account appropriate directory.

Note

This account needs to also have Manage User Profiles rights. To verify this, click on Personalization services permissionspage. It is advised that the SharePoint Administrator account is used.

7. Click OK.

8. On the User Profiles and Properties page, click

9. After import is complete, on the User Profiles and Properties page, click to view the import results.

It is now possible to create audiences.

4.7.2 Create an Audience

The Plan Audiences worksheet details the audiences to create.

Note

Audiences should not be created until a profile import has been completed. For more information, see section 4.7.1.

To create an audience:



3. Under Audiences, click

4. On the Manage Audiences page, click

5. In the Properties section


Default Access Account section, specify an account that has read access to the

This account needs to also have Manage User Profiles rights. To verify this, click on Personalization services permissions under User Profiles and My Sites page. It is advised that the SharePoint Administrator account is used.

On the User Profiles and Properties page, click Start full import.

After import is complete, on the User Profiles and Properties page, click import results.

It is now possible to create audiences.

udience

worksheet details the audiences to create.

Audiences should not be created until a profile import has been completed. For more information, see



, click Audiences.

On the Manage Audiences page, click Create audience.

section, enter a Name, Description and Owner.


Page 101

specify an account that has read access to the

This account needs to also have Manage User Profiles rights. To verify this, click on on the SSP Admin

After import is complete, on the User Profiles and Properties page, click View user profiles

Audiences should not be created until a profile import has been completed. For more information, see

Central



6. In the Add Audience Rule one of the following:

� Active Directory user property

� SharePoint property

7. If Property was selected

a. Use the property dropfor example, Work phone

b. In the operator section, select the most appropriate operator, for example,

c. In the Value section, type in an appropriate value, for example,

8. On the View Audience Properties steps 6-7 to add a new rule. Repeat this until all appropriate rules for the audience have been added. Audiences must now be compi

9. Using the breadcrumb navigation

10. On the Manage Audiences page, click

11. After compilation is complete, on the view the results.

Recommendation

Repeat the above steps for only because Active Directory configuration is likely to differ between stagiThis would require audiences to be manually added

4.7.3 Target Content

Using the Plan Audiences workshee

� List items or Web Parts

� Links published to Office

� My Site navigation bars

� Trusted My Site host locations


Add Audience Rule page, in the operand section, specify if the rule will be based on

Active Directory user property – select User

SharePoint property – select Property

was selected:

Use the property drop-down box to specify the property that the rule will be based on, Work phone.

section, select the most appropriate operator, for example,

section, type in an appropriate value, for example, 0118

View Audience Properties page, click Add Rule to add any additional rules. Follow to add a new rule. Repeat this until all appropriate rules for the audience have

Audiences must now be compiled before they can be used.

Using the breadcrumb navigation, click Manage Audiences.

On the Manage Audiences page, click Start compilation.

After compilation is complete, on the Manage Audiences page, click on

only a small sample of audiences if using a staging environmentconfiguration is likely to differ between staging and production environments.

e audiences to be manually added rather than migrated to the production environment.

ontent

worksheet it is possible to targeted content to groups of users

List items or Web Parts

Links published to Office client applications

My Site navigation bars

Trusted My Site host locations


Page 102

section, specify if the rule will be based on

down box to specify the property that the rule will be based on,

section, select the most appropriate operator, for example, Contains.

0118.

to add any additional rules. Follow to add a new rule. Repeat this until all appropriate rules for the audience have

ed before they can be used.

page, click on View audiences to

if using a staging environment. This is ng and production environments.

rather than migrated to the production environment.

to groups of users through:


4.7.3.1 Target Content via

The List Items and Web PartsWeb Parts to be used to target content to

To configure a list item or Web Part to target a specific audience:

1. Navigate to the page which displays the Web Part.


3. Click edit, and then click

4. In the Web Parts tool pane, expand the

5. In the Target Audiences Paediatricians in Reading

6. Click OK.

7. Repeat steps 1 to 6 for all Web Parts that will target content to audiences.


The Office Client Links column ofused to target content to audiences.

To configure a link published to Office client




Target Content via List Items or Web Parts

columns in the Plan Audiences worksheet details the list items and arts to be used to target content to audiences.

To configure a list item or Web Part to target a specific audience:

Navigate to the page which displays the Web Part.


click Modify Shared Web Part.

pane, expand the Advanced section.

Target Audiences text box, enter the name of the audience, for example, aediatricians in Reading.

for all Web Parts that will target content to audiences.

Target Content via Links Published to Office Client A

column of Plan Audiences worksheet details the Office Client Links to be used to target content to audiences.

To configure a link published to Office client applications to target a specific audience:




Page 103

worksheet details the list items and

text box, enter the name of the audience, for example, New

for all Web Parts that will target content to audiences.

Applications

worksheet details the Office Client Links to be

applications to target a specific audience:

Central



3. Under User Profiles and My Sites

4. Click New > New Item

5. In the URL section, type in the URL and description of the site, document library or data connection library that will have targeted content.

6. In the target audience content.

Note

The document library will appear as a choice whenever someone within the specific audience, for example, New Paediatricians in Reading, shares a document from an Office client

7. Repeat steps 4 to 6 for all links published to office applications that will target content to audiences.


The Personalization Site Links site links to be used to target content to audiences.

To add personalization site navigation links to the My Site horizontal navigation bar:






User Profiles and My Sites, click Published links to Office client applications

New Item.

section, type in the URL and description of the site, document library or data connection library that will have targeted content.

target audience section, type the name of the audience which will receive targeted

The document library will appear as a choice whenever someone within the specific audience, for aediatricians in Reading, shares a document from an Office client

6 for all links published to office applications that will target content to

Target Content via My Site Navigation Bars

inks column of the Plan Audiences worksheet details the personalization site links to be used to target content to audiences.




and My Sites, click Personalization site links.

Item.


Page 104

Published links to Office client applications.

section, type in the URL and description of the site, document library or data

type the name of the audience which will receive targeted

The document library will appear as a choice whenever someone within the specific audience, for aediatricians in Reading, shares a document from an Office client application.

6 for all links published to office applications that will target content to

worksheet details the personalization


Central



5. In the URL section, type in the URL of the personali

6. In the Owner section, type the name of the owner of the group. It is advised that the SharePoint administrator is used.

7. In the Target Audience content.

8. Repeat steps 4 to 7 for all personalization site navigation links that need to appear in audience My Site navigation bars. The added link will appear as a navigation link between My Home and My Profile on the navigation bar.

Note

A link to the portal home page can be addedusers to easily navigate from their My Site to the portal home page. Alternatively, page can be added to My Sites through the use of home page...35 for more information

4.7.3.4 Trusted My Site

The Trusted My Site Host LocationSite host locations to be used to target content to audiences.

To manage a list of Trusted My Site host locations and target each location to audiences:





35You do not see a link to the home page...


section, type in the URL of the personalization site.

section, type the name of the owner of the group. It is advised that the SharePoint administrator is used.

Target Audience section, type the name of the audience which will receive targeted

for all personalization site navigation links that need to appear in audience My Site navigation bars. The added link will appear as a navigation link between My Home and My Profile on the navigation bar.

A link to the portal home page can be added to My Sites by following the above procedure. This will allow users to easily navigate from their My Site to the portal home page. Alternatively, a link to the portal home page can be added to My Sites through the use of portal site connections (see You d

for more information).

Trusted My Site Host Locations

ocation column of the Plan Audiences worksheet details the to be used to target content to audiences.

manage a list of Trusted My Site host locations and target each location to audiences:



and My Sites, click Trusted My Site host locations

Item.

You do not see a link to the home page...{R35}: http://support.microsoft.com/kb/924464


Page 105

section, type the name of the owner of the group. It is advised that the

section, type the name of the audience which will receive targeted

for all personalization site navigation links that need to appear in audience My Site navigation bars. The added link will appear as a navigation link between

to My Sites by following the above procedure. This will allow a link to the portal home

You do not see a link to the

worksheet details the Trusted My

manage a list of Trusted My Site host locations and target each location to audiences:

Central


Trusted My Site host locations.

http://support.microsoft.com/kb/924464


5. In the URL section, type in the URL of the

6. In the Target Audiencespecified location.

Audiences will receive targeted content for the appropriate SSP.


section, type in the URL of the Trusted My Site host location

udiences section, type the name of the audience which need to view the

Audiences will receive targeted content for the appropriate SSP.


Page 106

Trusted My Site host location.

which need to view the


5 STABILISE

The Stabilise phase involves testing the solution components, issues that are found. It is advised environment is used for testing. This will ensure the solution components are used and tested under realistic environmental conditions.

Figure 22 illustrates the critical components which an IT professional responsible for stabilising the SharePoint Server 2007 information architecture needs to determine.


Using Test Computers

Test Procedures


Figure 22: Sequence for Stabilising SharePoint Server 2007

5.1 Testing Considerations

STABILISE



Testing is an important part of any software deployment project and has a number of benefits. Testing allows the administrator to be comfortable with or configuration changes that are about to be made. It is also important to allow the administrator to identify any potential issues that could be introduced, and to plan for them prior to implementation in a production environment.


The Stabilise phase involves testing the solution components, and resolving and prioritising any It is advised that a staging environment that mirrors the production

nvironment is used for testing. This will ensure the solution components are used and tested under realistic environmental conditions.

the critical components which an IT professional responsible for stabilising the information architecture needs to determine.



STABILISE

Test Procedures


Testing is an important part of any software deployment project and has a number of benefits. Testing allows the administrator to be comfortable with the information architectureor configuration changes that are about to be made. It is also important to allow the administrator to identify any potential issues that could be introduced, and to plan for them prior to implementation


Page 107

resolving and prioritising any that a staging environment that mirrors the production

nvironment is used for testing. This will ensure the solution components are used and tested

the critical components which an IT professional responsible for stabilising the

Testing is an important part of any software deployment project and has a number of benefits. ormation architecture implementation

or configuration changes that are about to be made. It is also important to allow the administrator to identify any potential issues that could be introduced, and to plan for them prior to implementation


5.2 Using Test Computers

STABILISE



Before SharePoint Server 2007infrastructure, they should be tested in a controlled environment using test computers that arepresentative of those used in the and the 2007 Office system, a test plan that contains Some example test objectives are:

� Verify that the user expeelements) is as expected. If the installation tailors navigation to audiences, ensure this occurs as expected

� Verify that content types work as expected, including any use of document templates

� Verify that SharePoint Server 2007affect the performance of any other application software

When testing SharePoint Server 2007to ensure that no adverse effects are experienced.

5.3 Test Procedures

STABILISE



The test procedures should give the processes, procedures and endinclude installing or deploying SharePoint Server 2007 {R5}.

The healthcare IT professional should during the course of this document.

The SharePoint 2007 Test Data Population TooServer 2007 server infrastructure with test data, such as documents, list and sites.

36 SharePoint 2007 Test Data Population Tool


Computers

STABILISE

Test Procedures


SharePoint Server 2007 and the 2007 Office system are implemented in the infrastructure, they should be tested in a controlled environment using test computers that arepresentative of those used in the healthcare organisation. When testing SharePoint Server 2007

a test plan that contains the testing objectives should be followedSome example test objectives are:

Verify that the user experience (as configured with sites, Web pages and navigation elements) is as expected. If the installation tailors navigation to audiences, ensure this

Verify that content types work as expected, including any use of document templates

SharePoint Server 2007 performs as expected, and that it does not adversely affect the performance of any other application software

SharePoint Server 2007 and 2007 Office system, follow a defined process for testing adverse effects are experienced.

Test Procedures

STABILISE

Test Procedures


The test procedures should give the healthcare IT professional the ability to run through all and end-user activities that would be carried out in production. Th

SharePoint Server 2007, as outlined in Deployment for Office .

IT professional should also test the configuration that was planned and developed during the course of this document.

SharePoint 2007 Test Data Population Tool36 can be used to populate the test server infrastructure with test data, such as documents, list and sites.

SharePoint 2007 Test Data Population Tool {R36}: http://www.codeplex.com/sptdatapop


Page 108

are implemented in the production infrastructure, they should be tested in a controlled environment using test computers that are

SharePoint Server 2007 should be followed.

pages and navigation elements) is as expected. If the installation tailors navigation to audiences, ensure this

Verify that content types work as expected, including any use of document templates

performs as expected, and that it does not adversely

, follow a defined process for testing

IT professional the ability to run through all that would be carried out in production. This should

Deployment for Office

planned and developed

populate the test SharePoint server infrastructure with test data, such as documents, list and sites.

http://www.codeplex.com/sptdatapop


5.4 Supporting Documents

STABILISE



SharePoint Server 2007 has performance and capacity limitsrequired in order to achieve acfound in the Plan for software boundaries (Office SharePoint Server)and capacity requirements for Windows SharePoint Services collaboration environments (Office SharePoint Server)38.

During stabilisation, critical events may occur that impact the performance of 2007. It is important to be able to diagnose these events and respond to them. More information on detecting and responding to critical Server 2007 Management Pack Guide

37 Plan for software boundaries (Office SharePoint Server)

38 Estimate performance and capacity requirements for Windows SharePoint Services collaboration environments (Office SharePoint Server) {R38}: http://technet.microsoft.com/en

39 SharePoint Server 2007 Management Pack Guide



STABILISE

Test Procedures


has performance and capacity limits, and it is useful to be aware of what is required in order to achieve acceptable performance. More information on these subjects can be

Plan for software boundaries (Office SharePoint Server)37 and Estimate performance and capacity requirements for Windows SharePoint Services collaboration environments (Office

critical events may occur that impact the performance of SharePoint Server . It is important to be able to diagnose these events and respond to them. More information on

detecting and responding to critical SharePoint Server 2007 events can be found in the Server 2007 Management Pack Guide39.

Plan for software boundaries (Office SharePoint Server) {R37}: http://technet.microsoft.com/en-us/library/cc262787.aspx

pacity requirements for Windows SharePoint Services collaboration environments (Office http://technet.microsoft.com/en-us/library/cc261795.aspx

SharePoint Server 2007 Management Pack Guide {R39}: http://go.microsoft.com/fwlink/?LinkID=94824&clcid=0x409


Page 109

and it is useful to be aware of what is ceptable performance. More information on these subjects can be

Estimate performance and capacity requirements for Windows SharePoint Services collaboration environments (Office

SharePoint Server . It is important to be able to diagnose these events and respond to them. More information on

events can be found in the SharePoint


pacity requirements for Windows SharePoint Services collaboration environments (Office






6 DEPLOY

Once the solution has been stabilisedDuring the Deploy phase, the core solution components are deployed for more widespread application and use, and the deployment is stabilised through ongoing monitoring.

Figure 23 illustrates the recommended deploying SharePoint Server 2007

Backup and Restore(Required)

Backup

Other Migration Tools(Optional)

Figure 23: Sequence for Deploying SharePoint Server 2007

To deploy the solution into a production environment aproduction environment should be

1. Running setup and selecting

2. Running the SharePoint Products and Technologies Configuration Wizard to create a new farm, configuration database and farm services

3. Creating Web applications for the Shared Services Provider and fneeded.

4. Creating the Shared Services Provider.

More information on deploying SharePoint Server 2007 {R5}.

To deploy the solution into a production environmentstaging environment. The existing data can be categorised into:

� Content – This is data stored in the Content database, typically created through the user interface or using tools such as hierarchies, site directories, nonplus any documents, files or list items stored within lists or libraries.

� Code – This includes items such as assemblies, XML files and other components related to custom development that reside outside of the content database, on the file system of the SharePoint Web servers. These are typically created using tools such as Visual Studio 2005, and includes custom Web Parts, field controls and site definitions.

It is possible to migrate audiences by using the Backup and Restore tool and specifying to backup and restore the farm. However, as production environments, only a small sample of audiences environment. In this case, audiences must be manually added to a production environment. To do this, follow the steps highlighted in section


Once the solution has been stabilised, it is possible to deploy it into a production environment. During the Deploy phase, the core solution components are deployed for more widespread application and use, and the deployment is stabilised through ongoing monitoring.

recommended tasks which a healthcare IT professional responsible for SharePoint Server 2007 may need to perform.

Backup Restore


To deploy the solution into a production environment an appropriate SharePoint Server should be setup and ready for use. This requires:

Running setup and selecting Complete Server Installation.

Running the SharePoint Products and Technologies Configuration Wizard to create a new farm, configuration database and farm services.

Creating Web applications for the Shared Services Provider and for other content as

Creating the Shared Services Provider.

More information on deploying SharePoint Server 2007 can be found in Deployment for Office .

To deploy the solution into a production environment, all data must be migrated from the existing staging environment. The existing data can be categorised into:

This is data stored in the Content database, typically created through the user interface or using tools such as Office SharePoint Designer. It includes site hierarchies, site directories, non-custom master pages, page layouts and content types;

ny documents, files or list items stored within lists or libraries.

This includes items such as assemblies, XML files and other components related to custom development that reside outside of the content database, on the file system of the

eb servers. These are typically created using tools such as Visual Studio and includes custom Web Parts, field controls and site definitions.

It is possible to migrate audiences by using the Backup and Restore tool and specifying to backup and restore the farm. However, as Active Directory configurations may differ in staging and

only a small sample of audiences should have been created environment. In this case, audiences must be manually added to a production environment. To do this, follow the steps highlighted in section 4.7.


Page 110

it is possible to deploy it into a production environment. During the Deploy phase, the core solution components are deployed for more widespread application and use, and the deployment is stabilised through ongoing monitoring.

IT professional responsible for


Running the SharePoint Products and Technologies Configuration Wizard to create a new

or other content as

Deployment for Office

all data must be migrated from the existing

This is data stored in the Content database, typically created through the Web . It includes site

custom master pages, page layouts and content types;

This includes items such as assemblies, XML files and other components related to custom development that reside outside of the content database, on the file system of the

eb servers. These are typically created using tools such as Visual Studio and includes custom Web Parts, field controls and site definitions.

It is possible to migrate audiences by using the Backup and Restore tool and specifying to backup configurations may differ in staging and

ave been created in a staging environment. In this case, audiences must be manually added to a production environment. To do


6.1 Backup and Restore

DEPLOY

Backup and Restore


To migrate content from the content database within a staging environment to a content database in a production environment, the Backup and used. Using the Backup and Restore feature it is possible to move farms, Web applications, content databases, and Project databases from one server farm ((for example, production).

6.1.1 Backup

Site hierarchies, site directories, any documents, files or list items stored within lists or libraries can be backed up.

To perform a backup:

Note

It is assumed that the destination server has a different name. It is also assumed2007 has only been installed once on the destination server, and has been configured appropriately.

1. In the staging environment, click SharePoint Central Administration

2. Click Operations on the top navigation bar.

3. On the Operations page, under

4. In the Perform a Backup required farm, Web application example, WSS_Content

Note

It is possible to select all farm components by Audiences are backed up.

5. Click Continue to Backup Options

6. In the Start Backup – Step 2 of 2: Select Backup Options page, in the section, select Full.


estore

To migrate content from the content database within a staging environment to a content database the Backup and Restore feature of SharePoint Server 2007

Using the Backup and Restore feature it is possible to move farms, Web applications, content databases, and Project databases from one server farm (for example, staging) to another

ite hierarchies, site directories, non-custom master pages, page layouts and content types; plus any documents, files or list items stored within lists or libraries can be backed up.

It is assumed that the destination server has a different name. It is also assumed that SharePoint Server 2007 has only been installed once on the destination server, and has been configured appropriately.

In the staging environment, click Start > All Programs > AdministrativeAdministration.

on the top navigation bar.

On the Operations page, under Backup and Restore, click Perform a

In the Perform a Backup – Step 1 of 2: Select component to Backup page, Web application (for example, moss.contoso.com), content database

WSS_Content), or project database item.

It is possible to select all farm components by selecting the Farm option. This will ensure that Audiences are backed up.

Continue to Backup Options.

Step 2 of 2: Select Backup Options page, in the Type of backup


Page 111

To migrate content from the content database within a staging environment to a content database SharePoint Server 2007 can be

Using the Backup and Restore feature it is possible to move farms, Web applications, staging) to another

custom master pages, page layouts and content types; plus any documents, files or list items stored within lists or libraries can be backed up.

that SharePoint Server 2007 has only been installed once on the destination server, and has been configured appropriately.

Administrative Tools >

backup.

Step 1 of 2: Select component to Backup page, select the , content database (for

. This will ensure that

Type of backup


7. In the Backup File Location \\backup\SharePoint.

Note

The SharePoint application pool account and the SQL server permissions on the file share specified as the backup location.

8. Click OK.

9. On the Backup and Restore Status page, click progress.

10. Once the backup is done,

11. Repeat steps 1 to 10 for all farms, Web applications, content databases or project databases that require migration.

6.1.2 Restore

Site hierarchies, site directories, nonany documents, files or list items stored within lists or libraries can be restored.

To perform a restore:

Important

If the Web application, that will have content restored to itsame name as the Web application that has been backed up, content may be overwritten.

1. In the production environment, click SharePoint Central Administration

2. Click Operations on the top navigation bar.

3. On the Operations page, un

4. On the Restore from Backup: Step 1 of 4: Select Backup FileLocation, enter the UNC path to the backup folder, for example,

5. Click OK.

6. On the Restore from Backup target backup package.


Backup File Location section, enter a backup location for example,

The SharePoint application pool account and the SQL server account must have appropriate permissions on the file share specified as the backup location.

On the Backup and Restore Status page, click Refresh to see the jobs currently in

Once the backup is done, Completed will show in the progress column.

10 for all farms, Web applications, content databases or project databases that require migration.

Site hierarchies, site directories, non-custom master pages, page layouts and content types; plus or list items stored within lists or libraries can be restored.

that will have content restored to it, has a site collection or a database with the application that has been backed up, content may be overwritten.

In the production environment, click Start > All Programs > AdministrativeAdministration.

on the top navigation bar.

On the Operations page, under Backup and Restore, click Restore from

Restore from Backup: Step 1 of 4: Select Backup File page, under , enter the UNC path to the backup folder, for example, \\backup

On the Restore from Backup – Step 2 of 4: Select Backup to Restore page, target backup package.


Page 112

section, enter a backup location for example,

account must have appropriate

to see the jobs currently in

column.

10 for all farms, Web applications, content databases or project

custom master pages, page layouts and content types; plus or list items stored within lists or libraries can be restored.

has a site collection or a database with the application that has been backed up, content may be overwritten.

Administrative Tools >

from backup.

page, under Backup File backup\SharePoint.

Step 2 of 4: Select Backup to Restore page, select the


7. Click Continue Restore Process

8. On the Restore from Backup required farm, Web application example, WSS_Content

9. Click Continue Restore Process

10. On the Restore from Backup Options section, select

11. If presented with the Login names and passwordspassword for the Web applications listed on the page.which was used when creating thsufficient SQL Server permissions to restore the database.

12. In the New names section, to create copies for the restored content, specify the Web application URL and name, the database server name, the file location on the server, and the new names for the new databases.

13. Click OK.

14. On the Backup and Restore Statusprogress.

15. When the recovery has finished, click

16. Type iisreset into the Run

17. If errors appear, more information can be founpreviously specified.


Continue Restore Process.

On the Restore from Backup – Step 3 of 4: Select Component to Restore page, farm, Web application (for example, moss.contoso.com), content database WSS_Content), or project database item to restore.

Continue Restore Process.

On the Restore from Backup – Step 4 of 4: Select Restore Options page, in the section, select New Configuration.

Login names and passwords section, enter the user name and password for the Web applications listed on the page. This is the user name and password which was used when creating the Web application. The user name account must ha

permissions to restore the database.

section, to create copies for the restored content, specify the Web application URL and name, the database server name, the file location on the server, and the new names for the new databases.

On the Backup and Restore Status page, click Refresh to see the jobs currently in

When the recovery has finished, click Start > Run.

Run dialog box and click OK.

ppear, more information can be found in the Sprestore.log file at the UNC path


Page 113

Step 3 of 4: Select Component to Restore page, select the , content database (for

Step 4 of 4: Select Restore Options page, in the Restore

section, enter the user name and This is the user name and password

lication. The user name account must have

section, to create copies for the restored content, specify the Web application URL and name, the database server name, the file location on the server, and

to see the jobs currently in

prestore.log file at the UNC path


6.2 Other Migration

DEPLOY

Backup and Restore


As described at the start of section production environment using:

� STSADM – A command line tool that can access the complete set of 2007 operations. More information on STSADM can be found in (Office SharePoint Server)

� The Content Deployment tool information on the Content Deployment tool can be found in

� The Content Migration Application Programming Interfacefor migrating content between Content Migration API can be found in

� Solutions and FeaturesVisual Studio to be packaged and migrated. can be found in Solutions and Web Part Packages

40 Stsadm command-line tool (Office SharePoint Server)

41 Plan content deployment {R41}: http://technet2.microsoft.com/Office/f/?en

42 Content Migration Overview {R42}:

43 Solutions and Web Part Packages {

44 Working with Features {R44}: http://msdn2.microsoft.com/en


igration Tools

As described at the start of section 6.1, it is also possible to migrate content from a staging to a roduction environment using:

A command line tool that can access the complete set of SharePoint Server More information on STSADM can be found in Stsadm command

(Office SharePoint Server)40.

The Content Deployment tool accessible via Central Administrationinformation on the Content Deployment tool can be found in Plan content deployment

The Content Migration Application Programming Interface – A simple and flexible API for migrating content between SharePoint Server 2007 sites. More information on the Content Migration API can be found in Content Migration Overview 42.

Solutions and Features – This enables code that has been developed in tools such as Visual Studio to be packaged and migrated. More information on Solutions and Features

Solutions and Web Part Packages43 and Working with Features

line tool (Office SharePoint Server) {R40}: http://technet.microsoft.com/en-us/library/cc261956.aspx

http://technet2.microsoft.com/Office/f/?en-us/library/edcdacca-8013-460e-95a0-d2b83b6cc7ef1033.mspx

: http://msdn2.microsoft.com/en-us/library/ms453426.aspx

{R43}: http://msdn2.microsoft.com/en-us/library/ms413687.aspx



Page 114

t is also possible to migrate content from a staging to a

SharePoint Server Stsadm command-line tool

accessible via Central Administration – More Plan content deployment41.

A simple and flexible API More information on the

This enables code that has been developed in tools such as More information on Solutions and Features

Working with Features44.


d2b83b6cc7ef1033.mspx

us/library/ms413687.aspx







APPENDIX A This appendix includes a description of the core Site Templates, Master Page Templates and Web Parts available within SharePoi

PART I Site Templates

Category Template

Collaboration Blank Site

Blog Site

Document Workspace

Team Site

Wiki Site

Enterprise Document Center

My Site Host

Personalization

Records Center

Search Center

Search Center with Tabs

Site Directory

Meeting Basic Meeting Workspace

Blank Meeting Workspace

Decision Meeting Workspace

Multipage Meeting Workspace

Social Meeting Workspace


TEMPLATES

This appendix includes a description of the core Site Templates, Master Page Templates and Web Parts available within SharePoint Server 2007.

Site Templates

Purpose

A blank site for customisation.

A site for a person or team to post ideas, observations, and expertise that site visitors can comment on.

Document Workspace A site for colleagues to work together on a document. It provides a document library for storing the primary document and supporting files, a tasks list for assigning toand a links list to point to resources related to the document.

A site for a team to quickly organise, author, and share information. It provides a document library and lists for managing announcements, calendar items, tasks, and discussions.

A site for a community to brainstorm and share ideas. It provides be quickly edited to record information and then linked together through keywords.

A site to centrally manage documents in a healthcare organisation.

A site used for hosting personal sites. The home page will always redirect to the user's My Site.

A site for delivering personalised views, data, and navigation from a site collection into My Site. It includes personalisation specific Web Parts and navigation that is optimised for My Site sites.

A site designed for records management. Records managers can configure the routing table to direct incoming files to specific locations. The site prevents records from being modified after they are added to it.

A site for delivering the SharePoint Server 2007 search experience. The site includes pages for search results and advanced searches.

Search Center with Tabs A site for delivering the search experience. The welcome page includes a search box with two tabs: one for general searches, and another for searches for information about people. It is possible to add and customise tabs to focus on other search scopes or result types.

A site for listing and categorising other sites in a healthcare

Basic Meeting Workspace A site to plan, organise, and capture the results of a meeting. It provides lists for managing the agenda, meeting attendees, and documents.

Blank Meeting Workspace A blank meeting site for customisation.

A site for meetings that track status or make decisions. It provides lists for creating tasks, storing documents, and recording decisions.

A site to plan a meeting, and to capture the meeting's decisions and other results. It provides lists for managing the meeting agenda and attendees, along with two blank pages for customisation.

A site to plan social occasions.


Page 115

This appendix includes a description of the core Site Templates, Master Page Templates and Web

A site for a person or team to post ideas, observations, and expertise that site visitors

site for colleagues to work together on a document. It provides a document library for storing the primary document and supporting files, a tasks list for assigning to-do items, and a links list to point to resources related to the document.

site for a team to quickly organise, author, and share information. It provides a document library and lists for managing announcements, calendar items, tasks, and

A site for a community to brainstorm and share ideas. It provides Web pages that can be quickly edited to record information and then linked together through keywords.

organisation.

home page will always redirect to the user's

A site for delivering personalised views, data, and navigation from a site collection into My Site. It includes personalisation specific Web Parts and navigation that is optimised

A site designed for records management. Records managers can configure the routing table to direct incoming files to specific locations. The site prevents records from being

A site for delivering the SharePoint Server 2007 search experience. The site includes

A site for delivering the search experience. The welcome page includes a search box two tabs: one for general searches, and another for searches for information about

people. It is possible to add and customise tabs to focus on other search scopes or

hcare organisation.

A site to plan, organise, and capture the results of a meeting. It provides lists for managing the agenda, meeting attendees, and documents.

A site for meetings that track status or make decisions. It provides lists for creating

A site to plan a meeting, and to capture the meeting's decisions and other results. It provides lists for managing the meeting agenda and attendees, along with two blank


Category Template

Publishing Collaboration Portal

News Site

Publishing Portal

Table 8: Default Site Templates

PART II Master Page Templates

Master Page Name Description

default.master � Provides a top navigation band and a vertical navigation section� Navigation uses a light blue colour scheme

BlueBand.master � Provides a top navigation band and a vertical navigation section

� Navigation uses a blue colour scheme

BlackBand.master � Provides a top navigation band and a vertical navigation section� Navigation uses a black colour scheme

BlueGlassBand.master � Provides a top navigation band and a vertical navigation section� Navigation

BlueVertical.master � Provides only a vertical navigation section� Navigation uses a blue colour scheme

BlackVertical.master � Provides only a vertical navigation section� Navigation uses a black colour scheme

BlueTabs.master � Provides top navigation by using tabs and a vertical navigation section� Navigation uses a blue colour scheme

OrangeSingleLevel.master � Provides a top navigation bar that shows a single level of navigation and a vertical navigation section that does not inc

� Navigation uses an orange colour scheme

BlackSingleLevel.master � Provides a top navigation bar that shows a single level of navigation and a vertical navigation section that does not include flyouts

� Navigation uses a black colour scheme

Table 9: Default Master Page Templates


Purpose

A starter site hierarchy for an intranet divisional portal. It includes a home page, a News site, a Site Directory, a Document Center, and a Search Center with Tabs. Typically, this site has an equal number of contributors and readers. Collaboration portals often include subsites based on templates in the Collaboration category.

A blank site for expanding the Web site and quickly publishing Web pages. Contributors can work on draft versions of pages and publish visible to readers. The site includes document and image libraries for storing Web publishing assets.

A starter site hierarchy for an Internet-facing site or a large intranet portal. This site can be customised easily to supply distinctive branding. It includes a home page, a sample press releases subsite, a Search Center, and a login page. Typically, this site has many more readers than contributors. This site enables content approval workflows by default for a more focontrolled publishing process. It also restricts the rights of anonymous users to only be able to see content pages, but not to be able to view SharePoint Server 2007 application pages.

Master Page Templates

Description

Provides a top navigation band and a vertical navigation section Navigation uses a light blue colour scheme

Provides a top navigation band and a vertical navigation section

Navigation uses a blue colour scheme

Provides a top navigation band and a vertical navigation section Navigation uses a black colour scheme

Provides a top navigation band and a vertical navigation section Navigation uses a blue glass colour scheme

Provides only a vertical navigation section Navigation uses a blue colour scheme

Provides only a vertical navigation section Navigation uses a black colour scheme

Provides top navigation by using tabs and a vertical navigation section Navigation uses a blue colour scheme

Provides a top navigation bar that shows a single level of navigation and a vertical navigation section that does not include flyouts Navigation uses an orange colour scheme

Provides a top navigation bar that shows a single level of navigation and a vertical navigation section that does not include flyouts Navigation uses a black colour scheme


Page 116

A starter site hierarchy for an intranet divisional portal. It includes a home page, a News site, a Site Directory, a Document Center, and a Search Center with Tabs.

and readers. Collaboration portals often include subsites based on templates in the Collaboration category.

A blank site for expanding the Web site and quickly publishing Web pages. Contributors can work on draft versions of pages and publish them to make them visible to readers. The site includes document and image libraries for storing Web

facing site or a large intranet portal. This site can to supply distinctive branding. It includes a home page, a sample

press releases subsite, a Search Center, and a login page. Typically, this site has

This site enables content approval workflows by default for a more formal and controlled publishing process. It also restricts the rights of anonymous users to only be able to see content pages, but not to be able to view SharePoint Server 2007

Provides a top navigation bar that shows a single level of navigation and a vertical navigation section

Provides a top navigation bar that shows a single level of navigation and a vertical navigation section


PART III Web Parts

Web Part Name Description

General SharePoint Web Parts

Content Editor Web Part This can be used to add formatted text, tables, hyperlinks, and images to a Web Part Page.

Form Web Part This can be used to connect to and filter a column of data in another Web Part. Both Web Parts must run on the same server.

Image Web Part This can be used to add a picture or graphic to a Web Part Page.

<List View> Web Part This can be used to Parts, including other List View Web Parts.

Note

The Web Part does not appear with the name ‘List View’. When a list is created, a Web Part is automatically created ancause the automatic creation of a Web Part called Patient Data Web Part in the Site Name gallery. The Web Part automatically displays the data contained in the Patient Data list.

Page Viewer Web Part This can be used to display a Web page, file, or folder on a Web Part Page.

Site Users Web Part This can be used to display a list of users and groups who have permission to use a site. The Site Users Web Part automatically appearto any Web Part page.

XML Web Part This can be used to display Extensible Markup Language (XML) and apply Extensible Stylesheet Language Transformations (XSLT) to the XML before the con

Team Site Template Web Parts

Announcements This can be used to share news, status, and other short bits of information with team members.

Calendar This can be used to display upcoming events or team schedules.

Links This can be

Shared Documents This can be used to share files from the default document library with site users.

Tasks This can be used to assign a task to a user, specify its due date and priority, and indicate its status and progress.

Team Discussion This can be used to provide a forum topic discussions.

Table 10: SharePoint Web Parts


Description

This can be used to add formatted text, tables, hyperlinks, and images to a Web Part Page.

This can be used to connect to and filter a column of data in another Web Part. Both Web Parts must run on the same server.

This can be used to add a picture or graphic to a Web Part Page.

This can be used to display, and edit, list or library data on a site. It can also be connected to other Web Parts, including other List View Web Parts.

The Web Part does not appear with the name ‘List View’. When a list is created, a Web Part is automatically created and named after the list. For example, creating a list called Patient Data will cause the automatic creation of a Web Part called Patient Data Web Part in the Site Name gallery. The Web Part automatically displays the data contained in the Patient Data list.

This can be used to display a Web page, file, or folder on a Web Part Page.

This can be used to display a list of users and groups who have permission to use a site. The Site Users Web Part automatically appears on the home page of a Document Workspace site. It can also be added to any Web Part page.

This can be used to display Extensible Markup Language (XML) and apply Extensible Stylesheet Language Transformations (XSLT) to the XML before the content is displayed.

This can be used to share news, status, and other short bits of information with team members.

This can be used to display upcoming events or team schedules.

This can be used to post hyperlinks to Web pages.

This can be used to share files from the default document library with site users.

This can be used to assign a task to a user, specify its due date and priority, and indicate its status and

This can be used to provide a forum topic discussions.


Page 117

This can be used to add formatted text, tables, hyperlinks, and images to a Web Part Page.

This can be used to connect to and filter a column of data in another Web Part. Both Web Parts must

display, and edit, list or library data on a site. It can also be connected to other Web

The Web Part does not appear with the name ‘List View’. When a list is created, a Web Part is d named after the list. For example, creating a list called Patient Data will

cause the automatic creation of a Web Part called Patient Data Web Part in the Site Name gallery. The Web Part automatically displays the data contained in the Patient Data list.

This can be used to display a list of users and groups who have permission to use a site. The Site Users s on the home page of a Document Workspace site. It can also be added

This can be used to display Extensible Markup Language (XML) and apply Extensible Stylesheet tent is displayed.

This can be used to share news, status, and other short bits of information with team members.

This can be used to share files from the default document library with site users.

This can be used to assign a task to a user, specify its due date and priority, and indicate its status and


APPENDIX B This section includes links to related SharePoint Server 2007 topics.

PART I Business Data CatalogThis can be used to integrate with a including Line of Business (LOB) applications, databases and Web services.

Skill or Technology Area

Resource Location

Introduction to Business Data Catalog features

http://office.microsoft.com/enus/sharepointserver/HA102200501033.aspx?pid=CH100948691033

Business Data Catalog http://msdn2.microsoft.com/enus/library/ms563661.aspx

Add connections to the Business Data Catalog

http://technet2.microsoft.com/Office/f/?enus/library/e6a2593e7cdff749df1c1033.mspx

Table 11: Resources for Business Data Catalog

PART II Users, Groups and Security


Resource Location

Plan site and content security

http://technet2.microsoft.com/Office/f/?enus/library/85a1866e9ea61905c6d41033.mspx

Plan for people and user profiles

http://technet2.microsoft.com/Office/enus/library/267523c2d75f1e2f66031033.mspx?mfr=true

Managing security and permissions

http://office.microsoft.com/engb/sharepointserver/CH101248581033.aspx?pid=CH100305511033

Table 12: Resources for Site and Content Security

PART III Alerts for Lists and Libraries


Resource Location

Plan outgoing e-mail http://technet2.microsoft.com/Office/f/?enus/library/754016518a636f0b072d1033.mspx

Create an alert or subscribe to an RSS feed

http://office.microsoft.com/engb/sharepointserver/HA102487581033.aspx

Table 13: Resources for Configuring Alerts for Lists and Libraries


OTHER RESOURCES

This section includes links to related SharePoint Server 2007 topics.

Business Data Catalog This can be used to integrate with a healthcare organisations existing information architecture, including Line of Business (LOB) applications, databases and Web services.

Resource Location Description


Provides an overview of the Business Data


Provides an overview of the Business Data Catalog and links to Business Data Catalog features, concepts, metadata models, samples and more.

http://technet2.microsoft.com/Office/f/?en-us/library/e6a2593e-4526-4780-8377-7cdff749df1c1033.mspx

Provides guidance on how to add a connection to the Business Data Catalog.

: Resources for Business Data Catalog

Groups and Security


http://technet2.microsoft.com/Office/f/?en-us/library/85a1866e-2743-4f98-a1ac-9ea61905c6d41033.mspx

Provides an overview of site and content security as well as links to useful resources.

http://technet2.microsoft.com/Office/en-us/library/267523c2-703f-455e-bbb5-d75f1e2f66031033.mspx?mfr=true

Provides an overview of people aas links to other useful resources that can assist in planning people and user profiles.

http://office.microsoft.com/en-gb/sharepointserver/CH101248581033.aspx?pid=CH100305511033

Provides a useful set of help topics to enable a site administrator to perform typical security tasks, from changing the portal site owner to managing SharePoint groups.

: Resources for Site and Content Security

Alerts for Lists and Libraries


http://technet2.microsoft.com/Office/f/?en-us/library/75401651-ef01-4348-878e-8a636f0b072d1033.mspx

Provides an overview of outgoing email and discusses how administrators can configure alerts to automatically notify users. Links to useful resources are also provided.

http://office.microsoft.com/en-gb/sharepointserver/HA102487581033.aspx

Provides an overview of alerts and RSS feeds, as well as a walkthrough of how to configure alerts for a list or library.

Alerts for Lists and Libraries


Page 118

existing information architecture,

Provides an overview of the Business Data Catalog.

Provides an overview of the Business Data Catalog and links to Business Data Catalog features, concepts, metadata models, samples and more.

Provides guidance on how to add a connection to the Business Data Catalog.

Provides an overview of site and content security as well as links to useful resources.

Provides an overview of people and profiles, as well as links to other useful resources that can assist in planning people and user profiles.

Provides a useful set of help topics to enable a site administrator to perform typical security tasks, from changing the portal site owner to managing

Provides an overview of outgoing email and iscusses how administrators can configure alerts to automatically notify users. Links to useful resources

Provides an overview of alerts and RSS feeds, as well as a walkthrough of how to configure alerts for
























APPENDIX C

PART I Terms and Abbreviations

Abbreviation Definition

ASPX Active Server Page

CSS Cascading Style Sheet

HTML Hypertext Markup Language

IRM Information Rights Management

LOB Line of Business

MOF Microsoft

MSF Microsoft Solutions Framework

PDF Portable Document Format

SSP Shared Service Provider

UI User Interface

UNC Uniform Naming Convention

URL Uniform Resource Locator

VSe Visual Studio Extensions

WSS Windows SharePoint

XML Extensible Markup Language

XSLT Extensible Stylesheet Language Transformations

Table 14: Terms and Abbreviations

PART II Definitions

Term Definition

Audience A group of users within an organisation, such as nurses, doctors

Author Someone who regularly contribute

Content Page A content type for a

(Also known as Page Content Type and Page Layout

Content Type A reusable collection of settings to apply tomanagement of metadata and behaviours of a document or item type in a centralised, reusable way.

Current best practice Current best change or be revised due to changes to products, changes in technology, or simply the additional field deployment experience that comes over time.

Current navigation (aka Quick Launch)

A navigation element which provides links to important content in the site default

Global navigation A navigation element which typically appears towards the top of a links to the primary sites in a portal.

Layout Page An Active Server Pages (controls into which the contents of page are displayed


DOCUMENT INFORMATION

Terms and Abbreviations

Definition

Active Server Page

Cascading Style Sheet

Hypertext Markup Language

Information Rights Management

Line of Business

Microsoft Operations Framework

Microsoft Solutions Framework

Portable Document Format

Shared Service Provider

User Interface

Uniform Naming Convention

Uniform Resource Locator

Visual Studio Extensions

Windows SharePoint Services

Extensible Markup Language

Extensible Stylesheet Language Transformations

Definitions

Definition

A group of users within an organisation, such as nurses, doctors or researchers

Someone who regularly contributes to the creation of Web page content.

A content type for a Web page. It defines the columns that an instance of a content page uses.

(Also known as Page Content Type and Page Layout Content Type)

A reusable collection of settings to apply to a certain category of content. management of metadata and behaviours of a document or item type in a centralised, reusable

Current best practice is used rather than best practice, as over time best practice guidance may change or be revised due to changes to products, changes in technology, or simply the additional field deployment experience that comes over time.

A navigation element which provides links to important content in the site default, it also provides links to related sites.

A navigation element which typically appears towards the top of a Web page to provide users with links to the primary sites in a portal.

An Active Server Pages (.aspx) page that defines a layout for a content page by providing field controls into which the contents of page are displayed.


Page 119

or researchers.

page content.

page. It defines the columns that an instance of a content page uses.

certain category of content. This enables the management of metadata and behaviours of a document or item type in a centralised, reusable

practice is used rather than best practice, as over time best practice guidance may change or be revised due to changes to products, changes in technology, or simply the additional

A navigation element which provides links to important content in the site that the user is visiting. By

page to provide users with

) page that defines a layout for a content page by providing field


Term Definition

List Item An item, su

Master Page A Webconsistent look and feel between pages.

Page Content Type See Content Page

Quick Launch See Current navigation

Site A central location where lists, libraries, pages, communications and tracking information can be added.

Site Administrator Someone who is responsible for the maintenance and administration of sites and site collectionsThis includes site security

Site Collection A hierarchical set of sites that can be managed together and consists of a topmore subsites.

Site Designer Someone who is responsible for the design of sites and interface and navigation.

Site Directory A site which enables sites to be classified

Site Owner The individual or team responsible for administering the site

SharePoint Portal One or more site collections that reside within a

SharePoint Web Application An application which is accessed over an to store datadatabase.

Tagging The process of applying relevant term(s) or keyword(s) to a piece of information, such as a document, to help better describe it. This assists in the

Top Link Bar See Global navigation.

User Someone who uses a site

Web Part An ASP.NET server control which is added to a Web Part Zone on a

Table 15: Definitions

PART III References

Reference Document

R1. Information Architecture Worksheets http://www.microsoft.com/industry/healthcare/technology/hpo/knowledgeworker/moss2007informationarchitecture.aspx

R2. Information Architecture Worksheets http://www.microsoft.com/industry/healthcare/technology/hpo/knowledgeworker/ecture.aspx

R3. Microsoft Office SharePoint Server 2007 Deployment Guidehttp://www.microsoft.com/industry/healthcare/technology/hpo/serverbuild/moss2007deployment.aspx

R4. Microsoft Office Online: Microsoft Office SharePoint Server 2007 product guide:http://office.microsoft.com/en

R5. Microsoft TechNet: Microsoft Office System: http://go.microsoft.com/fwlink/?LinkID=79589

R6. MSF Process Model White Paperhttp://www.microsoft.com/downloads/details.aspx?FamilyID=e481cb0bfc886956790e&DisplayLang=en


Definition

An item, such as a document or spreadsheet, which resides in a list.

Web page template that defines the look and feel for the outside areas of a page. This enables a consistent look and feel between pages.

Content Page

See Current navigation

A central location where lists, libraries, pages, communications and tracking information can be added.

Someone who is responsible for the maintenance and administration of sites and site collectionsThis includes site security, and the data and users associated.

A hierarchical set of sites that can be managed together and consists of a topmore subsites.

Someone who is responsible for the design of sites and Web pages. This includes the user interface and navigation.

A site which enables sites to be classified.


One or more site collections that reside within a Web application and can be centrally managed.

An application which is accessed over an Internet or intranet based network. It includes a database to store data, and the authentication method used to connect a SharePoint application to the database.

The process of applying relevant term(s) or keyword(s) to a piece of information, such as a document, to help better describe it. This assists in the classification and search of information.

See Global navigation.

Someone who uses a site.

An ASP.NET server control which is added to a Web Part Zone on a Web Part

References

Information Architecture Worksheets – Sample Data http://www.microsoft.com/industry/healthcare/technology/hpo/knowledgeworker/moss2007informationarchit

Information Architecture Worksheets – Empty Workbook http://www.microsoft.com/industry/healthcare/technology/hpo/knowledgeworker/moss2007informationarchit

Microsoft Office SharePoint Server 2007 Deployment Guide http://www.microsoft.com/industry/healthcare/technology/hpo/serverbuild/moss2007deployment.aspx

Microsoft Office Online: Microsoft Office SharePoint Server 2007 product guide: http://office.microsoft.com/en-us/sharepointserver/HA101680161033.aspx

Microsoft Office System: Deployment for Office SharePoint Server 2007:http://go.microsoft.com/fwlink/?LinkID=79589

MSF Process Model White Paper http://www.microsoft.com/downloads/details.aspx?FamilyID=e481cb0b-ac05-42a6-bab8-fc886956790e&DisplayLang=en


Page 120

page template that defines the look and feel for the outside areas of a page. This enables a

A central location where lists, libraries, pages, communications and tracking information can be

Someone who is responsible for the maintenance and administration of sites and site collections.

A hierarchical set of sites that can be managed together and consists of a top-level site and one or

pages. This includes the user

application and can be centrally managed.

or intranet based network. It includes a database and the authentication method used to connect a SharePoint application to the

The process of applying relevant term(s) or keyword(s) to a piece of information, such as a classification and search of information.

Web Part page.

Version

http://www.microsoft.com/industry/healthcare/technology/hpo/knowledgeworker/moss2007informationarchit1.0.0.0

moss2007informationarchit1.0.0.0

http://www.microsoft.com/industry/healthcare/technology/hpo/serverbuild/moss2007deployment.aspx 1.0.0.0

Deployment for Office SharePoint Server 2007:

http://en.wikipedia.org/w/index.php?title=Web_Part_Pages&action=edit





http://www.microsoft.com/industry/healthcare/technology/hpo/serverbuild/moss2007deployment.aspx


http://technet2.microsoft.com/Office/en-us/library/8a911115-de8a-4cf3-9701-f5ba78fa8bfc1033.mspx?mfr=true




Reference Document

R7. MOF Executive Overviewhttp://www.microsoft.com/technet/itsolutions/cits/mo/mof/mofeo.mspx

R8. Microsoft Office Online: Enable publishing features:http://office.microsoft.com/en

R9. Microsoft Office Online: Save a site as a site template:http://office.microsoft.com/en

R10. Microsoft Office Online: Use and configure a Summary Link Web Part or a Summary Link field controlhttp://office.microsoft.com/en

R11. MSDN: How to Create a SharePoint Server 2007 Custom Master Page and Page Layouts foContent Management Site:http://msdn2.microsoft.com/enus/library/bb727372.aspx#MOSS2007CustomMasterPageWCM_MasterPages

R12. Microsoft Office Online: Introduction to workflows:http://office.microsoft.com/en

R13. Microsoft TechNet: Microsoft Windows Server TechCenter: Active Directory How To...:http://technet2.microsoft.com/windowsserver/en/library/89a250d274578558991033.mspx?mfr=true

R14. Microsoft TechNet: SharePoint Server TechCenterhttp://technet.microsoft.com/en

R15. Microsoft TechNet: Microsoft Office System: http://technet.microsoft.com/en

R16. Microsoft TechNet: Microsoft Office System: http://technet.microsoft.com/en

R17. Microsoft Office Online: Create or change a view:http://office.microsoft.com/en

R18. Microsoft TechNet: Microsoft Office System: Plan Information Rights Management:http://technet2.microsoft.com/Office/f/?en

R19. Microsoft TechNet: Microsoft Office Systehttp://technet.microsoft.com/en

R20. Dublin Core Metadata Initiative:http://dublincore.org/documents/dces/

R21. Microsoft Office Online: Add a column to a libraryhttp://office.microsoft.com/en

R22. MSDN: Introduction to Content Types:http://msdn2.microsoft.com/en

R23. Microsoft Office Online: Introduction to http://office.microsoft.com/en

R24. Microsoft TechNet: WindowsSharePoint Services): http://technet.microsoft.com/en

R25. Microsoft Office Online: Add a http://office.microsoft.com/en

R26. MSDN: How to: Create or Delete a http://msdn2.microsoft.com/en

R27. MSDN: Windows SharePoint Services Developer Center:http://msdn2.microsoft.com/en


MOF Executive Overview http://www.microsoft.com/technet/itsolutions/cits/mo/mof/mofeo.mspx

Enable publishing features: http://office.microsoft.com/en-us/sharepointserver/HA101577721033.aspx?pid=CH101782971033

Microsoft Office Online: Save a site as a site template: http://office.microsoft.com/en-us/help/HA101577791033.aspx

Microsoft Office Online: Use and configure a Summary Link Web Part or a Summary Link field controlhttp://office.microsoft.com/en-gb/sharepointserver/HA101551681033.aspx?pid=CH101782981033

MSDN: How to Create a SharePoint Server 2007 Custom Master Page and Page Layouts foContent Management Site: http://msdn2.microsoft.com/en-us/library/bb727372.aspx#MOSS2007CustomMasterPageWCM_MasterPages

Office Online: Introduction to workflows: http://office.microsoft.com/en-gb/sharepointdesigner/HA101005871033.aspx?pid=CH100667661033

hNet: Microsoft Windows Server TechCenter: Active Directory How To...: http://technet2.microsoft.com/windowsserver/en/library/89a2508a-8446-4d61-9cd9-d274578558991033.mspx?mfr=true

SharePoint Server TechCenter: Configure targeted content: http://technet.microsoft.com/en-us/library/cc262334.aspx

Microsoft Office System: Configure personalization sites: http://technet.microsoft.com/en-us/library/cc262716.aspx

Microsoft Office System: Plan Shared Services Providers: http://technet.microsoft.com/en-us/library/cc263276.aspx

Microsoft Office Online: Create or change a view: http://office.microsoft.com/en-gb/sharepointserver/HA100215771033.aspx?pid=CH101471921033

Microsoft TechNet: Microsoft Office System: Plan Information Rights Management: http://technet2.microsoft.com/Office/f/?en-us/library/073bfc71-7b01-4b77-bdc3-ac018889d54b1033.mspx

Microsoft Office System: Document management roadmap: http://technet.microsoft.com/en-us/library/cc263142.aspx

Dublin Core Metadata Initiative: http://dublincore.org/documents/dces/

Microsoft Office Online: Add a column to a library: http://office.microsoft.com/en-gb/sharepointserver/HA101754741033.aspx?pid=CH102360031033#2

MSDN: Introduction to Content Types: http://msdn2.microsoft.com/en-us/library/ms472236.aspx

Microsoft Office Online: Introduction to information management policies: http://office.microsoft.com/en-gb/sharepointserver/HA101735291033.aspx?pid=CH100948701033

Microsoft TechNet: Windows SharePoint Services 3.0: Create or extend Web applications (Windows


Microsoft Office Online: Add a link to an existing site: http://office.microsoft.com/en-us/sharepointserver/HA100906311033.aspx?pid=CH100963401033

MSDN: How to: Create or Delete a Site or a Site Collection: http://msdn2.microsoft.com/en-gb/library/ms448720.aspx

MSDN: Windows SharePoint Services Developer Center: http://msdn2.microsoft.com/en-us/sharepoint/default.aspx


Page 121

Version


Microsoft Office Online: Use and configure a Summary Link Web Part or a Summary Link field control gb/sharepointserver/HA101551681033.aspx?pid=CH101782981033

MSDN: How to Create a SharePoint Server 2007 Custom Master Page and Page Layouts for a Web

gb/sharepointdesigner/HA101005871033.aspx?pid=CH100667661033


ac018889d54b1033.mspx

A101754741033.aspx?pid=CH102360031033#2


SharePoint Services 3.0: Create or extend Web applications (Windows




http://office.microsoft.com/en-us/help/HA101577791033.aspx




http://office.microsoft.com/en-gb/sharepointdesigner/HA101005871033.aspx?pid=CH100667661033







http://technet2.microsoft.com/Office/f/?en-us/library/073bfc71-7b01-4b77-bdc3-ac018889d54b1033.mspx


http://dublincore.org/documents/dces/

http://office.microsoft.com/en-gb/sharepointserver/HA101754741033.aspx?pid=CH102360031033#2





http://msdn2.microsoft.com/en-gb/library/ms448720.aspx

http://msdn2.microsoft.com/en-us/sharepoint/default.aspx


Reference Document

R28. Microsoft Office Online: Get started with basic site customizations:http://office.microsoft.com/en

R29. Microsoft Office Online: Modify the default SharePoint content placeholders:http://office.microsoft.com/en

R30. Microsoft Office Online: Reset a customized page to the site definition:http://office.microsoft.com/en

R31. Microsoft Office Online: Apply a custom style sheet to a SharePoint site:http://office.microsoft.com/en

R32. Microsoft Office Online: Customize a Meeting Workspace site: http://office.microsoft.com/en

R33. Microsoft Office Online: Introduction to incoming http://office.microsoft.com/en

R34. Microsoft Office Online: Add content controls to a template:http://office.microsoft.com/en

R35. Microsoft Help and Suport: You do not see a link to the home page of the portal site in a personal site that you created in SharePoint Server 2007:http://support.microsoft.com/kb/924464

R36. Codeplex: SharePoint 2007 Test Data Population Tool: http://www.codeplex.com/sptdatapop

R37. Microsoft TechNet: Microsoft Office System: Plan for software boundaries (Office SharePoint Server):http://technet.microsoft.com/en

R38. Microsoft TechNet: Microsoft Office System: Estimate performance and capacity requirements for Windows SharePoint Services collaboration environments (Office SharePoint Server):http://technet.microsoft.com/en

R39. Microsoft Office SharePoint Server 2007 Management Pack Guide:http://go.microsoft.com/fwlink/?LinkID=94824&

R40. Microsoft TechNet: Stsadm commandhttp://technet.microsoft.com/en

R41. Microsoft TechNet: Microsoft Office http://technet2.microsoft.com/Office/f/?en

R42. MSDN: Content Migration Overview:http://msdn2.microsoft.com/en

R43. MSDN: Solutions and Web Part Packages: http://msdn2.microsoft.com/en

R44. MSDN: Working with Features: http://msdn2.microsoft.com/en

Table 16: References


Microsoft Office Online: Get started with basic site customizations: http://office.microsoft.com/en-us/sharepointdesigner/HA101741431033.aspx?pid=CH100667691033

Microsoft Office Online: Modify the default SharePoint content placeholders: http://office.microsoft.com/en-us/sharepointdesigner/HA101651201033.aspx

Microsoft Office Online: Reset a customized page to the site definition: http://office.microsoft.com/en-us/sharepointdesigner/HA101741451033.aspx

Microsoft Office Online: Apply a custom style sheet to a SharePoint site: http://office.microsoft.com/en-us/sharepointdesigner/HA101691741033.aspx

Microsoft Office Online: Customize a Meeting Workspace site: http://office.microsoft.com/en-us/sharepointserver/HA100663671033.aspx?pid=CH101181631033#2

Microsoft Office Online: Introduction to incoming e-mail http://office.microsoft.com/en-us/sharepointserver/HA100823061033.aspx

Microsoft Office Online: Add content controls to a template: http://office.microsoft.com/en-us/word/HA100307541033.aspx#3

Microsoft Help and Suport: You do not see a link to the home page of the portal site in a personal site that reated in SharePoint Server 2007:


Codeplex: SharePoint 2007 Test Data Population Tool: http://www.codeplex.com/sptdatapop

Microsoft TechNet: Microsoft Office System: Plan for software boundaries (Office SharePoint Server):http://technet.microsoft.com/en-us/library/cc262787.aspx

Microsoft TechNet: Microsoft Office System: Estimate performance and capacity requirements for Windows SharePoint Services collaboration environments (Office SharePoint Server): http://technet.microsoft.com/en-us/library/cc261795.aspx

Microsoft Office SharePoint Server 2007 Management Pack Guide: http://go.microsoft.com/fwlink/?LinkID=94824&clcid=0x409

Microsoft TechNet: Stsadm command-line tool (Office SharePoint Server): http://technet.microsoft.com/en-us/library/cc261956.aspx

Microsoft TechNet: Microsoft Office System: Plan content deployment: http://technet2.microsoft.com/Office/f/?en-us/library/edcdacca-8013-460e-95a0-d2b83b6cc7ef1033.mspx

Content Migration Overview: http://msdn2.microsoft.com/en-us/library/ms453426.aspx

MSDN: Solutions and Web Part Packages: http://msdn2.microsoft.com/en-us/library/ms413687.aspx

MSDN: Working with Features: http://msdn2.microsoft.com/en-us/library/ms413687.aspx


Page 122

Version

us/sharepointdesigner/HA101741431033.aspx?pid=CH100667691033

us/sharepointserver/HA100663671033.aspx?pid=CH101181631033#2

Microsoft Help and Suport: You do not see a link to the home page of the portal site in a personal site that

Microsoft TechNet: Microsoft Office System: Plan for software boundaries (Office SharePoint Server):

Microsoft TechNet: Microsoft Office System: Estimate performance and capacity requirements for Windows

d2b83b6cc7ef1033.mspx





http://office.microsoft.com/en-us/sharepointserver/HA100663671033.aspx?pid=CH101181631033#2


http://office.microsoft.com/en-us/word/HA100307541033.aspx#3


http://www.codeplex.com/sptdatapop







