| If you have recently moved from an Office Live site to Office 365, you've probably noticed that page URLs are different. For example, you'll see /pages/ included in the Office 365 URL which didn't appear in the Office Live URL for the same page. While this isn’t an issue when accessing pages from your site, it can be a problem for other sites and search engines that have linked to you. Fortunately, there's a procedure for maintaining your original URLs, here:
Maintain web page URLs from an Office Live website
Hope you find this helpful,
mp |
| The Boys and Girls Club of Canada (BGCC) needed Web solutions to make their Internet pages more engaging and useful and their internal sites more productive. After building solutions with SharePoint Server and Microsoft Dynamics CRM, the club experienced an increase in site traffic, volunteers, and donations, while cutting administrative costs.
 The BGCC provides programs that support the healthy physical, educational, and social development of more than 200,000 Canadian young people and their families each year. It is an association of more than 100 clubs located in 700 communities across Canada. Clubs are in neighborhoods where they are most needed—in large city centers, in remote rural communities, and on First Nations reserves.
Some highlights include:
- A more visually engaging and interactive site that includes blogs, and integration with external social media sites.
- The ability to track clubs, service locations, staff, volunteers, donations, campaigns, newsletters, and marketing campaigns through Dynamics CRM.
- A members only portal where people can find the content that's targeted for them, based on their permission level.
“Our effective use of graphics, multimedia, and social media tools encourages greater visitor interaction and engagement with our mission,” says Susan Bower, Vice President of BGCC Operations. “More time on our site translates to an increased public awareness of our activities.”
For more case studies, see the Microsoft Case Studies site, where you can filter for combinations of products, type of industries, and so on. Thanks,
Toni,
SharePoint Information Worker Content Team |
| by Ben Tedder International School of Beijing In part 1 of this “Blogging in SharePoint” series we showed you how to create and manage multiple picture libraries. Today we’ll integrate photo albums with our posts in a unique way.Once you’ve uploaded your photos to a picture library, click Actions (Note:
don't click Site Actions, a common mistake) and then click View Slide Show. This is an out-of-the-box feature of SharePoint. It’s not the best slideshow in the world, but it works for our purposes.
Next, copy the URL of the page (right click anywhere on the slideshow page and select properties) for later use.
Now that we have the URL to our slideshow page copied, go create a new blog post. In this post, create a two-row table. In the first row put a small image to represent the gallery, and in the second row write the title of the gallery, a small description, and then a link that says "click to view the gallery." We want to make the picture AND the text clickable links that take us to that slideshow.
Here’s how:
- Select the text (or picture) that you want to link up.
- Click the Insert tab and then click Link > From Address
- Paste in the address we copied in the last step. Also, it might be beneficial if you select the Open in new tab checkbox so users don’t have to leave your page entirely to see the slideshow. Click OK, and you’ll see your text is now linked.
Tip: When you make an image into a link it will automatically add a default 1px border around it. You can counteract this either by selecting a different image style or by adding some custom styling to the image in your CSS (cascading style sheet) file. To learn how to customize the master page and CSS of your blog, click here, or for even more details on customizing CSS, click here.
So the final product: a nice looking "gallery" post. When you click on the main image, or the link below, you’ll be presented with a SharePoint slideshow in a new window.
As you can see, we're still using SharePoint’s default blog look & feel. But if you use your imagination, you can format the blog, as well as your post, to make it even more awesome.
|
| by John Lukosky
allyis | www.allyis.com Microsoft Gold Certified Partner
Feature Activation Dependencies Introduction
A feature activation dependency expresses a requirement in the relationship between two features.
You can express activation dependencies either for:
- Features of the same scope or
- Features at a higher scope. This is known as a cross-scoped activation dependency. An example would be a Web site-scoped feature being dependent on a site collection–scoped feature. A better description would be a parent-scoped activation dependency as the dependency is always to a higher level.
Purpose of activation dependencies
Activation dependencies are usually used for feature grouping concepts and feature resource guarantees.
Feature Grouping When one feature is activated, other features can also be activated automatically. For example, when the default "team collaboration" feature (in %ProgramFiles%\Common Files\Microsoft Shared\web server extensions\14\TEMPLATE\FEATURES\TeamCollab) is activated, it uses activation dependencies to activate various other features. When you activate the team collaboration feature, it activates the dependent features, and the specified list templates are made available. When you deactivate the feature, the dependent features are deactivated if no other features depend on them, thereby making the list templates unavailable.
Feature Resource Guarantees
A site collection-scoped feature may need to contain resources (for example, a content type) and a Web site-scoped feature to contain an implementation. Activation dependencies can ensure that both features are activated.
Activation Dependency Rules
Activation dependencies must abide by certain rules to avoid, for example, circular dependencies, dependency chains that limit performance, and so on.
Hidden Feature Rules
Only hidden features can be activated or deactivated automatically. Hidden features cannot have activation dependencies. This means that you must have a visible feature to activate and that you can only activate features from the visible feature. You cannot have a hierarchy of hidden features dependent on each other and have them all automatically activate in the correct order.
Same-Scope Rules
- Only same-scoped hidden features are automatically activated or deactivated.
- If a feature is dependent on another feature at the same scope, and the second feature is not activated when the first one is activated, Microsoft SharePoint Foundation activates the second feature.
- If a feature is deactivated, SharePoint Foundation deactivates a same-scope dependent hidden feature when the last visible feature that has an activation dependency on that hidden feature is deactivated.
Cross-Scope Rules
- Cross-scope activation dependencies are not supported if the feature depended upon is at a more restrictive scope. For example, a site collection–scoped feature cannot have an activation dependency on a Web site–scoped feature.
- Feature activation dependencies are not supported across scopes if the feature that is depended upon is not visible.
- If a feature that is depended upon is not activated, activation of the depending feature fails. For example, if a web site–scoped feature depends on a site collection–scoped feature that is not activated, activation of the web site-scoped feature (or of a site definition that contains a web site-scoped feature) fails.
General Rules
- Dependencies can work only one level deep. In other words, dependency chains are not supported. SharePoint Foundation does not support more than one level in activation dependencies if the last feature is visible—that is if a visible feature depends on a second visible feature that in turn depends on a third visible feature. However, SharePoint Foundation does support more than one level in activation dependencies if a visible feature depends on a second visible feature that in turn depends on a hidden feature.
- Activation dependencies can be against hidden or visible features, but hidden features cannot have activation dependencies. The Hidden attribute on the feature element determines whether the feature is displayed in the user interface.
Handling Dependencies Through Feature Stapling
Use Feature Stapling to Avoid Creating Site Definitions
Feature Stapling allows you to "staple" a feature to both out-of-the-box and custom site definitions without modifying them in any way. This means you can add your features to all sites created using that site definition. If you want to make modifications or customizations in out-of-the-box site definitions; develop them all as features and staple them with the respective site definition.
How to staple a Feature to a Site Definition:
To staple a feature to a site definition, create a stapler feature that will do the stapling. A feature stapled or associated with a site definition is called a staplee feature. Below is an example of a staple feature to staple a Multilanguage feature to the STS, and SPS site definitions: Stapler Feature.xml <?xml version="1.0" encoding="utf-8" ?><Feature Id="82E2EA42-39E2-4B27-8631-ED54C1CFC491" Title="$Resources:MultiLangStaplingFeatureName"Description="$Resources:MultiLangstaplingFeatureDescription"Version="12.0.0.0"Scope="Farm"xmlns="http://schemas.microsoft.com/sharepoint/"DefaultResourceFile="_Res"><ElementManifests><ElementManifest Location="Elements.xml"/>
</ElementManifests>
</Feature>
Elements.xml file (for stapler feature): <Elements xmlns="http://schemas.microsoft.com/sharepoint/">
<FeatureSiteTemplateAssociation Id="29D85C25-170C-4df9-A641-12DB0B9D4130" TemplateName="STS#0" /> <FeatureSiteTemplateAssociation Id="29D85C25-170C-4df9-A641-12DB0B9D4130" TemplateName="STS#1" /> <FeatureSiteTemplateAssociation Id="29D85C25-170C-4df9-A641-12DB0B9D4130" TemplateName="SPS#0" />
</Elements>
In the above Elements.xml file code, you can see the FeatureSiteTemplateAssociation element which basically defines the associations between features and site definitions. In the above example, the stapler feature "staples" the staple feature with the ID "29D85C25-170C-4df9-A641-12DB0B9D4130" to the STS#0, STS#1, and SPS#0 site definitions.
The scope of the stapler feature is always Farm.
If the stapler feature is deactivated, the existing sites will still have the Multilanguage feature activated but no new sites will have the Multilanguage feature activated.
If you want to staple a feature to all site definitions then you can staple it to the GLOBAL (GLOBAL#0) site definition and it will be added to all sites that are created.
To staple to other site definitions, use the table below to determine the name.
Site Templates
Use name column from following table to format the site stapling feature's Elements.xml file. Example: TemplateName="BLOG#0".
| Template ID |
Title |
Name |
| 0 |
Global template |
GLOBAL#0 |
| 1 |
Team Site |
STS#0 |
| 1 |
Blank Site |
STS#1 |
| 1 |
Document Workspace |
STS#2 |
| 2 |
Basic Meeting Workspace |
MPS#0 |
| 2 |
Blank Meeting Workspace |
MPS#1 |
| 2 |
Decision Meeting Workspace |
MPS#2 |
| 2 |
Social Meeting Workspace |
MPS#3 |
| 2 |
Multipage Meeting Workspace |
MPS#4 |
| 3 |
Central Admin Site |
CENTRALADMIN#0 |
| 4 |
Wiki Site |
WIKI#0 |
| 9 |
Blog |
BLOG#0 |
| 7 |
Document Center |
BDR#0 |
| 14483 |
Records Center |
OFFILE#0 |
| 22 |
Personalization Site |
SPSMSITE#0 |
| 39 |
Publishing Site |
CMSPUBLISHING#0 |
| 53 |
Publishing Site |
BLANKINTERNET#0 |
| 53 |
Publishing Site w Workflow |
BLANKINTERNET#2 |
| 33 |
News Site |
SPSNHOME#0 |
| 34 |
Site Directory |
SPSSITES#0 |
| 38 |
Report Center |
SPSREPORTCENTER#0 |
| 47 |
Collaboration Portal |
SPSPORTAL#0 |
| 50 |
Search Center with Tabs |
SRCHCEN#0 |
| 51 |
Profiles |
PROFILES#0 |
| 52 |
Publishing Portal |
BLANKINTERNETCONTAINER#0 |
| 54 |
My Site Host |
SPSMSITEHOST#0 |
| 90 |
Search Center |
SRCHCENTERLITE#0 |
| 90 |
Search Center Advance |
SRCHCENTERLITE#1 |
|
FAST Search Center |
SRCHCENTERFAST#0 |
|
Visio Process Repository |
visprus#0 |
Stapler Scope and Sequence of Activation
Farm scoped features are activated in this order. - Features from site definition
- Features without activation dependencies from stapler
- Features with activation dependencies from stapler (in correct sequence)
- When using WebApplication scope there does not seem to be any specific order.
Feature Activation Test Results
In performing the following tests I frequently received error messages that referred to web-scoped features as "Site scoped" and site-scoped features as "Site Collection scoped" features. When troubleshooting your own dependencies carefully read any error messages.
| Scenario |
Activation Type |
Success? |
Notes |
| Activate hidden site-scoped feature using staple feature |
Automatic |
Yes |
Staple feature can be used to activate a hidden site-scoped feature. |
| Activate visible site-scope feature using staple feature |
Automatic |
No |
Staple feature cannot be used to activate a visible site-scoped feature. |
| Activate hidden web-scoped feature using staple feature |
Automatic |
Yes |
Staple feature can be used to activate a hidden web-scoped feature. |
| Activate visible web-scoped feature using staple feature |
Automatic |
Yes |
Staple feature can be used to activate visible web-scoped features. |
| Activate web-scoped feature using a stapled hidden site-scoped feature |
Automatic |
No |
Hidden features cannot activate other features. |
| Manually activate web-scoped feature with dependency on another visible web-scoped feature |
Manual |
Yes |
Manually activating a web-scoped feature can be used to activate another web-scoped feature. |
| Manually activate web-scoped feature that has a dependency on a hidden site scoped-feature |
Manual |
No |
Web-scoped feature cannot activate a hidden site-scoped feature. This would be a cross-scoped feature that attempts to activate a feature across scopes to a higher level scope. |
| Manually activate site-scoped feature using a web-scoped feature |
Manual |
No |
Although web-scoped features can have dependencies on site-scoped features they cannot activate them. |
Resources
|
| By Carey Cole, Lecturer at James Madison University, and Lauren Danker and Kristen Podwika, SharePoint Independent Study Students at James Madison University
This is the second blog post in a series on the subject of Incorporating a SharePoint Workflow into a Business Course. My goal is to provide other University instructors with the materials and knowledge necessary to introduce SharePoint Workflows to their business students. This is the first year we have implemented such a program at James Madison University, and we are excited to share our progress, setbacks, and successes in order to better prepare others.
This entry initially focuses on the introduction of this assignment to students and later provides a brief description of workflows using SharePoint Designer.
The Classroom Setting
This assignment is given to students in a junior level Computer Information Systems major class. Please refer to my first post, Incorporating a SharePoint Workflow into a Business Course, for the initial problem definition. After receiving the problem statement students have two weeks to create a to-be solution and implement a workflow reflecting their solution.
This class of 25-30 students is split into teams of 4-5 students for the assignment. Each group will collaborate using SharePoint to complete the project. Each student will have visitor permissions to the professor’s main site, where they can reference documents and view due dates.
Each group will have their own subsite with Designer permissions. With Designer permissions students can view, add, update, delete, approve, and customize their site. We gave Designer access instead of Contributor access so students can utilize SharePoint Designer. On these subsites the students will be setting up their workflow and collaborating with their group and professor. The students will not have access to the other group’s sites. Please see Figure 1 for a screen shot of our class site.

Figure 1: Team Site
Classroom Presentation
The initial presentation on workflows for this assignment is done in the classroom. The students bring their laptops to class, for a “laptop” day (this could also have been done in a classroom computer lab). At James Madison University (JMU), students have had some exposure to SharePoint before; however the assignment is designed to expand their knowledge and help them utilize some of the SharePoint tools. Before coming to class, each student was provided with their SharePoint user account and password. The students were also split into groups before the classroom presentation.
During this class, students were given user documentation on the basics of SharePoint, SharePoint Designer, and Workflows. The students will be presented with a YouTube video to supplement the Workflow documentation on how to create a workflow.
Classroom Workflow
After receiving the initial documentation and classroom presentation, students have two weeks to work with their teams and create a workflow to solve the business problem described in my first post. This involves linking a workflow to a specific document library on their SharePoint site, developing the logic of the workflow with their “To-Be” Flowchart and working with a variety of conditions and actions to complete the process. In addition to basic documentation, students are given a list of all of the conditions and actions available in SharePoint Designer, as well as a list of the conditions and actions recommended for this assignment.
The following figures show the steps of a sample completed workflow and the corresponding activity diagram that explains its logic. It is triggered each time a new document is added to the Shared Documents library. The first condition requires the document name to include both the words "Application" and "GMAT." Each step represents a new grouping of actions within the business process. The workflow is completed after the application receives its final level of approval.
Step 1 in the workflow begins with a condition that requires a document to have both the words "Application" and "GMAT" in the title. If this condition is met, the workflow will perform the subsequent two actions. If this condition is not met the workflow will terminate. If the clerk verifies that the application is completed, step two of the workflow begins. Figure 2 displays the first step of the workflow in Visio while Figure 3 displays the first step in SharePoint Designer.
 Figure 2: Workflow Step 1 Diagram
 Figure 3: Workflow Step 1
In Step 2, the application is sent to a new person, the adviser, for review and a possible recommendation. Once the Adviser reviews the application, step three is initiated. Figure 4 displays the second step of the workflow in Visio while Figure 5 displays the second step in SharePoint Designer.
 Figure 4: Workflow Step 2 Diagram
 Figure 5: Workflow Step 2
Step 3 includes the logic behind the decisions being made about the applicant. The decisions made by the faculty panel and by the dean will determine who receives acceptance and rejection letters to the University’s Masters program. Once the e-mails have been sent, the workflow will terminate. Figure 6 displays the final step of the workflow in Visio while Figure 7 displays the final step in SharePoint Designer.
 Figure 6: Workflow Step 3 Diagram
 Figure 7: Workflow Step 3
The workflow described above is similar to what the students are expected to complete. Before implementing such an assignment in a classroom setting, it is critical to have a basic understanding of SharePoint Designer and how it is used to develop workflows. A future posting will address this issue.
Posting Final Thoughts
Since the assignment has not been completed yet it will be interesting to see how the students perform with this exercise. At this time I am thinking there will be two more postings on this exercise. The next one will focus on the YouTube video and the SharePoint Designer documentation. The last posting will focus on how the students in class handled the SharePoint Workflow class assignment.
|
| One of the most practical and efficient ways to set up a basic level of security for forms libraries and other site objects in a SharePoint site is to align your Active Directory security groups with your SharePoint permissions. Although this is not already configured out of the box in SharePoint 2010, you can achieve this by assigning Active Directory security groups to the SharePoint groups you use to grant permissions to your libraries and lists. That way, as soon as a new site user who's a member of an Active Directory security group comes online, the person is automatically granted the correct permissions to access your library documents and list items.
Once you've referenced Active Directory security groups in your site permissions parameters, there's no need to manually add individual users to SharePoint permissions groups. So, for example, by referencing the appropriate AD security groups you can set up permissions so that new site users in the account management group in AD are automatically granted full read/write access to employment forms and documents on your site, while users in the account processing group are granted read access only.
Prerequisite
To allow users to access form libraries or other site objects based on AD security groups, you'll need to contact your site IT administrator and get the names of the AD security groups that map to your libraries.
For detailed information about how to set up permissions for SharePoint 2010 lists and libraries, see Edit permissions for a list or library or Permissions Management
How to grant site permissions through Active Directory security groups
- If you don't already have a permissions group ready for this setup, create a new one from for the site by choosing Site Actions > Site Permissions > Create Group, enter a group name that represents a role, such as Human Resource Managers, then define permissions for the group.


- Select a library and click Library Permissions from the Library tab in the ribbon.

- Click Grant Permissions in the Permissions Tools tab.

NOTE: If the site to which you're adding the group inherits permissions from a parent site, click Stop Inheriting Permissions in the ribbon. The site in the above example does not inherit permissions so the Stop Inheriting option doesn't appear.
- Enter one or more Active Directory security group names in the Select Users text box, depending on how many security groups may share the same access permissions to the selected library.

- Under Grant Permissions, click Add users to a SharePoint group and enter the name of the group that you already set up in step 1.
- Click OK.
Now anyone who needs to access your site content and is listed in an Active Directory group that you've referenced in the site permissions forms will be granted the correct permissions. Note that permissions may take some time to process, depending on network conditions that affect synchronization between Active Directory and SharePoint servers.
mp- |
| By Joe Levine
You may have noticed the "I Like It" and "Notes & Tags" ribbon commands that are available on some types of site pages.
 These commands allow you to tag SharePoint content, typically documents in libraries. Tagging is an effective way to keep track of content. But tagging content is also a social activity: As you and your colleagues tag content, you can share each others' discoveries, and build your pool of resources.
This blog provides a quick refresher on tagging in SharePoint. Additionally, it focuses on how you can tag any Web site -- SharePoint or other -- and the benefits of doing this activity.
The fastest and easiest way to tag content is to click "I Like It". However, tagging with "I Like It" doesn't allow you to describe the content you're tagging. Tagging with the "Notes & Tags" tool is a bit more work, but allows you to categorize your tagged content using descriptive terms. You can see all of your tags, including "I Like It" on the Tags and Notes tab of your profile. Here, they appear in a "Tag Cloud," which emphasizes the tags that you've used most frequently.
 You can click a tag in your tag cloud to quickly see all content you've tagged with it.

Colleagues who have checked "Tagging by my colleague" in their profiles receive an update in their newsfeed to tell them about the content you've tagged. Similarly, colleagues get newsfeed updates if you use a tag they've listed in their profiles as an "Interest", and they've checked "Tagging with my interest" in their profiles.

The Notes & Tags ribbon command is available on only certain SharePoint site pages. However, with a bit of setup, you can add the Notes & Tags tool as a favorite in your Web browser, or even add it to your Favorites Bar. By doing so, you make the Notes & Tags tool available when visiting any Web page.
- On your profile page, click the Tags and Notes tab.
- Follow the instructions at the bottom of the page titled "Add SharePoint Tags and Notes Tool".

If you add your Notes & Tags tool to your Favorites Bar, you can rename it any way you want.

Now you can open the Notes & Tags tool when visiting any Web page, add tags to appear in your tag cloud, and share the site pages you've found with colleagues in their newsfeeds. You can also enter notes about these site pages to appear on your note board.
That's all there is to it. As you can see, adding the Notes & Tags tool to your Favorites can greatly expand the scope and usefulness of social tagging in SharePoint.
For more detailed information on this topic, see Use tags and notes to share information with colleagues or watch a video on the same topic. |
| SharePoint includes three publishing column types that enable you to control how rich text, images, and hyperlinks are handled on site pages, lists, and libraries. A description of each column type follows. Incidentally, these column types have long names and are sometimes indicated by the shorter name you see in the table below.
Full HTML content with formatting and constraints for publishing |
Publishing HTML |
Enables rich text authoring by specifying font, styles, links, tabular layouts, reusable content, and so on. Helps you manage authoring options by placing content field controls within SharePoint page layouts. Content and formatting constraints can be applied to ensure new content appears according to pre-established styles and themes. |
Image with formatting and constraints for publishing |
Publishing Image |
Enables authors to provide metadata about the images used on their site. This metadata includes image path, alt text, hyperlink, image alignment, thumbnail, and rendering size. Provides an easier way to add images rather than manually entering the URL of the image or web reference. Control over images can be set when placing content field controls within SharePoint page layouts. |
Hyperlink with formatting and constraints for publishing |
Publishing Hyperlink |
Enables authors to browse to an object and link to it rather than typing a URL. Also provides the option of entering display text and tool tip metadata. Link formatting and other options can be set when placing content field controls within SharePoint page layouts. |
Before you can use any of these column types, you must create publishing columns. After that, add the newly created publishing columns to your content types, lists, or libraries. In this post, I’ll show you how.
Note: Publishing must be enabled by a site collection administrator for these column types to appear. To enable publishing, go to the Site Actions menu and click Site Settings. Under Site Collection Administration, click Site collection features. Scroll down to SharePoint Server Publishing Infrastructure and click Activate.
Create the publishing column
Let’s start by creating a publishing column. We’ll use the Publishing Hyperlink column type for this example.
Note: You must be a site administrator or site collection administrator to create publishing columns.
- Go to the Site Actions menu and click Site Settings.
- Under Galleries, click Site columns.
- Click Create.
- Give the column a name. For this example, we’ll use “Hyperlink.”
- Select Hyperlink with formatting and constraints for publishing from the list of column types.
- Add the column to the publishing columns group. This is an optional step but can be helpful for organizing columns. Your selections should look like this:

Add a publishing column to a content type
Publishing columns based on the Publishing HTML and Publishing Image column types are already part of the Article Page, Enterprise Wiki Page, Project Page, and Welcome Page content types. Publish Hyperlink is not. In this procedure, we’ll add our new Hyperlink column, which is based on the Publishing Hyperlink column type, to a content type. The procedure is the same regardless of whether the content type is built-in or custom.
Note: You must be a site administrator or site collection administrator to edit content types.
- Go to the Site Actions menu and click Site Settings.
- Under Galleries, click Site content types.
- Scroll down the list and select content type to which you’ll add the column.
- At the bottom of the content type information page, click Add from existing site columns.
- Select the Publishing Columns group (or whatever group you chose above), click Hyperlink in the Available columns list, and click Add. Your selections should look like this:

Now your content type includes the Hyperlink column. When you edit the properties for any new page created from that content type, you’ll see the column listed.

Add a publishing column to a list or library
The steps for adding a publishing column to a list or library is very similar to adding one to a content type. In this example, we’ll continue to use the Hyperlink column that we created in the first procedure. It doesn’t matter whether the list or library is built-in or custom, the procedure is exactly the same.
Note: You must be a site administrator or site collection administrator to add columns to lists and libraries.
Navigate to your list or library.
On the List tab of the ribbon, in the Settings group, click List Settings. (If you’re adding the column to the library, click Library Settings.)
Under Columns, click Add from existing site columns.
Select the Publishing Columns group (or whatever group you chose above), click Hyperlink in the Available columns list, and click Add. Your selections should look like this:

Now, your list includes the Hyperlink column. When you add an item to the list, you will see the column in the properties page.
 Go ahead and click the blue text to add a new hyperlink. You’ll see the expanded set of metadata fields that publishing columns, which are only available on publishing sites, can provide.

For more information about site columns, see Site column types and options on Office.com.
Tricia
|
|
This is the fourth post in a series on training your people to increase user engagement. The premise of this series is that by creating a training site collection in your SharePoint environment, you can facilitate ongoing learning.
In my current environment I have been delivering 1 hour “brown bag” sessions covering a set of core skills. The sessions are supported with hands on labs that the attendees can complete on their own. The lab instructions are based on each attendee having their own personal training site.
Lab instructions do take time and effort to get right. Since the population I am serving is brand new to SharePoint, and they are making time in their schedules to work on the exercises, it is important that the exercises be relatively short and use screen shots as much as possible.
The three previous posts are here:
In this post I will provide instructions on working with Libraries. The prerequisites for this lab are:
- Your trainees have a training site (of course).
- They did labs 1 and 2 so they can navigate around SharePoint and they can create a site.
- You have provided a package of sample files that will be used during the exercise. You provide a simple spreadsheet that categorizes the sample files.
The logic is that the trainee will practice the skills they learned in the prior lessons by navigating through SharePoint and creating a site. The trainees will practice new skills by creating a library, some columns, and then views to organize the sample content that you provide.
Lab 3 Working with Libraries
Lab Objectives:
- Setup a site for lab exercises
- Create new document library
- Migrate Content from File Share to SharePoint
- Create Columns
- Create Views
Upload and Organize Files in a Document Library
Exercise 1 – Create a site to explore different list types and settings
Task 1- Create a new site called “Daily Work”.
1. Navigate to your student site which you should be able to find from the Training Site.

Figure 1 - Navigate to your personal Training Site
2. Select Site Actions | New Site 3. Select the Blank Site template 4. Click More Options 5. On the Create page. Enter the following information:
a. Title: Daily Work b. Description: I am going to use this site to practice working with lists. c. URL Name: DailyWork d. Select, Use same permissions as parent site e. Select, Use the Top Link bar from the parent site f. Click Create – The blank site template will create an empty SharePoint site. It is not very useful yet since there are no lists or libraries to store and manage information. To verify this, use the All Site Content page.
 Figure 2 - Daily Work Site
6. Under the Quick Launch area of your page, click All Site Content

Figure 3 - All Site Content is below the Quick Launch menu

Figure 4 - All Site Content - No Lists or Libraries in a blank site
7. Review the All Site Content Page and notice how there are no lists or libraries included with the Blank Site Template (if you see any lists or libraries, you didn’t select the Blank Site Template).
 Figure 5 - Navigate up the bread crumb
8. Use the Navigate Up control to navigate up to your Daily Work site.
Task 2 – Create the “Every Day Documents” document library
1. Select Site Actions | More Options.
2. Select Document Library
3. In the name field, type EveryDayDocuments
4. Click Create.
5. On the ribbon, click the Library tab and then click Library Settings.
 Figure 6 - Library Settings on the ribbon
6. On the Document Library Settings Page, click Title, description and navigation.
After creating the library without spaces in the name so the URL is easier to read and a little shorter, we will use the Library Settings page to add spaces in the name so it displays with spaces. This way our URL is friendly and the library name in our Navigation displays with spaces, which looks nicer. If we initially created our library with spaces then our URL would fill those spaces with “%20” which is not nice to read.
7. In the Name field, add a space between Every Day Documents. 8. In the Description field type, Upload and organize files that I work with every day. 9. Confirm that Yes is selected for Display this document library on the Quick Launch. 10. Click Save. 11. Navigate back to your Daily Work site homepage.
Exercise 2 – Adding and organizing documents in SharePoint
Task 1- Download and unzip sample content from the Training site
For the purposes of this exercise, I zipped up some sample files and put them on the training site for the trainees to work with. The trainees are going to download them, unzip them and upload them to their Every Day Documents library. Depending on your audience, it may be better to store the sample files on a network drive that they all have access to. This was not possible in my environment so I uploaded them to the training site as a single zip file.
Explain to the trainees that these are sample files for this exercise, but they should think about the files that they actually work with on a regular basis.
2. On Quick Launch menu, select Training Documents.
3. In the Training Documents library, right click Sample-Content and choose Save Target as…
4. Save the Sample-Content.zip file to a location of your choosing. (your desktop, a folder etc. )
5. Browse to the Sample-Content.zip file and right-click it and choose Extract All.
6. From the extracted files, open Document-Classification-Worksheet.xlsx.
| Conf_Room_List_Sept11.xlsx |
Meetings |
| LTR-Pro-Staff.docx |
Policy |
| NewEmployeeChecklist.docx |
Onboarding |
| Operating-expense-budget1.xlsx |
Practice File |
| PivotTable-Practice-SalesTransactions.xls |
Practice File |
| TOP Codes.xlsx |
Accounting |
| Employee-Recognition-Program.docx |
Staff Development |
| Training-Policy.docx |
Staff Development |
| Document-Classification-Worksheet.xlsx |
Planning |
Table 1 - Document Classification Worksheet
7. Review the Document-Classification-Worksheet.xlsx . Notice how it is a simple list of ten files with a column that labels them with different categories. In SharePoint we can add columns to our libraries that we can use to classify and organize our information. Once we classify our information SharePoint provides some pretty incredible tools that we can use to organize and manage our content. Let’s keep it simple for now and create a choice column in our Every Day Documents library that we can use to organize our files.
Task 2 – Create Choice Columns to organize your content and upload documents
In this task you are going create one choice column in your Every Day Documents library. You will use the Document Categories as choice values. You will then adjust the column default values before uploading content.
1. Navigate back to your Daily Work site.
2. On the Quick Launch menu, select Every Day Documents
3. On the ribbon, select the Library tab.
4. On the ribbon, select Create Column
5. In the Name field, type Document Category
6. For column type, select Choice.
 Figure 9 - Create Choice Column
7. Once you select Choice as the type of column the page updates and displays options that apply to Choice columns.

Figure 10 - Choice column options
8. In the box labled "Type each choice on a separate line:" Replace “Enter Choice #1, Enter Choice #2, Enter Choice #3” with the Document categories from your worksheet:
Meetings Policy Onboarding Practice File Accounting Staff Development Planning
9. Select the radio button to display your choice values using a drop-down menu. 10. Select No for Allow Fill-in Choices. 11. Notice the default value option. When you upload multiple files at once, the default value will be used. This is a handy way to move files from your shared drive to SharePoint. 12. Click OK 13. On the Library page, click Add Document. 14. On the Upload Document dialog box, click Browse. 15. Browse to your sample content and select Conf_Room_List_Sept11.xlsx. 16. Click Open. 17. Click OK.
 Figure 11 - File Uploaded to SharePoint
18. Make sure the Title is descriptive, this one looks OK. An inaccurate title can confuse people that find the document through search. 19. Since this file falls into the Meetings category, make sure Meeting is selected. 20. Click Save. 21. Repeat steps 13 – 20 to upload the rest of your sample documents. Refer to the Document-Classification-Worksheet.xlsx to select the Document Category for each document you upload.
You could upload multiple files, and if you did, you wouldn't be able to choose the Document Category for each document. Instead the column default document category would be added to all the files uploaded at once.
22. After uploading the sample content and selecting the correct categories, your library should look similar to the screen shot below.

Figure 11 - Sample Content Uploaded to SharePoint
Exercise 3 - Create library views to display your newly uploaded content
Task 1 – Create a Grouped View
The "Every Day Documents" library now is now populated with ten files. Let’s create a Grouped View to display the files in Groups by Document Category. In our practice we are working with a small number of files. When you are doing the exercise think how useful this would be if you were working with 50 or more files.
1. On the Ribbon, select the Library tab. 2. On the Ribbon, select Create View. 3. On the Create View page, select Standard View. 1. In the View Name field, type Grouped by Category. 2. Scroll down the page and expand Group By. 3. Under First group by the column:, select Document Category. 4. Scroll down to the bottom of the page and click OK. 5. Explore your new grouped view.

Figure 13 - Grouped View
Lab Summary
In this Lab you learned and practiced the following skills:
• Create Choice Columns
• Uploaded Content to SharePoint
• Created a Grouped view
Now that your users have some sample files and the Every Day Documents library, you can create addtional exercises. For example you could have them set the choice column default value to "Policy," and then have them upload multiple policy files so they see how each newly uploaded file has Policy as the document category. You could also build on this and create folders and set the default column values by folder.
Next month I will build on this lesson and cover:
Creating an filtered view
Configuring versioning
Configure and check library permissions
Co-Authoring a word document
Remember, keep the lab exercises short and support your SharePoint project by delivering brown bag sessions.
--Gregory
|
| I want to share a few tips about finding and working with your SharePoint content. I hope you find them useful.
Access libraries with Windows Explorer
Did you know you can access a site's document libraries via Windows Explorer by using the WebDAV protocol? WebDAV is an extension of Hypertext Transfer Protocol (HTTP).
To use this protocol, you need to add the davwwwroot path to the URL. Type the path in the Windows Explorer address bar using in the following format:
\\server\site\davwwwroot
For example, if your site’s URL is http://contoso/sales, you would type \\contoso\sales\davwwwroot.
NOTE: For a more detailed look at working with files in Windows Explorer, see Joe Levine's post, Ways to work with your SharePoint content in Windows Explorer.
Move files between libraries and do other file tasks
In Microsoft SharePoint Server 2010 and SharePoint Server 2007, you can use the Site Content and Structure page to move or copy files between libraries located in different sites within your site collection. The page also has other uses: You can also perform actions on files, such as checking files in or out, and you can view reports about the files in the site collection.
To get to the Site Content and Structure page, do one of the following:
- On the Site Settings page, click Content and Structure.
- Append _layouts/sitemanager.aspx to your URL.
NOTES:
- You must have a minimum of Contribute permissions to access the Site Content and Structure page.
- Before you can use the Site Content and Structure page, you must activate Office SharePoint Server Publishing Infrastructure (Site collection features) and Office SharePoint Server Publishing (Site Feature).
- The Site Content and Structure page is not available in Microsoft SharePoint Foundation 2010, Windows SharePoint Services 3.0 or Windows SharePoint Services 2.0.
Link SharePoint 2010 Document Libraries to Outlook 2010
It's possible to synchronize a SharePoint library, contact list, task list, Project task list and a certain type of SharePoint external list with Microsoft Outlook 2010. The ability to synchronize lists and libraries can help you work more collaborate more efficiently on projects.
Read more about this on Office.com in the article Synchronize SharePoint 2010 content with Outlook 2010.
Thanks,
Anthony Labriola
|
View in Web Browser /Blogs/GetThePoint/_layouts/VisioWebAccess/VisioWebAccess.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 0x0 0x1 FileType vdw 255 Compliance Details javascript:commonShowModalDialog('{SiteUrl}/_layouts/itemexpiration.aspx?ID={ItemId}&List={ListId}', 'center:1;dialogHeight:500px;dialogWidth:500px;resizable:yes;status:no;location:no;menubar:no;help:no', function GotoPageAfterClose(pageid){if(pageid == 'hold') {STSNavigate(unescape(decodeURI('{SiteUrl}'))+'/_layouts/hold.aspx?ID={ItemId}&List={ListId}'); return false;} if(pageid == 'audit') {STSNavigate(unescape(decodeURI('{SiteUrl}'))+'/_layouts/Reporting.aspx?Category=Auditing&backtype=item&ID={ItemId}&List={ListId}'); return false;} if(pageid == 'config') {STSNavigate(unescape(decodeURI('{SiteUrl}'))+'/_layouts/expirationconfig.aspx?ID={ItemId}&List={ListId}'); return false;}}, null); return false; 0x0 0x1 ContentType 0x01 898 Edit in Browser /_layouts/images/icxddoc.gif /Blogs/GetThePoint/_layouts/formserver.aspx?XsnLocation={ItemUrl}&OpenIn=Browser&Source={Source} 0x0 0x1 FileType xsn 255 Edit in Browser /_layouts/images/icxddoc.gif /Blogs/GetThePoint/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser&Source={Source} 0x0 0x1 ProgId InfoPath.Document 255 Edit in Browser /_layouts/images/icxddoc.gif /Blogs/GetThePoint/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser&Source={Source} 0x0 0x1 ProgId InfoPath.Document.2 255 Edit in Browser /_layouts/images/icxddoc.gif /Blogs/GetThePoint/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser&Source={Source} 0x0 0x1 ProgId InfoPath.Document.3 255 Edit in Browser /_layouts/images/icxddoc.gif /Blogs/GetThePoint/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser&Source={Source} 0x0 0x1 ProgId InfoPath.Document.4 255 View in Browser /Blogs/GetThePoint/_layouts/xlviewer.aspx?id={ItemUrl}&DefaultItemOpen=1 0x0 0x1 FileType xlsx 255 View in Browser /Blogs/GetThePoint/_layouts/xlviewer.aspx?id={ItemUrl}&DefaultItemOpen=1 0x0 0x1 FileType xlsm 255 View in Browser /Blogs/GetThePoint/_layouts/xlviewer.aspx?id={ItemUrl}&DefaultItemOpen=1 0x0 0x1 FileType xlsb 255 View in Browser /Blogs/GetThePoint/_layouts/xlviewer.aspx?id={ItemUrl}&DefaultItemOpen=1 0x0 0x1 FileType ods 255 |
|
|
|
|
|
|
View in Web Browser /Blogs/GetThePoint/_layouts/VisioWebAccess/VisioWebAccess.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 0x0 0x1 FileType vdw 255 Compliance Details javascript:commonShowModalDialog('{SiteUrl}/_layouts/itemexpiration.aspx?ID={ItemId}&List={ListId}', 'center:1;dialogHeight:500px;dialogWidth:500px;resizable:yes;status:no;location:no;menubar:no;help:no', function GotoPageAfterClose(pageid){if(pageid == 'hold') {STSNavigate(unescape(decodeURI('{SiteUrl}'))+'/_layouts/hold.aspx?ID={ItemId}&List={ListId}'); return false;} if(pageid == 'audit') {STSNavigate(unescape(decodeURI('{SiteUrl}'))+'/_layouts/Reporting.aspx?Category=Auditing&backtype=item&ID={ItemId}&List={ListId}'); return false;} if(pageid == 'config') {STSNavigate(unescape(decodeURI('{SiteUrl}'))+'/_layouts/expirationconfig.aspx?ID={ItemId}&List={ListId}'); return false;}}, null); return false; 0x0 0x1 ContentType 0x01 898 Edit in Browser /_layouts/images/icxddoc.gif /Blogs/GetThePoint/_layouts/formserver.aspx?XsnLocation={ItemUrl}&OpenIn=Browser&Source={Source} 0x0 0x1 FileType xsn 255 Edit in Browser /_layouts/images/icxddoc.gif /Blogs/GetThePoint/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser&Source={Source} 0x0 0x1 ProgId InfoPath.Document 255 Edit in Browser /_layouts/images/icxddoc.gif /Blogs/GetThePoint/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser&Source={Source} 0x0 0x1 ProgId InfoPath.Document.2 255 Edit in Browser /_layouts/images/icxddoc.gif /Blogs/GetThePoint/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser&Source={Source} 0x0 0x1 ProgId InfoPath.Document.3 255 Edit in Browser /_layouts/images/icxddoc.gif /Blogs/GetThePoint/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser&Source={Source} 0x0 0x1 ProgId InfoPath.Document.4 255 View in Browser /Blogs/GetThePoint/_layouts/xlviewer.aspx?id={ItemUrl}&DefaultItemOpen=1 0x0 0x1 FileType xlsx 255 View in Browser /Blogs/GetThePoint/_layouts/xlviewer.aspx?id={ItemUrl}&DefaultItemOpen=1 0x0 0x1 FileType xlsm 255 View in Browser /Blogs/GetThePoint/_layouts/xlviewer.aspx?id={ItemUrl}&DefaultItemOpen=1 0x0 0x1 FileType xlsb 255 View in Browser /Blogs/GetThePoint/_layouts/xlviewer.aspx?id={ItemUrl}&DefaultItemOpen=1 0x0 0x1 FileType ods 255 |
|
|
|