External Data in Microsoft Word 2010 using SharePoint

Introduction

In the previous article, we learnt Customize SharePoint List Forms using InfoPath 2010. In this article we will be seeing how to show external data in Microsoft Word 2010.
Content controls in Microsoft Word provide a User Interface that is used for user input and print. For more information on Content Controls in Microsoft Word 2010 please refer
http://msdn.microsoft.com/en-us/library/bb157891.aspx.These These Content Controls can be used in the Microsoft Word 2010 to expose the external data in the document. Here we will be seeing how to expose the external data in the word document.
I have a document library called Shared Documents in my SharePoint site.I have added an External Data column named Employee Name which includes some additional fieldsDesignation, Location, EmpId and Department. I am going to add these external data column in the word document so that the values will be automatically populated based on the external data columns in the word document.

Steps Involved:

1. Open the SharePoint Site (http://servername10:10736/sites/ect).
2. Click on Shared Documents in the Quick Launch bar.
3. Shared Documents has the following columns

4. In the ribbon interface go to Library Tools, click on Documents tab.
5. Click on New Document button in the New group.

6. A new word document will be opened.
7. I have created a sample table which contains the information as shown in figure

8. Go to Insert tab, Click on Quick Parts.
9. Click on Document Property, you could be able to see all the columns as shown in figure.

10. Drag and drop the columns in the table as shown in figure

11. Save the document.
2. A new document will be added to the document library.
13. Select the document, click on Edit Properties in the ECB menu.

14. Add the value to the external data column “Employee Name”.

15. Click on Save.

16. Select the document, click on Edit in Microsoft Word in the ECB menu.
17. Values for the external data columns will be automatically updated in the word document as shown in figure.

Conclusion:

Thus in this article we have seen how to show external data in Microsoft Word 2010.

Programmatically create User Profile Sub-Types in SharePoint 2010

User Profile Sub-Types:

User properties can be associated to the particular user Profile Sub Type and these sub types allows creating different kinds of User Profiles. Each User Profiles will display different user properties based on the Sub Types. In this you will see how to create User Profile sub types in SharePoint 2010 using SharePoint Object Model.

Steps Involved:

1. Open Visual Studio 2010 by going Start | All Programs | Microsoft Visual Studio 2010 | Right click on Microsoft Visual Studio 2010 and click on Run as administrator.
2. Go to File tab, click on New and then click on Project.
3. In the New Project dialog box, expand the Visual C# node, and then select the Windows node.
4. In the Templates pane, select Console Application.
5. Enter the Name and then click OK.
6. In the solution explorer, right click on the solution and then click on Properties.
7. Select the Application tab, check whether “.Net Framework 3.5” is selected for Target Framework.
8. Select the Build tab, check whether “Any CPU” is selected for Platform Target.
9. In the solution explorer, right click on the References folder and click on Add Reference.
10. Add the following references.

1.  Microsoft.SharePoint.dll
2.  Microsoft.Office.Server.UserProfiles.dll
3.  System.Web.dll

11. Double click on Program.cs and add the following Namespaces.

1.  using System.Web;
2.  using Microsoft.Office.Server.UserProfiles;
3.  using Microsoft.SharePoint; 

12. Replace Program.cs with the following code snippet.

namespace UserProfileTesting
{
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Web;
using Microsoft.Office.Server.UserProfiles; 
using Microsoft.SharePoint; 

class Program
{
public static void Main(string[] args)
{
using (SPSite site = new SPSite("https://servername.com/hrp/hrp/"))
{
//// SPServiceContext class is used to represent a context object that encapsulates all the information that is required to make a call to a user profile service application.
SPServiceContext context = SPServiceContext.GetContext(site);
////ProfileSubtypeManager class is used to create, delete, retrieve, and manage profile subtypes for a profile type.
ProfileSubtypeManager psm = ProfileSubtypeManager.Get(context);
//// Get the user profile subtype 
ProfileSubtype subtype=psm.GetProfileSubtype("Finance");
//// Check whether the subtype exists
if (subtype == null)
{
//// create a new user profile subtype
//// Finance is the Name of the subtype
//// Finance Subtype is the Display name of the subtype
psm.CreateSubtype("Finance", "Finance Subtype", ProfileType.User);
}
else
{
Console.WriteLine(subtype.DisplayName + " already exists.");
Console.ReadLine();
}
}
}
}
}

13. In the solution explorer, right click on the solution and click on Build.
14. Hit F5.

InfoPath Web Part in SharePoint 2010

In this article we will be seeing how to create an InfoPath web part in SharePoint 2010.

Introduction

In the previous article, we learnt Customize SharePoint List Forms using InfoPath 2010 In this article we will be seeing how to create an InfoPath web part in SharePoint 2010.
I have a custom List named Employee Details which contains the following columns

I have customized the list forms using InfoPath 2010 and the form looks like the following

And I have modified the view for the Employee Details list as shown in the following

In this article we will be hosting the forms in a Web Part inside any Web Part page and will be creating an list view web part in the same page.  Then we will use the connections between the Web Parts to interact with other components on the page.

Create Web Part Page:

1. Open SharePoint site.
2. Go to Site Actions => More Options...

3. In the left task pane, select Page.
4. Click on Web Part Page and then click on Create.

5. Enter the Name for the page and click on Ok.
6. The page looks like the following

Create List view web part:

1. In the web part page click on Add a Web Part.
2. In the Categories section, click on Lists and Libraries and then click on Employee Details.

3. Click on Add.

Create InfoPath Form web part:

1. In the web part page click on Add a Web Part.
2. In the Categories section, click on Forms and then click on InfoPath Form Web Part.


3. The web part looks like the following

4. Click on Click here to open the tool pane to select the form.
5. In the tool pane, select Employee Details from drop down in List or Library.


6. Select Item from the drop down in Content Type.
7. Click on Ok.

Connecting the web parts:

1. In the InfoPath Form Web Part, click on the down arrow.
2. Click on Connections, then click on Get Form From and click on Employee Details.

3. On the Page tab click on Stop Editing.



4. On the Page tab click on Stop Editing.
5. Click the  icon next to the First name in the Employee Details list, the details for that employee will appear in the InfoPath Form Web Part.

Conclusion:

In this article we have seen how to create an InfoPath form web part.

How To Add Custom Asp.net Page Using Layouts folder approach in SharePoint2010

Adding Custom Asp.net pages into SharePoint using Layout Folder approach

Introduction

 Layout Folder approach is one of the methods of integrating files into Share Point Site .This document explains the steps for adding Custom asp.net Pages to _layout folder using Layout Folder approach.

Advantages

Following are the advantages when we add Custom Aspx Pages into Share Point Site
·         End users can perceive all those pages within SharePoint site. She/he must not go to a separate web application URL.
·         No additional Work needs to be done once the integration is done.
·         Share Point Security and access rules will take care of everything.
·         No additional Authorization and Authentication mechanism needs to be done.
·         Development Efforts are less compared to developing Web Parts.

Solutions

Following are few solutions in which we can integrate Custom Aspx Pages into Share Point Site
1. SharePoint designer approach: This approach is better when we work with few aspx pages and less functionality.
2. Web Parts approach: This can be used in combination with SharePoint designer. But once again, developing many web parts is not feasible solution and sometimes leads to performance issues.
3. _Layouts folder approach: This is best and simple method of all. This method deploys the web application pages under the _layouts folder of Share Point Site and the pages can be accessed from any Share Point Site.
 
Steps  
Following are the steps how to add Custom aspx or asp.net Pages in Share Point Site
   
Step 1: Open Visual Studio 2010 and create an Empty Share point Project named as “AspxToLayouts”
 
 

 
 
 
Step 2: Select “Deploy as Farm solution”.
 

Step 3: Right click on the Project and add navigate to “Add -> SharePoint “Layouts” Mapped Folder”.
 
 

 
 
 
Step 4: After adding, Layouts folder structure will be generated in your project. After that we will add our newly custom aspx page to the Layouts folder that got generated in our project. Sometimes we can add existing Aspx also if required.
 

Step 5: Hence to add a new aspx page, Right click on your custom folder “AspxToLayouts” and click on “Add -> New Item”. Following, In Add new item menu under “General” tab select “Text file” and rename it as “MyPage.aspx”. See the screen shot below

 
 
   
Step 6: Now your Project structure should look something like below screen shot.

 
 
 
Also, in the above screen verify the “Deployment Path” for newly created Page. To verify Traverse to “MyPage.aspx” -> Properties window.
 
Step7: Next, in solution explorer right clicks the Project and Build & Deploy.
 
 
Step 8: Once it is deployment is done successfully, traverse to your 14 hive folder and validate that new folder “AspxToLayouts” generated with our custom page “MyPage.aspx” in it.

References

 
1.    http://office.microsoft.com/en-us/sharepoint-server-help/getting-started-with-sharepoint-server-2010-   HA010371435.aspx
2.    http://www.learningsharepoint.com/

Configuring Managed Metadata Services (MMS) In SharePoint 2010

Metadata Management is very one of the critical aspects of any organization. By managing its metadata, consistency of the information used across the various units and teams in an organization could be enhanced, thus facilitating the information to be more locatable.

Introduction
 
Metadata is additional information about other data/artifact. Metadata is used to describe that artifact. This metadata resides outside of the artifact. E.g. Author, Organization, Language, technology to which that artifact is written by or belongs to, and type of the document like white paper, training material, check list, etc. These are additional information about the artifact but reside outside of the artifact and tell more about the artifact.
 
The following points will cover in this document:
 
1) In what way the metadata can be managed?
2)Real-world techniques for metadata implementation.

