Woody Windischman

Oct-282011

The Fractal Nature of SharePoint

The Closer You Look, the More Complex it Gets...

Over the years, there have been many analogies proposed to help people understand the sheer depth and breadth of SharePoint. Application, Platform, Pie wedges, Donuts, Layers like an onion, Shimmer ("Floor wax and a dessert topping!"). A few years ago, I used the parable of "The Blind Men and the Elephant", and that was looking at the much simpler (relatively speaking) SharePoint 2003!!

Today, SharePoint Server 2010 is orders of magnitude more comprehensive. At the most superficial level, you can look at the whole of SharePoint, and see organization and structure. The key areas are fairly easy to identify, but maybe a little fuzzy around the edges. Consider the image below, which represents the "complete" Mandelbrot Set - the classic fractal example.

Mapping this to SharePoint, you might see the large, two-lobed central area representing the Collaboration and Content Management features, the large ball to the left as social, and other balls representing Excel Services, Access Services, Search, etc...

But when you get closer, and start exploring some of the deeper capabilities, things don't get any simpler. Let's say you want to start exploring the integration of social tagging with content management, so you zoom in on the area just above the center of the image, between the two larger segments. Suddenly you open up a whole new world of options in API's, storage requirements, user interactions with news feeds and tag clouds, managed metadata and tagging external content - all in just that one small area of SharePoint functionality!

This same expansion of detail and complexity occurs virtually anywhere you look. And although every area you zoom into is clearly related to the whole, each has its own variations in the detail. This is why I am using fractals, rather than layers, to describe the depth of SharePoint. While each aspect has levels of functionality (from basic web UI to development APIs), each set of levels is slightly different. The social APIs look different from the search APIs, which are different from the publishing APIs.

That's why it is so hard to find anyone who knows "everything" about SharePoint - it can't be done. People tend to disappear into whatever rabbit hole they find most interesting. Now that doesn't mean that a single person can't know a lot about many different areas. But, you can pretty much guarantee that they don't know everything about everything. There is a very strong tendency to specialize, and even the specialists are (if they're worth their salt) constantly learning.

Oh, and just so you know, the detail image at the top of this article is about the same fraction of the image immediately above as that image is of the entire set!

Note: The fractal images in this article are derived from those in the Wikipedia article on Fractals, and used under the Creative Commons Attribution-Share Alike 2.5 Generic license. They were originally created by Wolfgang Beyer with the program Ultra Fractal 3.


Published: Oct-28-11 | 1 Comment | 0 Links to this post
Tagged as: General, SharePoint 2010

Aug-222011

Calling All People

wpe4Which Way did They Go?

One of the big attractions (and honestly, biggest fears) of SharePoint for overworked Network Administrators is its ability to delegate permissions management to site collection owners. For purposes of this article, I'm going to gloss over the details of where users are coming from. Suffice to say that they can come from Active directory, or any number of other sources. I'm also not going to talk about breaking inheritance, or anything like that. Instead, I'm going to show you where to find a very useful tool.

Generally speaking, if you have groups available, you want to use them to apply permissions in SharePoint. For example, you might put a network (Active Directory) group into one of the default SharePoint groups. Although it isn't an ideal practice, on an Intranet, it is common to apply a base level of permissions to anyone who has logged into your network:
image

Once users log in and start doing things, they leave a trail of things they have touched, and thus show up as users in SharePoint. On SharePoint 2007, you had an easy to see option to list who had actually done things on your site. This was the "All Users" view. Unfortunately, in SharePoint 2010, there is no obvious way to access this same information. In fact, there are several types of users who you can't readily see:

  • Individuals who are members of Windows groups (such as Authenticated Users above).
  • Site Collection Administrators
  • People given permissions through Web Application policies

The good news is, the information is still there. To get to it, open any group in People and Groups:

image

Then, in the URL, change the "MembershipGroupId" to zero:

image

This will result in the classic "All People" view showing up, including every user who has made updates to your site!

image

A Word of Caution

Although this view is very useful, there are probably good reasons that it was suppressed in SharePoint 2010. The most likely has to do with a classic SharePoint foible - the so-called"2000 item limit". While that is not (and never was) truly a "limit", the fact is that when lists grow to many thousands of items, rendering views can get pretty slow.

SharePoint 2010 has made great strides in working around this issue compared to SharePoint 2007, but there are still some performance constraints when rendering large lists. Given the importance of the Users list, having it locked during a large read could be "a very bad thing." In a large environment, you could have tens (or hundreds) of thousands of people accessing a singe site collection, meaning tens (or hundreds) of thousands of items in the Users list. Attempting to render an unfiltered view of "All People" in such a case could be disastrous.

So, now that you know how to find the All People view, you need to treat it like a sharp knife or a power tool. Handle with Care!


Jun-282011

SharePoint Day at Microsoft

Just a quick note to let you know that Office and SharePoint 2010 Service Pack 1 is now available. See my previous article about SP1 for more details...​

In other SharePoint news, Office 365, the 2010 based version of SharePoint Online (aka BPOS), has also been released.


Jun-202011

Still Certifiable

wpe4On Making Productive Use of Down Time

One of the facts of life in consulting is that occasionally you will have gaps between engagements. I'm in one of those gaps right now. So, while I'm looking for that next contract, I decided I would also fill out my portfolio a bit. I've been certified on the IT Pro side of SharePoint for a long time, but never got around to taking the development certification exams. Those who know me know I'm not a "hard core" developer who lives in Visual Studio, so I don't have the whole API memorized. That doesn't mean I can't code when I have to (See my rewrite of the CodePlex SharePoint 2007 Org Chart web part). I just spend a lot more time in the Architecture and IT Pro space.

In any case, since the dev exams will be required should I ever decide to attempt the SharePoint MCM, I decided to get it over with. Last week, I walked in and took what is nominally the "second" development exam "70-576: PRO: Designing and Developing SharePoint 2010 Apps" cold (without any preparation). As I expected, I passed. This morning, after taking a little time last week to review the API subjects covered, I took and passed the TS exam "70-573: TS: Microsoft SharePoint 2010, Application Development". Again, I'm pleased to say that I passed the exam.

Once my transcript is finalized, I will be able to add to the certification logo at the bottom of my site: "MCPD: SharePoint Developer 2010".

That's one more notch in the belt, and one big step closer to MCM.

And now, back to the search for my next engagement...