This is Part 3 of the SharePoint Staff Vacation Planner – DIY Guide

So having set up our basic SharePoint list with filtered views, and our “Wall Chart” dashboard, using SharePoint Planner webpart, we are now ready to get up our “Staff Absences to date” and “My Absences” dashboards.  This is the bit that allows managers to monitor the amount of absence each of their team members has had:

Or for individual staff members to monitor their own absences:

For this part of the process you are going to need SharePoint PivotPoint webpart.

If you don’t have PivotPoint already you can download the free trial version and view the installation instructions.

So we need to set up 2 webparts, and you will need to give some thought to where you are going to put them.  “My Absences” is intended to be visible to anyone, so that could go on your main team page, or your HR home page.  “Absences to Date” however is only meant for managers, so you will need to place it in a location where only your managers have viewing permissions.

The webpart setup is very simple.  Let’s start with “Absences to Date” add the webpart to your chosen page in the same way as we did in part 2.

Now “edit shared webpart”.  What PivotPoint is going to do is add all the absences, of each type, that each of your staff members has had in the current year*, then pesent this information to you, in a table which will be automatically updated every time some has more time off approved.

In the webpart configuration tool tell PivotPoint to get its data from the Staff Absence Planner List and the Approved Absences view.

For the columns of our table we want the Reason field from our list, and for the Rows we want the Requested By field.  We will have Totals on both columns and rows.  Our values will come from the #Days Absence field and the Calculation we want to perform is a simple Sum.

For the set up of the “My Absences” webpart, everything is the same other than the view you want to watch, which is My Absences.  There is also little point having totals on the columns for this one.

So, now we are finished, apart from one little glitch, which is how to handle “this year”

*Clearly for this dashboard we only want to be displaying absences in the current absence year.  Now luckily, you don’t actually need to sort this out right now, you have until the end of your current year to think about how you handle it, but it’s going to need doing sooner or later so best to give it some thought now.

There are two methods you could use for ensuring these dashboards are only showing data from the current year.  The first is to set up a filter on the list, so that PivotPoint only looks at list events for the current year.

The second possible method is to set the system up as a site template, and create a new site for each year.

Either one may work for you, and you have a little while to decide which method suits you best.

Next installment – set up a simple Absence approval workflow with SharePoint Reminder webpart.

Related posts:

1. SharePoint Staff Vacation Planner – DIY Guide part 2 – set up a “Wall Chart” Dashboard Create a SharePoint Staff Vacation and Absence Planner Wall Chart...
2. SharePoint Staff Vacation Planner – DIY Guide – Part 1 Create a SharePoint staff vacation Planning system with Pentalogic Planner...
3. SharePoint Staff Vacation Planner – DIY Guide part 5 – the system in action and Out of the box options. See the SharePoint Staff Vacation Planner system in action with...

In SharePoint 2007 there is a well known trick for opening up a list’s forms (New/View/Edit) in design mode – append ?ToolpaneView=2 onto the url – this is often used to add instructions or javascript using a Content Editor Web Part (CEWP) e.g.

• Showing a records ID on the View and Edit forms
• Setting a default duration for new SharePoint calendar events

However when I first tried to use my tried and tested shortcut in SharePoint 2010 I came a little unstuck as now the New/View/Edit forms appear in a fake popup window and modifying the URL doesn’t work.

There are two ways to do this in SharePoint 2010 – and once you know where to find them they should actually make life that little bit easier.

The first is to open up the form in a new window and then add ToolpaneView=2 onto the end of the URL, so

Right click on Add new Item or the lists Title field and select Open in New Tab or hold down CTRL while left clicking.

Alternatively you can do this using the new-fangled ribbon toolbar – select under List Tools the List tab, then on the right hand side of the ribbon you should see an icon for Form Web Parts which gives a menu of the different forms associated with the list that you can edit.

Related posts:

1. Showing the records ID on the View and Edit forms ID’s are a convenient, often short, way to uniquely...
2. Setting a default duration for new SharePoint Calender Events Post provides javascript for setting a default duration for SharePoint...
3. SharePoint List Superpowers Lists are at the heart of SharePoint and we can...

