Making Sense of the SharePoint World

Dec-262008

SharePoint in 2008 – An Interesting Road

MCBD19892_0000[1]

Driving Through Flyover Country

2008 should theoretically have been a boring year for SharePoint. The current version (WSS 3.0 and MOSS 2007) was released in 2006. The next version wouldn’t be out until 2009, if not later. The software equivalent of flyover country.

Yet, if you (like me) have actually driven through this so-called flyover country, you will know that there is a lot going on in that vast middle ground:

You have “tourist traps” like Wall Drug, and the Corn Palace.

image

You’ll find Natural wonders like Devil’s Tower, Wyoming, and of course Yellowstone. Legends like Deadwood, South Dakota – just a stone’s throw from that ultimate in stone carving – Mount Rushmore.

image

Not to mention the over-all beauty of this great land.

image

The same is true with SharePoint in 2008. In what could have been a year of coasting, those following The SharePoint Road found plenty to be excited about.

Among the sights:

  • We welcomed a pair of new members to the family – Search Server, and the free Search Server Express
  • Infrastructure Updates brought Search Server’s enhancements to MOSS, along with some much needed improvements to Content Management
  • Not to mention, Service Packs and the other “normal” updates that occur.

Search Server 2008 Express  Search Server 2008

But even more impressive than the evolution of the product itself has been the reaction of the community:

  • SharePoint became a Billion Dollar Product.
  • A huge ecosystem has grown up around SharePoint.
  • Books, Add-ins, training, documentation, and other support material has proliferated

In fact, opportunities to get “up-close and personal” with key players in the SharePoint world have been many:

  • The Microsoft SharePoint Conference 2008 was a sell-out, and had the greatest attendance of any SharePoint-only event to date.
  • Beyond Microsoft, SharePoint Connections, and the SharePoint Best Practices conference were also huge hits.
  • Users Groups and user-inspired events have sprung up everywhere, and are growing fast.

image Best Practice SharePoint Conference
image

A taste of “14”. Some tidbits about the next version have come out recently:

  • “Microsoft SharePoint Services” for the Cloud, shown as part of Windows Azure
  • Fully interactive, web-based versions of Office applications. Will these be part of the SharePoint Family?

Looking Forward

So, you see, 2008 has been anything but boring in the SharePoint space. But what about next year? What does 2009 hold?

Predicting the future is never an exact science, but I think, even with the down economy, we can be certain that there will still be more excitement in the SharePoint world:

  • More Conferences and Events:
    • Connections is a occurrence.
    • Of course, SharePoint will always be well-represented at Microsoft’s TechEd and the Professional Developers Conference (PDC).
    • The next Best Practices conference is the first week of February – Don’t Miss This one! (And I’m not just saying that because I’m going to present…)
  • More Updates:
    • Service Pack 2 should be out early next year.
    • Constant growth in the number of add-ins available, both in the marketplace, and on CodePlex
  • Betas? Customer Previews? The Real Deal? Well, I wouldn’t hold my breath on getting final code next year, but it wouldn’t surprise me at all to see something come out that we can play with.

There you have it. My version of a retrospective on 2008, and a look towards 2009. I hope you have enjoyed travelling the SharePoint road with me this year, and I hope to have you along for the ride next year!

image


Published: Dec-26-08 | 0 Comments | 0 Links to this post
Tagged as: Blog, General

Dec-232008

A Page in a Box – The Easiest SharePoint Integration

MCj03970360000[1]

Gift-wrapping Web Applications with the Page Viewer Web Part

With the Holidays upon us, everyone is putting things in boxes. Boxes are very convenient – they let you just drop something into them without having to change anything about the item being packaged.

As you start to deploy SharePoint in your organization, you will often find people wishing that they didn’t have to bounce from one web site to another all of the time. With Data Views, Search Federation, and other tools, you have seen how easy it is to get the information from other systems and applications into SharePoint. However, there are times when you just want to be able to get to another application directly within your SharePoint page.