Problem with the existing systems
 

1. Metadata inconsistency:
    
    If the metadata is not standardized, then there is a possibility of inconsistent way of tagging data. For example, if an application to fill in the field called Location, one person might fill as INDIA, second as ASIA, third person as BHARATH. When somebody tries to get all documents belonging to the location INDIA, he may not get the right set of documents.
    
2. Metadata hierarchy maintenance:
    
   For example, End user want to tag one document to the test1 project in banking domain of xyz organization, so user can get the document in result set with hierarchy; it is not possible in existing systems.
      
3. Free text Metadata:
    
   1) Existing system allows free text without proper governance; it will make difficulty in search and comparing data or content.
   2) In SharePoint Server 2010 Search relevance is improved as user inputs also get crawled and indexed while adding metadata tags, in current system it’s not provided.  
        
    
4. Grouping Metadata:
    
   Metadata will be grouped to sub units.
   Grouping metadata will allow managing metadata differently for different sub units,
   Example:  One organization having Sales department and it is connected with both Company Global store and Purchase department So, while searching for a particular term, all files associated with that term(both Company Global store and Purchase department) are retrieved from the multiple site collections across the web applications.
    
    
5. Synonyms Terms:
    
   Synonyms are used to get terms in search results in different way of wording,
   For Example: SharePoint Services, Windows SharePoint Services 3.0, SharePoint Services 4.0, Windows SharePoint Services 4.0 all these are different search keywords are used to refer to the same term.
    