Last year, when I first started having dealings with SharePoint, I was mightily confused by all this “MOSS”, “WSS”, “SPS” -stuff.   What did all these acronyms stand for? What was the difference between all these different versions of SharePoint? And did it really matter?

Well, one year on and I’m slightly less confused, but only slightly!  So I thought it might be useful, for me and for anyone else out there who suffers similar confusion, to list out the different versions of SharePoint, their usual acronyms and key distinguishing features – I hope it helps:

So, in the begining, back in 2001, SharePoint emerged as two distinct products.  SharePoint Team Services was a bottom up team collaboration product, SharePoint Portal Server was a top down, portal, search and document management product.

By 2003 Microsoft had gathered that although customers liked both products what they would really like was the capabilities of both, combined.  So in 2003 what most of us would recognise as SharePoint: collaboration, search, content management and portal capabilities all under one roof – was born.

WSS was the basic version, free with Windows Server OS. SPS, the premium version, built on the foundations of WSS, incorporating extra functionality primarily around the areas of search and document management. Jason Masterman and Ted Pattison writing in MSDN Magazine put it quite neatly:

In essence, WSS gives you a place to put all your content while SPS provides the means to navigate and search through your content when you need it.

In 2007 much the same formula was followed, with Windows SharePoint services as the free version for windows server users and Microsoft Office SharePoint Services the premium version.  The MOSS designation references the greater level of integration with the Office suite.

In SharePoint 2010 it’s all change again and Microsoft have dropped references to both Office and Windows, leaving SharePoint to stand alone in 3 basic flavours: foundation, the free version, Standard – the premium version, which adds lots of functionality primarily around the area of search, and Enterprise – super premium, where the extras are pricipally in the area of content management.

This is very much a whistle stop tour, not an attempt to give an all encompassing overview of what is in each of the many SharePoint versions we have seen over the years – but we hope it might help you to at least get the acronyms straight!

Related posts:

1. New for 2010 – Premium Support We like to think that the standard support we...
2. We’re now a Microsoft Certified Partner – with Software that “Works with Windows Server 2008″ SharePoint webpart specialists Pentalogic Technology have achieved Microsoft Certified Partner...
3. SharePoint 2010 Ready – PHEW! Well, OK so it probably hasn’t been quite as...

Last week we had an email from a customer who was confused about his options for SharePoint 2010. He was planning to move his 5 WSS site across to SharePoint 2010 Foundation – but had found this document from Microsoft:

http://sharepoint.microsoft.com/en-us/buy/Pages/Licensing-Details.aspx

which seems to suggest that sites and Workspaces were not available in Foundation, only in SharePoint 2010 standard edition or above.  Well we knew this wasn’t right;  but that wasn’t what the info from Microsoft seemed to be saying.

This gave us a reminder of just how confusing our friends at Microsoft can make things.  So we thought we would gather together some handy resources for all of you who may be thinking of moving over to SharePoint 2010. As always we have focussed mainly on users and administrators.  I hope you find it useful.

First a proper list of features for the different SharePoint 2010 versions:

http://sharepoint.microsoft.com/en-us/buy/Pages/Editions-Comparison.aspx

If you want to download the free SharePoint 2010 Foundation version here’s the link:

http://www.microsoft.com/downloads/details.aspx?FamilyID=49c79a8a-4612-4e7d-a0b4-3bb429b46595&displaylang=en

Or for the 180 day free trials of the paid versions of SharePoint 2010 try this one:

http://sharepoint.microsoft.com/businessproductivity/products/pages/try-it.aspx?bannerId=2#fbid=xIIGCkpQnQK

For a Virtual Hard Drive, pre-configured with everything you need to get a trial up and running quickly try this:

http://www.microsoft.com/downloads/details.aspx?familyid=751FA0D1-356C-4002-9C60-D539896C66CE&displaylang=en

Then take a look at the walk through guide:

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=8c619bef-008b-4af2-9687-8a05848fea97

Take a look at Microsoft’s SP 2010 end user training materials here:

http://sharepoint.microsoft.com/en-us/resources/Pages/End-User-Training-Guide.aspx

Online training sessions on installing, upgrading, branding and social media coming up in June 2010, from SharePoint 911 – $99 per session.