Fortunately, there is a web part made just for such a situation – the Page Viewer Web Part. The Page Viewer is nothing more nor less than a box in which you can place and display content from another location.

You add a Page Viewer to your page just like any other Web Part.

image

The initial web part doesn’t have anything in it except instructions on how to add content:

image

Once you click the link to open the tool pane,

image

You can select a web page, a folder (file share), or specific file. Unlike some other web parts, this file is NOT accessed by the SharePoint server as an intermediary. It is retrieved and rendered directly by the user’s browser. Because of this, make sure you are specifying a location that is accessible from your expected users’ client PC’s.

Note: Technically, what you are doing is feeding an “iFrame” – essentially a browser within a browser.

You will probably want to adjust the settings of the "Appearance” section in order to make sure the web part is big enough to show the critical parts of the page you are selecting.

image

Then, once you hit “OK” and exit page edit mode, the external page is living happily inside your SharePoint site!

image

Of course, it is helpful if the site you are embedding in the Page Viewer offers a mode without a lot of extraneous “chrome”. Some applications offer a “portal mode” page, just for such usage.

So, that’s it. Very “back to basics”, but also potentially quite useful.

I hope you enjoy this little gift, in a little box, from SharePoint.

I wish you all a Merry Christmas!


Dec-152008

Best Bets and Keywords in SharePoint and Search Server

wheel "When it Absolutely, Positively, has to be Found."

One of the key features of Microsoft Office SharePoint Server 2007 (MOSS), and Microsoft Search Server 2008 (MSS) - including Express (MSSX), is Enterprise Search. What you may not realize is that SharePoint actually includes two fundamentally different mechanisms for providing search results to your users. I'm not talking about WSS versus MOSS/MSS search. Rather, I'm talking about a second, parallel, system that returns results to user queries - often on the same page as the "regular" search engine.

So, what is this "shadow" search mechanism? Keywords and Best Bets. Although you may have heard of them - possibly even used them on your sites - you probably didn't know that they were completely independent of your main Enterprise Search corpus. This independence brings with it a number of ramifications. While mostly positive, it is important to understand them in order to both avoid potential pitfalls, as well as take maximum advantage of this powerful capability.

Enterprise Search - Not Enough on its Own

Enterprise search is a great tool to help your users find the information they need; however, a search system alone cannot solve all problems related to true "Findability". Bill English's series on Findability and SharePoint details many other factors, such as corporate culture and information architecture, that play a major role. Still, the technology of search itself can be a limiting factor.

Most people are aware of how the basic search functionality works - you define a content source, and SharePoint crawls it - interpreting and indexing the contents of the files it encounters. Then, when your users enter a query into a form, the server looks in this index and returns results that match. Of course, this relies on several things being true. Among them:

  • The information exists
  • The information is in a content source being crawled
  • The terms being queried are contained in the crawlable properties of the information
  • The information has actually been crawled and compiled into the index at the time of the query (lag time)