6. Lack of Search Administration Reports:
    
   In SharePoint server 2010 there is a provision for an administrator to actually view a graphical representation of the searched keywords against the time taken for its retrieval.
    
   In MOSS 2007 there is a limitation of site collection boundary, In brief site columns are specific to the site collection, so if any user want to share same columns (metadata and taxonomy) across the multiple site collection the he have to create same columns in each site collection. So it is very difficult when user need to update any column (metadata and taxonomy), for this user need to update the columns in all the site collections.
     To overcome such challenges; SharePoint 2010 has been bundled with a new important feature called Enterprise Metadata Management (EMM). EMM is a key building block in Enterprise Content Management and will offer enterprise, management of metadata terms and content types for the content management systems. This will permit the sharing of the metadata taxonomies and terms in organizations across its multiple SharePoint websites and site collections.
   In MOSS 2007 there is a limitation of site collection boundary, In brief site columns are specific to the site collection, so if any user want to share same columns (metadata and taxonomy) across the multiple site collection the he have to create same columns in each site collection. So it is very difficult when user need to update any column (metadata and taxonomy), for this user need to update the columns in all the site collections.
    
   To overcome such challenges; SharePoint 2010 has been bundled with a new important feature called Enterprise Metadata Management (EMM). EMM is a key building block in Enterprise Content Management and will offer enterprise, management of metadata terms and content types for the content management systems. This will permit the sharing of the metadata taxonomies and terms in organizations across its multiple SharePoint websites and site collections.
      
      
     Metadata in SharePoint 2010 is broadly classified into two types.

 

 
 
 