http://www.sharepoint911.com/training/Pages/2010Training.aspx

Basic free end user training videos from point8020.  These aren’t really highlighting differences between 2010 and earlier SP versions, but they are all done in 2010 and there are lots of them, so could be good for the new user:

http://www.point8020.com/SharePointEndUserTraining.aspx

On the books front, Amazon already has an impressive list. You can get SharePoint 2010 for Dummies on paper or Kindle (I do like my “Dummies” books !)

http://www.amazon.com/SharePoint-2010-Dummies-Vanessa-Williams/dp/0470476435/ref=sr_1_2?ie=UTF8&s=books&qid=1274957537&sr=1-2

or “Professional SharePoint 2010 Administration” in the generally reliable Wrox series:

http://www.amazon.com/Professional-SharePoint-2010-Administration-Klindt/dp/0470533331/ref=sr_1_3?ie=UTF8&s=books&qid=1274957537&sr=1-3

And in the same series “Professional Workflow 4 in SharePoint 2010″:

http://www.amazon.com/Professional-Workflow-SharePoint-2010-Solutions/dp/0470617888/ref=sr_1_13?ie=UTF8&s=books&qid=1274959947&sr=1-13

“Building the SharePoint 2010 user Experience” from Apress also looks interesting for anyone who is a SharePoint champion within their organization:

http://www.amazon.com/Building-SharePoint-2010-User-Experience/dp/1430227753/ref=sr_1_11?ie=UTF8&s=books&qid=1274957537&sr=1-11

There are lots more books out there, but mostly aimed at developers or focussed on specific features like BCS.

If you’re a developer you might want to take a look at these:

And then finally the most valuable SharePoint 2010 resource of all is clearly our own fabulous range of Pentalogic webparts for SharePoint, which are all 2010 ready!

Sorry, I just couldn’t help myself!

Related posts:

1. SharePoint 2010: What’s Hot and What’s Not – #3 Social Networking This is the final part in our occasional series...
2. SharePoint 2010 gets into the Groove With all the furore surrounding the business release of...
3. SharePoint 2010: What’s Hot and What’s Not for End Users — #1: Hot Along with many others in our part of the...

With all the furore surrounding the business release of SharePoint 2010 it would have been easy to miss the launch (or relaunch) of another little Microsoft product in the SharePoint space which quite neatly addresses some of my personal SharePoint bug bears.

Wonderful though SharePoint is there are always a few things we wish it would do better.  Personally I have always been a little frustrated by the limitations on sharing with people outside of your own organization, the difficulties around working off-line and with the difficulties of moving documents from your PC and other applications, into, and out of SharePoint.

I collaborate a lot with people outside of the organization, dealing with designers, writers and partners, often on an ad hoc basis.  Getting things set up to share SharePoint content with someone who you may only be working with on one project, for a few days or weeks, can be a real pain.  I have to admit to resorting to Google Docs from time to time.

I am lucky enough to have a lot of flexibility in where and when I work. But SharePoint puts limits on this.  Although “cloud computing” is definately the flavor of the month – if not the year – anyone who has tried to access the “cloud” from a plane, a train or even a remote part of the country will know just what I’m talking about.

Then there is the whole businesses of getting content from other applications into and out of SharePoint.  I’m a drag and drop girl myself and anything that requires more effort just puts my hackles up.  So I end up with a stack of documents on my desktop, waiting for me to find a moment to save them to SharePoint – and as you can imagine, quite often that “spare moment” just never arrives.

So I was really pleased when I noticed that Microsoft have now relaunched Groove as SharePoint Workspace 2010 – which seems to address both of my problems.

When Microsoft bought Groove back in 2005 many people wondered what they were up to – did they want Groove or did they really want its creator Ray Ozzie?  Well they got both, and Groove has now been relaunched as SharePoint Workspace 2010 and now seems to make much more sense.

Microsoft say that Workspace will be easier to deploy than Groove and will offer organizations the opportunity to “provide a more consistent enterprise information strategy based on SharePoint technology.”

For those of us on the coal face it addresses the issues of ad-hoc collaboration, working on and off line, and moving content between SharePoint and desktop applications with drag and drop quite neatly.