Even where this is true, the user still may not actually "find" the information that is needed. Perhaps there are a large number of similar documents containing the chosen query term, or the desired term has special meaning in your organization, but is also used differently in other contexts. (This is also discussed in Bill's article series.)

Note that this weakness is not unique to SharePoint search. Any system you put into place - whether it is MOSS, the Big Yellow Box, or some other system - is going to be faced with the same issues. (While the others may also offer comparable capabilities, I'm focusing on the SharePoint/Search Server version here.)

All of this adds an element of risk to the search process. Like spinning the roulette wheel, you might hope you get the result you want, but there is always that element of doubt. Fortunately, in this case, you are actually "the House", and therefore have the ability to control the odds. In fact, you can stack the deck to ensure that the right information always comes out on top.

Place Your (Best) Bets!

The Keyword and Best Bets feature in SharePoint works very differently from the primary search. This is a completely manual system. You enter the terms you expect your users to use, and the results those terms should generate. No crawling, indexing or other "automated" processes need to take place. No services need to be reset. Results are available in queries immediately, and you know what the results will be, because you have defined them.

In many respects, this makes Keywords system more of a direct lookup system than a "search" system per se. But "search" is still the action your users perform, and "find the right information" is the desired result. Let's see how to make that happen.

Configuring Keywords and Best Bets

Keywords and Best Bets can be easily configured by a site collection owner. As always, you start with the Site Actions menu, and select Site Settings. Since Search is configured at the site collection level, if you are in a sub-site you will need to click through to "top level site settings" in order to get the page below.

image

Click the "Search Keywords" link. This will bring you to the Manage Keywords page.

image

The Manage Keywords page looks and operates much like a SharePoint list. You have the toolbar with its Add button, for example. Notice though, that it has a somewhat different search bar. Search can be very important here because you could end up generating a lot of keywords. The "where" dropdown gives you the ability to look up keywords various ways.

image

In addition, there are some predefined views listed in the Quick Launch area. These provided an appropriately reduced list based on information entered into the keyword definition. When you click Add Keyword, you are presented with this form, which is also used to edit existing keyword definitions.

image

Again, it looks a lot like any other list form in SharePoint.

There is only one required field - the keyword itself. Of course, a keyword alone doesn't do much to help your users. The Synonyms field allows you to register other terms your users might enter which should bring up the same results. For example, if your company president's name is "Selma Superior" you might have that as a keyword, with synonyms of CEO, Managing Director, President, or even Big Cheese. From that point on, any of these terms will return the entry associated with the keyword.

Note: Remember that the keyword/best bets system is independent of the primary search service. Synonyms you enter here will not affect regular results. To achieve a similar effect there, you need to edit the Thesaurus files on the SharePoint Servers.

Once you have used a term as a keyword or synonym, the system knows it has already been used, prevents you from using it again in another keyword definition. This can help you avoid creating ambiguous results.

image

The best bets are links to the actual pages or documents you want your users to find when they enter the keyword or its synonyms. When you click "Add Best Bet," you will see the form listed below.

 image

In addition to the link itself, you can provide some descriptive text. You can have multiple best bets on a keyword. You can also associate the same best bet with multiple keywords. Using the earlier example, one of the Best Bets for the CEO might be the Executive Committee's Newsletter/Blog. That location could be equally valid for the CFO and CIO.

You can enter some descriptive text, which will be shown along with any matching results. You can also use the keyword feature for time-sensitive information by entering a start and end date for the keyword's display, and review date to ensure the content is still valid. The contact information allows you to distribute ownership of different keyword entries, as well as automatically notify people when entries are due for review.

The results from keywords and best bets are displayed on the default SharePoint results page above the results from the standard search.

image

The keyword search system has its own web parts for displaying results. If you are creating your own results page, you will need to add either a "Search Best Bets" or "High Confidence Results" web part to that page.

More Ways to use SharePoint Keywords and Best Bets

Earlier I pointed out that most of the fields in a keyword configuration are optional. While it is true that a keyword "by itself" isn't very useful, there are a lot of ways you can use keywords that go beyond highlighting particular pages and files in your corpus. This is one of the big benefits of the system being independent of the primary search. Here are just a few examples:

Policy Flags

You can bring critical company information to the users' attention before they even click into a document:

  • Description text for obscene keywords might bring up the actual text of the company's profanity or abuse policy, without showing the offensive word itself.
  • Searches for "financials" might display a warning that any public release of financial information must go through the PR department.
Disambiguation In the case where a word could have several meanings, you can describe each definition, and provide appropriate detail links.
Announcements Use the time-stamp to ensure that searches for the Phoenix Office note that it is closed for remodeling.
"Sponsored" links Everyone wants "their" content listed first in search results. If it fits in with your resource charge-back model and information management policy, let them pay for premium placement.
Direct Information The real purpose of search is to help people find what they need. If the information can be shown directly in the result set, why make them click through to a document? This could be useful for a glossary of your industry's buzzwords, for example.
External Links Even when you do enter a link, there is no requirement that it be within your intranet corpus, or even within your company. This can be handy for such things as industry association web sites, or maybe an index of clients or competitors.

So, What's the Catch?

Of course there's a catch. Administration.

As a manual system, you need to be careful that information is not only entered correctly, but also maintained. If someone moves a document flagged in a best bet, you need to manually change the entry in the keyword system. You should be careful to include review dates and contact information on as many keywords as possible. Use the views provided for keywords that have expired or are due for review, and check them regularly.

Conclusion

The keyword and best bets system in SharePoint and Search Server gives you a powerful tool to increase the findability of information within your organization. However, it is not a panacea. Like any other aspect of SharePoint, it requires careful planning and long-term commitment to ensure that you get the most out of it. But if you double-down, do the legwork, and keep up with the maintenance, you will find you have a system that will put your users on a winning streak.


Dec-82008

Cross-browser Rich Text Editing and More in SharePoint

MCj04136380000[1]"It's not just for Firefox anymore"

Today I'm going to talk about one of the earliest enhancements that was available for the current release of SharePoint. It has been around for so long, that it has either fallen off folks' radar, or has never made it onto the screen for newer users. That's a little sad, because it has always been a very useful component, and in its latest release is even more so. What is this magic add-on? The Telerik RadEditor Lite.

Considering the complexity of the markup SharePoint generates, its out of the box cross-browser compatibility (though not perfect) is pretty good. One area of weakness for non-IE browsers, however, is rich text editing. Recognizing this, Microsoft came to an agreement with tools vendor Telerik, whereby they would produce a version of their RadEditor that could be downloaded and used within SharePoint sites - without cost, and without sacrificing supportability. (They had a similar deal for Content Management Server, or CMS.)

That was the state of affairs in 2007, which is all well and good. But, time marches on, and it is almost 2009. If you are new to SharePoint, or if that early release was the last time you evaluated (or updated) the RadEditor Lite, you could be missing out on some nice improvements that go beyond cross-browser compatibility.

Note: Almost everything in this article applies to all "rich text" experiences within SharePoint, from Announcement lists, to MOSS Publishing Pages (the original purpose). I'm going to be using a SharePoint's Wiki here for two reasons:

  1. Wiki pages, by default, are basically one big rich text field, making screen shots easy to get and understand.
  2. One of the primary complaints about the SharePoint Wiki feature is that it is too hard for users to incorporate images into their pages. As you will see, the RadEditor Lite makes this problem go away.

The Basics

Consider the default SharePoint experience. For most users, just browsing the site, things are pretty consistent, regardless of whether you are using Internet Explorer (left) or Firefox (right):

image image
(Click on the image to see the full-sized screen shots, if desired.)

But click the "Edit" option, and you can see the problem -

In IE, you get a traditional editing toolbar, and everything looks pretty much like it does on the read-mode page:

image

But in Firefox, all you see is plain text, with embedded HTML markup:

image

Not exactly the experience you want for a typical, non-technical, user - the kind that Wikis were intended for.

Installing the RadEditor Lite Control

The first step, of course, is to download the control from Telerik's web site. It isn't exactly high-profile for them these days, so you'll either have to dig for it, or just follow the download links I've provided on this page.

That that will get you is a ZIP file containing an EULA document, the solution package (RadEditorMOSS.wsp), and a very extensive help file. Since I'm not going to go into all of the customization details possible with this control (and there are a lot of them), you might want to keep this in mind.

This control does not provide an automatic installer, so you will need to manually add the solution to your farm.

  1. Extract the WSP from the ZIP file
  2. Add the solution to SharePoint:
    stsadm -o addsolution -filename {path you extracted to}\RadEditorMOSS.wsp
  3. Deploy the solution to the web applications where you want to make this control available. You can do this either through the Operations tab of Central Administration, or by using the STSADM command with the deploysolution operator.
    Note: This solution is deployed on a per-web application basis, not farm-wide.
  4. Activate the feature on the web sites where you want to use the RadEditor Lite.

Notice the granularity allowed in the deployment. The feature activation itself takes place at the Site, rather than Site Collection level. You also have two options for activation:

  1. Use RadEditor to edit List Items
  2. Use RadEditor to edit List Items in Internet Explorer as well

image

Once you have activated the first feature, you will see that FIrefox now shows a much richer editing experience, complete with all of the expected toolbars:

image

If you using RadEditor Lite on MOSS, you're done! Maybe (see the next section). If you are using it on WSS, there are a couple more steps to perform on your server. This is because, by default, the RadEditor Lite relies on some controls that are part of MOSS. However, it does have its own built-in controls that perform similar functions, so you just need to adjust an XML configuration file. (You can use RadEditor's native controls on MOSS, too, by making the same adjustments.)

The XML configuration file is usually located at:

c:\Program Files\Common Files\microsoft shared\Web Server Extensions\wpresources\RadEditorSharePoint\4.5.4.0__1f131a624888eeed\RadControls\Editor

"4.5.4.0__1f131a624888eeed" above is the version of the control you are using, and so may vary.

You need to edit the file named "listtoolsfile.xml"

Find the line

<tool name="MOSSLinkManager" />

and edit it to remove "MOSS", resulting in a tag reading:

<tool name="LinkManager" />

I would also add one of the following lines:

<tool name="AjaxSpellCheck" />

or

<tool name="SpellCheck" />

The tool provides spell checking, so why not use it?

Progress is Progressing

There are a couple of questions you might be asking yourself at this point:

  • Why are there two separate activation options? and
  • Why would I need to use this control in Internet Explorer, when it already supports rich text editing?

The answer to the first question is this - when the free RadEditor Lite was first released for SharePoint, it was officially licensed for one purpose - to provide rich text editing to non-Internet Explorer browser users in MOSS Publishing sites. That is because the agreement with Telerik was carried over from a similar agreement relating to Content Management Server (CMS), and MOSS Publishing was the direct replacement for CMS functionality. It wasn't until much later that the agreement was expanded to allow use on WSS and for non-Publishing scenarios in MOSS. The original activation option allows for full compatibility with the pre-expansion scenario, while the second activation allows for the answer to the next question.

The second answer has a few different facets. The first is simple consistency. You may have noticed from the screen shot that the RadEditor uses the browser's default font, rather than the SharePoint styled font. By using the RadEditor in IE as well, you get the same experience for your users, even if it isn't "perfect".

The other piece is related to the spell-check activation I advised above. Even though it is limited compared to their paid version, the RadEditor Lite has a lot of features the default SharePoint rich text editor doesn't provide. By activating the component for Internet Explorer, you gain access to all of these features. Spell checking is just one of them. Another is that its tools for inserting tables and images are much richer. Look at the comparison below of the Image insertion dialog.

First is the default SharePoint's. You can type in a URL to an image, and enter an alt tag. That's it.

image

Now look at the RadEditor's image manager:

image

Not only do you get an easy browser, including image preview, notice the "Upload Image" tab. That's right, you can upload images to your site while editing a page! Besides cross-browser editing, Image management and spell checking have been some of the biggest complaints about SharePoint wikis, and the RadEditor Lite makes them all obsolete.

Summary

The Telerik RadEditor Lite is one of the oldest free add-in components available for SharePoint. It is also a very mature product, which has gone through a number of revisions over the years. It offers a lot of functionality to SharePoint users, developers, and administrators, no matter what the browser. Not only that, its use is fully endorsed by Microsoft. (See the SharePoint and ECM Blogs.)

Who could ask for anything more in a free download?