1. Governance Driven (Taxonomy):
    
   In this terms are pre-defined by an administrator and are centrally governed. We can say these terms are Managed Terms. A controlled term can only be created by those with appropriate permissions. Managed terms can be structured into a hierarchy and can be selected by the users out of the new ‘Managed Metadata’ column type. When a metadata column of this type is defined, the user will be permitted to decide the metadata from the collection of pre-defined managed terms.
    
    
2. User Driven (Folksonomy):
   In this users specific to SharePoint 2010 items is going to add words or phrases we can say these terms are Managed Keywords. By default the managed keyword column is present. User-generated keywords (tags) are kept in list keyword set, this is a non-hierarchical.
    
    Case Study
    
   Below is the example of an organizational instance, where a user needs to enter in a field called “Location” and the possible keywords are already available from centrally governed keyword thus enabling classification and search easier.
     i)             Create a Group (term) and Term Sets in the Taxonomy term store
   Creating a Group (term) and Term Sets in the Taxonomy term store under the Managed Metadata Service as below:
    
   Group name:  TCS
   Term Sets:  Locations and Unit 
    
   So, we here are initiating the creation of a hierarchy level.
    
   See the below image:
    

          
            


ii)Create child terms for each term

By creating child terms, metadata across the organizational applications is consistent.
i) Click on down arrow beside above created Term (Group).                    


             

ii) Create two child items like below, Location and Units       
  

                      
iii)Create Synonyms for each term
It will help to improve search relevance as their inputs also get crawled and indexed thus achieving greater scope for end users to retrieve the documents with ease.
i)Creating a term under child:


        

 ii)Creating term India under location




 
 
iii)Creating Synonyms for term India

 
 
   
     
 
iv) Defining metadata column as a metadata column in a list
Defining metadata column as a metadata column in a list(Go to any doc library and click on create column)




v)Assigning the right node from taxonomy
Assigining the right node from taxonomy to the metadata column.
i)Select the Managed Metadata option
ii)Assign the node
iii)Click on Ok

 


vi)End user view of metadata column


i) End user view of metadata column    
       

 


 
ii) Searching through Synonym, after entering ‘hi’ it is showing India in search result, as we given ‘Hindustan’ as the Synonym in List.
 

 
 
 
 
iii)On Click on picker to select it will opens the follwing window:



iv) After selecting the term:

 
 
 

References
i)http://technet.microsoft.com/en-us/library/ee424403.aspx  
ii) http://sharepointgeorge.com/2010/configuring-managed-metadata-service-application-sharepoint-2010-part1/

Sharepoint Terminology