Workspace might present real competition for companies like Colligio who’s products address these issues within SharePoint.

But Colligio and similar companies should probably not panic just yet, as sadly it seems that it’s going to be quite difficult for us mere mortals to actually buy SharePoint Workspace 2010.  Workspace isn’t part of the 17 different versions of SP 2010, you can’t buy it as a stand alone product, the only way you can get it is as part of Microsoft Office Pro +, which can only be purchased through volume licensing, so is only really going to be accessible to large corpoarates.

Come on Microsoft – give us a break! SharePoint Workspace 2010 looks really useful – can we buy it please?

Related posts:

1. SharePoint 2010: What’s Hot and What’s Not – #3 Social Networking This is the final part in our occasional series...
2. SharePoint 2010 What’s Hot and What’s Not? #2 NOT! So here we are with the second installment in...
3. SharePoint 2010: What’s Hot and What’s Not for End Users — #1: Hot Along with many others in our part of the...

Well, OK so it probably hasn’t been quite as much effort as climbing Everest – but sometimes it’s felt that way! Last week Microsoft made the “final” release version of SharePoint 2010 available to developers and large corporates.  So we have been able to get on with our “final” set of compatibility tests and we can now announce that all of our products are SharePoint 2010 Compatible.

When you make software that works on a particular platform – whether it’s Windows, SharePoint, or the iPhone – the introduction of a major new version is really exciting, but it can also be very stressful. The introduction of a new feature might open up lots of new possibilities, but it could equally well present new problems for the way your own software works with the platform, or even make your application completely redundant.

So as you can imagine we were all over the public beta version of SP2010 as soon as it became available last November. We were very pleased to see that whilst there are lots of fantastic new features in SharePoint 2010 Microsoft haven’t introduced anything within the Out of the Box functionality that undermines our own products. For users of SharePoint 2010 our PivotPoint, Planner and Reminder will continue to add valuable planning, reporting and alert functionality to the Out of the Box offering, and we have also spotted some interesting new possibilities for product development.

Over the past few months we have carried out extensive in house and third party testing on all of our products in the beta version of SP 2010. There are some significant changes in this latest version of SharePoint and we have been busy making sure that our products function properly with these changes.

But we know from past experience that there can be significant differences between the beta version of any piece of software and the final release candidate – that’s what a beta is for after all.  so we know we wouldn’t be finished until we saw the final release candidate – and last week we got it and were able to run our final set of tests.

So we can now say, with confidence “Yes, we are SharePoint 2010 ready.” SharePoint 2010 versions of all of our products are available to download from the website for existing customers who are upgrading to 2010 or new customers who are running or trialling a SP2010 deployment.

Although there is a lot of excitement about SharePoint 2010 we know that many people won’t be upgrading overnight. We know 15% of our clients are still using SharePoint 2003. SharePoint 2010 only runs on 64 bit servers. This means that anyone currently running on 32 bit servers will need to upgrade their hardware before they can upgrade to SP2010. Though this would be normal practice for many large corporate, for smaller businesses on tighter budgets it introduces extra costs and could be a potential barrier to upgrades.

So whilst we are now fully SharePoint 2010 compatible, all of our products also remain compatible with all previous versions of SharePoint and we intend of continue to support all previous versions for the foreseeable future.

And now we are done with compatibility testing for the time being we can get on with some new product development – which should be much more fun!

SharePoint 2010 will be available on general release in May. There are 8 versions and as yet Microsoft have made no announcements regarding pricing.

Related posts:

1. New for 2010 – Premium Support We like to think that the standard support we...
2. SharePoint 2010: What’s Hot and What’s Not – #3 Social Networking This is the final part in our occasional series...
3. We’re now a Microsoft Certified Partner – with Software that “Works with Windows Server 2008″ SharePoint webpart specialists Pentalogic Technology have achieved Microsoft Certified Partner...

