One of the most powerful means of filtering, sorting and searching information that has emerged as part of social computing is the use of “tags” to classify content of all types.

It should not be of great surprise to anyone that Microsoft’s plan for SharePoint is to provide the foundation for access to all information in the enterprise. With SharePoint’s tightly coupled integration with the Office product, SharePoint’s popularity in collaboration and openness for developers and integrators, SharePoint is positioned to touch every single byte in your corporate network.

SharePoint 2010 comes with a bunch of web 2.0 features, tags, tag clouds, rating, social bookmarking and enhanced blogs and wikis. What I really missed in SharePoint 2007 were tags and tag clouds. On the other hand this was a free space for developers like me, see Power Tag Cloud ;-) My experience with SharePoint 2003 already showed that text, dropdowns and lookup columns are too inflexible and people tend to over categorize in the conception stage.

I had a user request to automatically fill in text to a required field based on the selection of a radio button on the page. The form that is being filled out is used by a hiring manager to document the decision process for a certain recruit. Since each position will only have one person hired, but typically more than one applying, the answer to the question: “Was this person hired?” will be “No” way more than it will be “Yes.” Therefore, a reason for the “No” is required.

One of the first things I thought, once I started to play around with jQuery, was whether we could use it to secure a SharePoint view. The answer is “no” (or at least, I’m not claiming it’s possible). However, it is certainly possible to make it difficult for people to see a particular view.

Previously, I wrote about how to use jQuery to locate and hide a text field on a form. I didn’t care for the specific approach (I was chaining parents – that’s simply isn’t done these days, at least in families of quality).

This is a pretty terrible approach I think because it’s extremely dependent on the very specific structure of this form. When SharePoint 2010 comes out, this whole structure could change and break this approach. What I really want to do is craft a jQuery selector that is along the lines of “find me all the TR’s (and only TR tags) that have somewhere in their child elements an input field whose title = Hide Me!”. I starting from the bottom and moving up. Assuming I figure this out, I’ll post an updated “quick and easy’ post

One of the most frequently overlooked capabilities of SharePoint 2007 is its automatic creation of efficient, mobile views. This is a powerful capability that people often find surprising. The SharePoint mobile view allows you, and your users, to gain access to the SharePoint list information contained on your site. I will show you how create and use your own Microsoft Tag to easily load your mobile SharePoint 2007 site on your Smartphone. The use of a Microsoft Tag to get to your mobile SharePoint site, or any other mobile site for that matter