Active Directory	The Active Directory stores information about a variety of objects in the network. Importantly, user accounts, computer accounts, groups, and all related credential information used by windows and SharePoint.
Activities	Activities are tracked updates related to a specific user. They are often related to the users social interaction within SharePoint (such as tagging, rating, etc).
Activity Feed	A message that provides updates about items of interest based on custom notification settings. This includes updates about changes to documents, the status of colleagues, social tags, and colleague profiles.
Alerts	To notify users of changes to existing information or new information add an alert to track new matches to search queries, changes to content in an area (list/library, folder, and document/item), or a new site added to the Site Directory.
Anonymous Authentication/Access	An authentication mode in which neither party verifies the identity of the other party.
Anonymous User	A user who presents no credentials when identifying himself or herself.
Areas	A means to organize the portal for navigational simplification.
Ascending Order	A sort order in which text strings are arranged in alphabetical order, numerical values are arranged from smallest to largest, and dates and times are arranged from oldest to newest.
Attachment	An external file that is included with an email message or associated with an item in a SharePoint list.
Audience	A named group of users that is used for targeting content.
Audiences	Groups of users, who meet certain criteria, created for targeted distribution of information. Users are said to be a member of an audience if they meet that audience’s membership criteria. The criteria are associated with properties found in the Active Directory.
Authentication	(1) The ability of one entity to determine the identity of another entity. (2) The act of proving an identity to a server while providing key material which binds the identity to subsequent communications. (How the system knows who the user is)
Authorization and Authentication	Authentication is the process of deciding WHO a user is. Authorization is the process of deciding WHAT they can do. IIS (the web server) handles Authentication alongside things like Active Directory and SharePoint handles authorization. Authentication methods include things like Anonymous, Basic, Forms, Integrated (NTML/Kerberos and Claims).
BCS	Business Connectivity Services – A new service that empowers users (who have sufficient access rights) to pull in external data use in SharePoint.
BDC	Business Data Catalog – For connecting with other lines of business (enterprise level feature)
Collaboration Content	Collaboration content is content stored in lists like calendars, task lists, and document libraries.
Content Type	A named and uniquely identifiable collection of settings and fields that store metadata for individual items in a SharePoint list. One or more content types can be associated with a list, which restricts the contents to items of those types. A collection of Site Columns grouped together to define an item that you would like to store.
Data Validation	The process of testing the accuracy of data; a set of rules that specify the type and range of data that users can enter.
Default View	The view of a list that is defined by the owner of the list to appear when users browse to the list without specifying a view.
Descending Order	A sort order in which text is arranged in reverse alphabetical order, numerical values are arranged from largest to smallest, and dates and times are arranged from newest to oldest.
Discussions	SPS supports two types of discussions: discussion boards and Web discussions. Discussion boards are similar to any newsgroup forum. Web discussions, on the other hand, are a new way to comment on documents and share those comments with others. When a new site is created, a discussion board is automatically created.
Distribution List	A collection of users, computers, contacts, or other groups that is used only for e-mail distribution, and addressed as a single recipient.
Document Center	A document library template that is preconfigured to store a large quantity of documents.
Document Library	A configurable list in which documents and folders can be stored. The document library has special settings above and beyond a folder such as versioning settings, workflow settings, and information policies.
Document Workspace	A document repository that enables users to collaborate on one or more documents.
Document Workspace	SharePoint Services site that contain a document library, tasks, links, and other information. Document workspaces can be created directly in SPS as a new site, or they may be created ad-hoc from within an Office product. End users can collaborate without having SPS open alongside Office.
External Content Type	A reusable collection of metadata that defines a set of data from one or more external data sources, the operations available on that data, and connectivity information related to that data.
External List	A list of items of an external content type.
Farm	The entire installation as a whole. So if something has “Farm” level scope it applies to everything. or Installation of one or more load-balanced Web servers, and back-end servers, with a configuration database. A collection of servers (web, database, index) that together make up a SharePoint Installation – aka Topology. You can do all this (web/datababase/index etc) on a single server in “Simple Installation” mode in which case you don’t need a NLB. For many small businesses this is plenty enough. Medium sized businesses usually start with at least 2 Web Front Ends (WFE’s) and a database server. Multinationals can have some very complex setups involving dozens of components.
Farm Feature	Feature that is scoped globally for the entire server farm. For this reason, farm Features are also known as "global Features." Unlike other Feature types, a global Feature is activated by default in the farm. A farm Feature contains several elements that are critical for implementing applications and logic.
Feature	A package that can be activated or deactivated at either the site or site collection level. Each feature varies considerably so you must refer to it’s description to understand the impact of activating or deactivating a specific feature. Or A package of Windows SharePoint Services elements that helps a user accomplish a particular goal or task. For example, one Feature might be named "My Favorite Items" and contain the following: A custom list that stores, per user, a list of the user’s favorite items. This list is created as a single hidden list per workspace when a Feature is enabled. A custom menu item, named "Add to Favorites", that is attached to all lists and adds an item to the Favorites list. A Web Part that shows the user the top 10 favorites, with usage and link tracking to bring true favorites to the top. Each of these individual elements, by themselves, may not be useful, but when you enable all of them on a site they become a complete Feature that solves a particular task.
Gallery	A library that is used to store a collection of site resources, such as Web Parts, list templates, or site templates.
Item	An individual entry within a SharePoint list. Each list item can have multiple columns associated with it depending on the list it is contained within and, depending on the content type of the item.
Key Performance Indicator (KPI)	A predefined measure that is used to track performance against a strategic goal, objective, plan, initiative, or business process. A visual cue is frequently used to communicate performance against the measure.
Keyword	One or more words or phrases that site administrators identified as important. A keyword provides a way to display best bets and definitions on a search results page.
Levels of the SharePoint Hierarchy
Libraries	In order to share files, SharePoint makes use of libraries. The three types of libraries available in SharePoint are document libraries, form libraries and picture libraries.
List Template	An XML-based definition of list settings, including fields and views, and optionally list items. List templates are stored in .stp files in the list template gallery.
Lists	Along with document libraries, lists form the foundation of content within SPS. A list is a collection of information items displayed in an area or on a site. List types include: Announcements, Links, Contacts, Events, Tasks and Issues.
Lookup Column	A column of the Lookup type that allows a user to select items from another list/library. This column can also bring in extra data/fields from the list it is referencing.
Major Version	An iteration of a document, or list item that is ready for a larger group to see, or has changed significantly since the previous major version. For an item on a SharePoint site, the minor version is always zero for a major version.
Managed Term	A word or a phrase that can be associated with a SharePoint item . Managed terms, are usually predefined, can be created only by users with the appropriate permissions, and are often organized into a hierarchy. Also called “term” where “managed” is clear from the context.
Masterpage	The masterpage is the structural content which often surrounds your site. Often it makes up the header and footer of the site and may or may not also contain the left navigation. Typically if you have multiple masterpages these will significantly alter the look of each site they are applied to.
Meeting Workspace	A specialized SharePoint Services site. Can be created directly in SPS or in Outlook as a part of a meeting request. Should not be confused with Live Meeting, etc.
Metadata	Data about data. This is often seen in the form of column values in a SharePoint library or list, but can take many other forms.
Minor Version	For an item on a SharePoint site, the minor version number is never zero and is incremented for each new version of an item, unless a major version is explicitly published. When minor versioning is disabled on a SharePoint site, only major version numbers are incremented, and the minor version is always zero.
Moss	Microsoft Office SharePoint Server 2007 – The fully licensed product in 2007 (note there is still enterprise and standard variations)
My Network	My network is a page designed to provide a summary and roll up of the activities going on in your network.
My Site	A single page portal that contains the user’s personal sites, links, etc. My Site consists of both a public and private view. The private view is intended as a personal workplace for the individual end user. The public view, on the other hand, acts like a business card that can be accessed by other portal users. You can see the different views by clicking either Private or Public under the Select View list.I am leaving this, because many will still refer to My Home, or Personal Sites as MySites for some time.
OOTB	Out of the box. Typically in SharePoint this represents the components and features shipped with the product. As in the existing webparts, and templates in the product. There is contention around whether using SharePoint Designer is OOTB as SharePoint Designer (while free) is still another product from SharePoint.
Page Layout	A dynamic Web template that is stored as a document. It contains content placeholders that bind to fields of a publishing page. A page layout has an associated content type that determines which publishing pages it can be bound to. The page layout can contain webpart zones, as well as webparts. In SharePoint think of the Masterpage as the wrapper for page layouts.
Permission	A rule that is associated with something to regulate which users can gain access to that something and in what manner.
Permission Level	A set of permissions that can be granted to users, distribution lists or SharePoint groups on an entity such as a site, list, folder, item, or document.
Personal Site	A type of SharePoint site that is used by an individual user for personal productivity. The site appears to the user as My Site.
Privacy Level	A setting that specifies the category of users who are allowed to view the personal information of other users, such as user profile properties, colleagues, or memberships.
Private Web Part	A Web Part added to a Web Part Page by a user who is working on the page in personal view. Private Web Parts are available only to the user who added or imported the Web Part.
Provision	The process of creating and deploying something, and in some cases, populating that something with default data and settings.
Published Version	The version of a list item that is approved and can be seen by all users. The user interface (UI) version number for a published version is incremented to the next positive major version number and the minor version is zero. and minor version.
Publishing Pages	Publishing pages are pages under /Pages/ document libraries on each site that include specific content types. Content for these pages are stored in this document library like columns in a list, with each column storing data for a page field.
Recycle Bin	A container for items that are deleted. Items in this container are visible to users with the appropriate permissions and to site collection administrators and can be recovered or removed (default of 45 days before they are automatically emptied).
Ribbon	The Ribbon is a new UI component added to simplify navigation, and increase the visibility of functions. It is Context Sensitive (which means when you click on something, it knows what you clicked on).
Search Scope	A list of attributes that define a collection of items to be filtered/returned in searches.
Server Farm	A central group of network servers maintained by an enterprise. A server farm provides a network with load balancing, scalability, and fault tolerance. In some configurations, multiple servers may appear to users as a single resource. Each SharePoint farm has a single, unique configuration database where information and configuration settings for the farm are registered. Each server in the farm relies on that configuration database to get information about the farm and to provide services in the farm.
Shared Documents Library	A document library that is included by default in the Team Site site template.
Shared Web Part	A Web Part added to a Web Part Page by a user who is working on the page in shared view. Shared Web Parts are available to all users of a Web Part Page who have the appropriate permissions.
SharePoint Foundation (Server)	This is the next version of WSS renamed. This version has no licensing costs (aside from infrastructure it runs on) and has less functionality than the full copy of SharePoint Server.
SharePoint Server	The new product/platform name. No longer called MOSS or Microsoft Office SharePoint Server.
Site	A complete Web site stored in a named leaf of the top-level Web site. (aka Web’s) – these are the actual sites that you use. A site can be a top-level site or a sub site of the top level site. A site can also have other sites – these are called sub-sites. Sub sites can also have other sub sites and so on. A site can inherit its parent’s permissions or define its own – more on this complex subject in a future article.
Site Collection	A set of Web sites on a Web application that has the same owner and share administration settings. Each site collection contains a top-level Web site and can contain one or more sites (or subsites). There can be multiple site collections on each Web application. A site collection can use only a single content database. Everything is now a site collection: a portal is a site collection where Home is the top-level Web site and the areas are sites (or subsites), a channel hierarchy is a site collection where the root channel is the top-level Web site and sub-channels are sites (or subsites). · Each web application has at least 1 Site Collection (but can have many). · Each Site collection has exactly 1 ‘Top Level Site’. · The Site Collection doesn’t actually contain anything itself - that is down to the Top Level Site. · This is the level that things like the Recycle bin and Quotas are organized at. · Each site collection can only use a single content database (though multiple site collections can us the same content database) – this has major design implications as there are maximum recommended sizes for a content database
Site Collection Administrator	A user who has administrative permissions for a site collection.
Site Column	A column that can be associated with a content type or list within a site or site collection.
Site Content Type	A named and uniquely identifiable collection of settings and fields that store metadata for lists within individual sites. This is at the site collection level, so that it is available throughout the subsites or sites beneath it.
Site Groups	Site groups are custom security groups that apply to a specific Web site. Users are assigned to site groups to grant them permissions on a SharePoint site.
Site Membership	The status of being a member of a site and having a defined set of user rights for accessing or managing content on that site.
Site Templates	Whenever you create a new site, SPS use predefined templates to simplify the creation of the new elements for the site. These templates allow you to create everything from a specialized team site to a blank site you can use to create content from scratch.
SPD / Sharepoint Designer	SharePoint Designer is a free tool which allows users to modify pages, and customize their SharePoint sites in more powerful ways than the out of the box GUI interface.
SPS	SharePoint Portal Server
Subsite	A named subdirectory of the top-level Web site that is a complete Web site. Each subsite can have independent administration, authoring, and browsing permissions from the top-level Web sites and other subsites.
Survey	A Web site component that enables users to respond to a set of questions specified by the creator of the survey. Results are tallied in a graphical summary. Surveys provide a way to poll portal users for input on a subject. Surveys support a wide variety of response types from simple Yes/No answers to free-form text.
Term Set	A collection of related terms. For example, the term set named “milestone” could include the terms “M0” “M1” “M2” “Alpha” “Beta1” “Beta2” “RC1” “RC2” and “RTM.”
Top-Level Web Site	The top, root default site in a site collection. Every site collection has, at its root a top-level Web site. Access to the top-level web site is provided supplying the URL of the site collection (like http://ServerURL or http://ServerURL/sites/SiteCollectionName) without specifying a page name or subsite. A Top Level Site is a site… at the top level… see – this terminology is not that confusing after all Most of the time we can use Top Level Site and Site Collection interchangeably - in fact Microsoft do this all the time. Each Top Level Site has zero to many sub-sites (simply called sites) This is the lowest level that many things can be scoped to, for example only the Top Level site contains a web part Gallery so you can’t say Collection X, Site A can have a web part but Collection X, Site B can’t. When you look at Site Settings in a top level site you will see the highlighted sections – in a sub site you will not. Both are called Sites in the UI.
View	A named collection of settings for querying and displaying items/documents in a SharePoint list/library. There are two types of views: Personal, which can be used only by the user who creates them; and Public, which can be used by all users who have access to the site.
Web Application	A virtual server that resides on an HTTP server but appears to the user as a separate HTTP server. Several Web applications can reside on one computer, each capable of running its own programs and each having individualized access to input and peripheral devices. Each Web application can have its own domain name and IP address. An IIS Website that has been configured to run SharePoint. Can only be created in the Central Admin UI (or via the STSADM tools etc) A Farm has one running the central administration site and 1 to many others running normal SharePoint sites. This is generally how the main part of the URL is defined – e.g. http://somesite.yourcompany.com and http://othersite.yourcompany.com will be separate Web Applications. This authentication method is set at the Web Application level – though you can have the same content (i.e. SharePoint site) delivered by two different web applications with two different authentication methods. Port and network card bindings, host headers and a host of other networky stuff is set at the Web Application level – so if you want external users, for example, to have access to a site that would apply at the Web Application level (you can apply more granular restrictions using authorization security though). The Application Pool (the account that SharePoint runs under and the resources that it can consume) are also set at the Web Application level.
Web Part	Customizable Web page element that can be added to SharePoint pages
Web Part Connection	An element in a Web Parts page that defines a provider-consumer data relationship between two Web Parts. When a Web Parts page is rendered, data provided by one Web Part can affect how and what is rendered by the other Web Part.
Web Part Page	Often certain pages will be called web part pages – Really this just means that these pages most likely have pre-defined zones you can use to add and re-arrange webparts on.
Web Part Properties	The properties which can be changed for a web part to appear or function differently.
Web Part Zone	A container with a set of properties that can be configured to control the organization and format of Web Parts on a Web Part Page. Web Part zones can also be used to provide protection against changes to Web Parts.
Workflow	The automation of business processes, where business documents and tasks are passed automatically from one user to another for action, according to a set sequence.
WSS	Windows SharePoint Services