This is the final part in our occasional series on what’s hot and what’s not for the end user in SP 2010. A couple of weeks ago we focused on our favorite new feature for end users: FAST Search, which we think is going to make a huge impact on how people store and search for content in SharePoint 2010.  Last week we took at pop at Business Connectivity Services – which we feel could cause more problems than it solves. Today we are throwing stones at SharePoint 2010 Social Networking – which gets our vote for joint top turkey in terms of new features that have been heavily hyped, but in our opinion are not likely to deliver much real value for the end user. The thing with SharePoint 2010 Social Networking is that we just don’t understand why its there.  This is enterprise software – it’s not supposed to be fun, it’s supposed to help you get the job done.  Have Microsoft added these features just because “social” is so darned sexy at the moment?

Director of Collaborative Product Management Christian Finn presented at last year’s SharePoint conference and said that their goal for Social in SP 2010 was to have it be “as much about people and seem as much about people as it is about documents.”

There are three main areas to the social features in SharePoint 2010:

• Social Networking
• Social Content
• Social Feedback

So, we have a whole range of social features: profile pages that look like Facebook, blogging, status updates – like twitter, central photo sharing – like flickr, tags, notes and votes – like Digg (OK, so we admit we quite like this, but that’s because it’s going to have huge benefits in content rating outside the social domain).

OK, so if you are using SharePoint to run some sort of a club or social group – great.  But for the corporates, we just don’t see it.

Microsoft claim that the social functionality within SP2010 will allow people within the organization to “connect, share ideas and find solutions”. Well if that was what people were going to use it for great.  But in reality we all know that what people are really going to do with it is spend hours, pimping their profile page, sharing photos of their last holiday and “tweeting” about how rough Sarah in accounts looks this morning.  As an “enterprise” why would you even switch it on?

Added to that, even if people were using it to “connect, share ideas and find solutions” in a business-related way, we need to remember that that kind of creative behavior falls way outside the job description for most workers.  Those of us who have the opportunity to express some creativity in our work need to remember that we are part of a tiny, privileged minority.  For the vast majority of workers in corporations around the world the brief for the working day is not “connect, share ideas and find solutions” its “keep your head down, get on with the job, and follow the set procedures.”

If you have a good boss you might get to go out for a drink after work to connect, share some ideas and maybe solve a few problems, but the world of free-flowing ideas and intercourse envisaged by Microsoft just does not exist within the workplace of most of their clients.

Our next problem is that Social Networking outside of the enterprise is cool, sexy and on-trend, it moves really fast.  By the time Microsoft actually roll out SP2010, the social networking platforms they have modeled its social features on could well be passé. Social Networking functionality in SharePoint 2010 is always likely to be behind the curve.  Because it’s enterprise software created by one of the biggest corporations in the world and it’s never going to be able to move at the speed of a disruptive start up that goes viral, like Facebook.

And let’s face it, unless you work for someone like Google or Apple your company social network is never likely to be really “cool”.

So those corporates who use SharePoint’s social networking functionality in an effort to channel the “unstoppable force” of social networking in a corporately acceptable direction are likely to be disappointed: employers won’t be using SP2010 social at work instead of LinkedIn, Facebook and Twitter, they will be using it “as well as”.

There has been much talk of “controlling” the social buzz around your product or service by giving employees an internal social channel within which to express themselves.  My thought on this is just “Get Real!” Is the employee who has negative things to say about your product, service or personnel really likely to say them on internal “corporate twitter”?  What would be the point?  We should all know by now that you can’t “control” social.

So, we just don’t get the whole SharePoint 2010 social networking thing.  Don’t get us wrong, we love Microsoft really, we just think sometimes, like all of us, they go a bit off track – and the introduction of social networking features into SharePoint 2010 could be one of those times.

Do you agree, or do you think we are way off mark?

Related posts:

1. SharePoint 2010 What’s Hot and What’s Not? #2 NOT! So here we are with the second installment in...
2. SharePoint 2010: What’s Hot and What’s Not for End Users — #1: Hot Along with many others in our part of the...
3. SharePoint 2010 gets into the Groove With all the furore surrounding the business release of...

So here we are with the second installment in our occasional series on SharePoint 2010 features for the end user. In part 1 we looked at the new features in SharePoint 2010 that we thought would be most welcomed by end users.  Our vote went to FAST Search, because it’s going to make search within SharePoint much more like search in Google – which has to be a good thing. This provoked a lot of debate and whilst some of you agreed with us, others had different candidates for the top spot. A lot of people liked the improved UI and the introduction of the Office Ribbon, others loved the new Metadata features, tagging and voting, and others thought Records Management was going to be a winner.

But enough of all this positivity: (we are British after all: skepticism is our default setting!) this week we are looking at our pick for the #1 “turkey” feature SharePoint 2010, the feature that has been really hyped but that we believe could easily sink without a trace.

And our vote goes to . . . . well, we have a tie for top spot actually:

• Business Connectivity Services
• Social Networking

So, today we are going to talk about Business Connectivity Services, and on Monday we’ll come back to Social Networking- we wouldn’t want to bore you by gong on for hours!

So, Business Connectivity Services.  This is the successor of the Business Data Catalogue, which allowed integration of Line of Business Data into SharePoint.  It wasn’t all that well used as a feature (according to the AIIM 2009 State of the Market Report) and where it was used it was almost always used in a read-only capacity – read/write was not available out-of-the-box, and was very tricky to implement through 3^rd party applications.

BCS goes a lot further and encourages the set up of 2 way, read/write links between SharePoint and Line of Business applications.  It sounds great: you will be able to access, amend, even create data for your line of business applications from within SharePoint 2010.

Well, nice idea, but we don’t think it’s going to fly.

Two way synchronization between any two complex applications is a minefield, both politically and technically.

On the technical side, two-way synchronization is a two-way street. SharePoint 2010 may be all set up for seamless integration into your line of business applications, but things may not run so smoothly at the other end.

So Microsoft may very well be able to set up SharePoint 2010 so that they can run a search in SP2010 for “Steve Jobs”, see the receipt for the Xbox 360 Mr. Jobs just bought in the accounting system, find his customer record in Salesforce, and change the record of his address and banking details. All done from within SharePoint.  But the problems start when we try to push those changed records back into Salesforce and the accounting system.

This is really a very complex process and the potential for error is huge. There is a lot of development time involved in making sure that the two (or maybe even more) applications work correctly together.  It’s not just a one-off investment in development time either – every time there is a change, or an upgrade or a patch in either system time needs to be spent on figuring out what implications that has for the link – and making changes where needed.

Things that look really impressive in the laboratory conditions of a demo can very easily turn into a nightmare when subjected to the constantly changing environment of the real world.

The political issue is around security and governance.  Line of Business data is generally sensitive and closely guarded stuff.

The accounts department might be happy to print out (or these days maybe even email!) endless reports on what’s going on with the numbers – but do they want the rest of the business poking around inside the accounting system?  I don’t think so!

So in our scenario above, Mr. Jobs returns his Xbox, (because he’s found he gets a much better gaming experience on his new iPad) and asks for a refund.  Sales pass the request to accounts, who duly refund the money to Mr. Jobs debit card – only they don’t because the helpful soul who amended the records from within SharePoint has miss-keyed, the card number. The money goes to some random person in Guatemala, accounts have no chance of retrieving it and Mr. Jobs is fuming because he hasn’t got his refund.  The head of Accounts can’t even fire anyone, because the person who made the error isn’t in her department!

All in all we feel that BCS may fail to live up to the hype once businesses start to look at the implications of this in the the real world. From both development and governance points of view they may well decide that a BDC type read-only connection is going to be good enough – if indeed they feel the need to integrate line of business data into SharePoint at all.

The AIIM report seems to bear out our feeling.  Of those surveyed who had deployed SharePoint but then stopped using it, the two most common reasons for ceasing use were security concerns, and problems with integration into existing systems.

Do you agree with us on this one, or do you have your own #1 candidate for a SP2010 turkey?

Let us know your thoughts, and check back on Monday when we will be taking a pot shot at SP2010 Social Networking.

Related posts:

1. SharePoint 2010: What’s Hot and What’s Not – #3 Social Networking This is the final part in our occasional series...
2. SharePoint 2010: What’s Hot and What’s Not for End Users — #1: Hot Along with many others in our part of the...
3. SharePoint 2010 Ready – PHEW! Well, OK so it probably hasn’t been quite as...

Along with many others in our part of the technology industry, we’ve spent the past few months with our heads firmly buried in SharePoint 2010, getting our products compatible, and along the way getting really familiar with the wealth of new features on offer.

So as we’re now at the “been there, done that” stage with SP 2010 we thought it might be useful to share our thoughts on what the killer features are, and where to watch out for the white elephants!

This week — killer features.

There’s a lot to get the developers excited: Just do a quick Google search and you’ll come across bags of blog posts on all the great new developer features. But here we want to take a slightly different tack and focus on the features that we think will make the most difference to the end user.

Our vote goes to FAST search.

In days gone by, we used to store things electronically and search for things electronically in much the same way as we store and search in the real world. We’d store things in the appropriately labelled folder in the correct virtual “drawer” of a virtual file cabinet.  When we needed to find things electronically, we’d then be relatively happy to trawl through our virtual file cabinets until we located the item we needed.

That has all changed now. For a start, we no longer “file” electronically. For the most part we just leave our stuff in a disorganized heap with a bunch of “tags” attached. Our electronic lives look a bit like a teenager’s bedroom. And yet, despite our virtual untidiness, we expect to be able to find things at the click of a mouse. We expect logical search results ranked for relevance, maybe displayed with images or other media and delivered instantly. And on the Web we get this with Google, but we’re rarely so lucky when searching within a Web site, or worse still when searching internal corporate data.

Google’s magic relies on links to pages being like votes. Given enough votes the best content for any subject becomes apparent. But you don’t get the same high level of interlinked content inside organizations so this doesn’t work as well. Hence the scenario we’ve all faced of being unable to find that document that we know is hiding somewhere.

So, going back to our virtual teenagers bedroom, if we search for “Xbox” on Google it will most likely direct us first to the console, or the controllers or maybe our current favorite game – because those are the things that are being used most (linked to most), so Google reckons they are most likely to be what we are looking for.

If we search our virtual bedroom for “Xbox” on a corporate search it is just a likely to send us to the Xbox packaging gathering dust under the bed, or the Xbox receipt stuck in a book we gave up reading six months ago. Because – well – they both say “Xbox” on them, don’t they?

FAST search for SharePoint 2010 has the potential to change this. FAST was the Norwegian company that provided the technology behind Alltheweb and Lycos (Remember them?). Acquired by Microsoft in 2008 FAST Search for SharePoint 2010 is?? the first FAST product deployed by Microsoft, and if the integration of FAST with SharePoint delivers all that it promises it should offer the end user plenty to smile about.

There are a huge number of features we could talk about, but these are the three key things we think end users will really notice:

1. Findability. The main pitfall with much enterprise search to date has been that you just couldn’t find things. Meta data is key to findability in enterprise search and problems occur because many unstructured documents are stored with no Meta data giving the search engine very little to work on. FAST has the ability to automatically and quickly generate Meta data for unstructured documents which would mean that the user will be able to actually find what they’re looking for.
2. Relevance. We’re all used to the sheer randomness of server search results. FAST should improve things here greatly. Not only does it have advanced linguistic capabilities, but it also offers contextual search capabilities which can tailor search results to user profiles. All this offers the promise of far more relevant search results.
3. Speed. How long have we all spent looking at that little spotlight icon endlessly scanning an empty screen as we wait for our file search results to appear? In this respect FAST lives up to its name. It promises to maintain speed and performance levels on searches of 100 million documents or more which will offer a real time saving for many users.

FAST Search for SharePoint 2010 is an add-on, not part of the out-of-the-box solution, and there are those pundits who believe the OOTB search has been improved so much in SharePoint 2010 that for most deployments the investment in FAST cannot be justified.   We disagree and feel that the improvements in the end user experience will result in higher usage rates and so improved productivity.

So. FAST search is definitely on the top of our list of killer features in SharePoint 2010 – what’s on top of your list?

Related posts:

1. SharePoint 2010 What’s Hot and What’s Not? #2 NOT! So here we are with the second installment in...
2. SharePoint 2010: What’s Hot and What’s Not – #3 Social Networking This is the final part in our occasional series...
3. SharePoint 2010 gets into the Groove With all the furore surrounding the business release of...