Thursday, November 18, 2010

Moss Site usages report

Moss Site usages report explained

This paper gives detailed descriptions of parameters displayed in MOSS 2007’s usage reports.
Since very similar reports exist at both the Site and Site Collection level, descriptions will be combined when applicable.  The phrase “site/collection” will be used to indicate either site or site collection, depending on which level the report was requested at.
Performance tip: the default page for usage reporting demands the most of SQL Server because it has the most reporting parts; each part executes at least one stored procedure to retrieve its data.  Each part is also found on other reporting pages.  It may be desirable to bookmark specific pages for detailed reports, it the summary report is not desired.  This will prevent the intensive processing required to summarize all reports if all that is wanted are details.
Note, when a description says “over the past 30 days” or “divided by 30” the underlying calculations always account for the possibility that usage reporting may have been turned on less than 30 days ago, and fewer than 30 days worth of records exist.  In these cases, the appropriate number less than 30 is used.
In all calculations, “Requests” means a request for a single page, and does not include any of the items that appear on the page that may require additional HTTP requests to the server.  In other words, a Request is equivalent to what is commonly called a Page View.  Statistics for intra-page requests such as graphics, scripts and style sheets are not collected for SharePoint usage reporting.
“Distinct” users are the same as “Unique” users.  Each is computed via the SQL operator DISTINCT when selecting over all users.
Show hidden text for underlying technical specifications.

Average requests per day over past 30 days: average = total number of requests over past 30 days, divided by 30 to give daily average.
Distinct users over past 30 days: total number of users accessing this site/collection over the past 30 days, not including repeat visits from the same user.
Distinct users yesterday: total number of users accessing this site/collection on yesterday’s date, not including repeat visits from the same user.
Requests yesterday: total number of requests to this site/collection on yesterday’s date.
Queries Yesterday: total number of search queries submitted by all users from this site/collection on yesterday’s date.
Queries Over Past 30 Days: total number of search queries submitted by all users from this site/collection over the past 30 days.

Top Pages (Average requests per day over past 30 days)
Table
Page: URL of requested page
Value (decimal): average = total number of requests for this page over the past 30 days, divided by 30 to give daily average.

Top Users (Average requests per day over past 30 days)
Table
User: ID of user accessing this site/collection.
Value (integer): average = total number of requests from the user to this site/collection over the past 30 days, divided by 30 to give daily average.

Top referring pages (past 30 days)
Pie Chart
URL: page that any user visited just prior to browsing to a page in the current site collection.  The top 5 URLs are shown.
Slice-value (integer): total number of times this URL was a referring page over the past 30 days.


Tuesday, October 26, 2010

What's in a SharePoint Managed Path?

What's in a SharePoint Managed Path?

I often hear and sense confusion about SharePoint managed paths. Managed paths are essentially 'mount points' for site collections.There are two types of managed paths - Explicit and Wildcard.

What's the difference between an explicit managed path and a Wildcard managed path?

By default, the root ‘/’ managed path is explicit, meaning only one site collection can be in it and it assumes the identity of the managed path. That's how you browse to http://webapp.fqdn.msft and get a Web page. A Web application without a site collection in the root managed path will return a 404 error when browsing to the root. You could always create another explicit managed path for multiple portal support in a Web application, i.e. http://webapp.fqdn.msft/HR. HR is a peer to '/'. Now, you can no longer have an HR sub-site in the root - you will get a security validation error because the URL space is already taken.

A Wildcard managed path is basically 180 degrees in the opposite direction. A Wildcard managed path can support hundreds or thousands of site collections, but they are appended to the managed path, like http://webapp.fqdn.msft/sites/team, with sites being the Wildcard managed path. It will always return a 404 error when browsing directly to a Wildcard managed path. But, you can create many Wildcard MPs like teams or projects.  Wildcard managed paths are like a sorting mechanism for site collections.

I hope this helps your Web application structure and design.

Wednesday, October 6, 2010

Share Point Designer

Share Point Designer – A definite Maybe

SharePoint Designer does have some great qualities that at first glance get you really excited about using it. I could make some analogy here likening SharePoint Designer to an attractive girl you meet at a bar and before you know it you wake up in a bathtub full of ice missing a kidney, but I’ll refrain. So, what’s good about

Don’t have to develop on a the server

Probably the most awesome thing about SharePoint Designer is that you don’t have to develop on the freaking server! This is phenomenal for those developers who have to get SOMETHING done and they don’t have access to the necessary development tools. This was my ONLY option for development for the first 6 months that we were using and learning about SharePoint. You do however need to be a site owner on the site in question.

Modifying ASPX files, Master Pages, and CSS

SharePoint Designer is great for modifying and maintaining your ASPX pages, Master Pages, and Cascading Style Sheets. It especially is useful in browsing through and learning SharePoint’s massive CSS files. SharePoint Designer has a pretty good WYSIWYG editor (What You See Is What You Get) as well which can really help when designing and creating themes.

Prototyping

SharePoint Designer is great for throwing together a quick Prototype on your development servers and getting it in front of people to build some excitement about SharePoint and show what SharePoint is capable of.

SharePoint Designer Workflows

The second best thing about SharePoint Designer are the SharePoint Designer Workflows. SharePoint Designer comes with quite a few workflows that can be connected to a SharePoint List and can be set up to be executed manually, when an item is created, or when an item is changed. Some of things you can easily do with these workflows are:
  • Send emails, including emails to individuals who created a list item or executed the workflow
  • Do simple business calculations and store those values in your lists
  • Create lists
  • Update lists

Thursday, August 19, 2010

Intranet Governance


Who should own the intranet? Communications? IT? HR? All of them?

You may be shocked to learn that many companies don’t know the answer; in fact, many organizations can’t clearly answer with any confidence whom is the present intranet owner.

Gone are the days where a single IT geek creates an intranet on a server under his desk, and manages the whole kit-and-kaboodle (at least in a real business  environment that doesn’t feature the cast of Dilbert). Also in retreat, facing extinction (where budget permits) is the ‘wild west’ intranet: anyone can do whatever they want, and they do.

As is the case with most intranet it is simply impossible to achieve any long-lasting success without a clearly defined ownership and management structure. Far from being a buzz word or jargon, intranet governance provides clarity and rules: namely the titles, roles and responsibilities of its owners, managers, stakeholders and contributors.

Simply put, governance defines an intranet’s ownership and management model and structure including the:

  • Management team
  • Roles & responsibilities of contributors
  • Decision making process
  • Policies & standards

Like the content of your website or intranet, planning and governance is technology agnostic; whether it’s SharePoint, IBM or another portal or content management system, the necessity for and the approach to governance is the same. Given its technology neutral status in governance is largely applicable to any technology platform.

POLITICS

Politics and the issues of control, ownership and standards go hand-in-hand with intranet management and perhaps these issues, more than any other, have driven the requirement for planning and defined governance models. Sadly, very few organizations actually have a well-defined governance model, and many of those have spent hundreds-of-thousands to millions of dollars on their website or intranet – amounting to extraordinary investments left to chance and execution on a whim.

According to the Intranet 2.0 Global Survey in 2009:


  • Only 47% of organizations has a defined governance model (32% have 6,000 employees or more; 11% have 30,000 employees or more)
  • Of the tools and platforms being used by survey participants, a whopping 47% are using SharePoint (MOSS 2007) in some shape or form.
By 2011, according to the Social Intranet Study, the picture had improved considerably: 67% of organizations have some form of governance, and at minimum, some form of policy that regulates intranet content publishing and management. A marked improvement for certain, but still many lack a well-defined governance model that explicitly details the ownership structure and policies required to support and govern a leading intranet.

Most importantly, a thorough governance model will help inoculate your intranet against the number one killer: politics.

Politics will kill your intranet. Without a well defined governance model (and should your intranet survive the naturally occurring politics of competing priorities amongst various stakeholders – communications, IT, human resources, various business units, etc.) then the value the intranet or portal delivers will be severely hampered.

OWNERSHIP

“If you don’t have structure, you’re going to constantly run into politics,” said Sonia Chouhan, ex-Webmaster  of  LM Wind Power. “Without a governance structure with standards, different silos try to do something in parallel (their own thing) and it costs more… and will lessen the user experience.”

Much of the problem lies in the immaturity of this nascent intranet technology. With the rational consolidation of intranet sites and services under a central site or portal, disparate departments and stakeholders such as corporate communications, human resources, IT and varying business units now must cooperate under a lone umbrella with a single intranet home page. Along with this ‘forced’ cooperation comes the predictable politics and competition for ownership of the intranet (and competition for valued home page real estate).

The problem lies with the traditional growth and evolution of the intranet. Initially, when intranets first came online in the early to mid-1990s, they were nothing more than a web brochure (a.k.a. ‘brochureware’) that sat on a small server under the desk of a Web developer who served as designer, writer and Webmaster.

GOVERNANCE MODELS

I categorize intranet governance by four broad approaches or models:

  • Decentralized (no single owner; do-what-you-like)
  • Centralized a single owner or department controls it all; highly bureaucratic; common in small organizations)
  • Collaborative (shared ownership via committee)
  • Hybrid, centralized (single owner, with collaborative accountability, decentralized content ownership)

COLLABORATIVE GOVERNANCE


The most common governance model in recent years, in medium to large-size organizations, has been the collaborative model. The collaborative model is most often focused on a cross-representative steering committee representing the major functional stakeholders:

  • Communications
  • Human Resources
  • Operations
  • Information Technology
  • Business units / departments

This model is most successful when the committee is championed by one or two key executives, often the CIO, the head of Communications, or HR. Instead of no owner, or one single owner, a collaborative team governs the intranet through the application of policies, standards and templates. This committee is typically responsible for the direction, vision, prioritization of projects, and future evolution.
About two-thirds of medium to large-size organizations have some form of collaborative governance and some form of intranet ‘steering committee’ or council. They typical committee has 6-10 individuals (mostly from IT, HR & communications) and is focused on:

  • Mandate and vision
  • Business objectives
  • Policies and standardization
  • Project prioritization
  • Trouble-shooting and conflict resolution

HYBRID, CENTRALIZED GOVERNANCE


The hybrid, centralized governance model is one that combines elements of all three previous models:

  • Centralized ownership
  • Centralized policy making and future development decision-making
  • Centralized technology and content management platforms
  • Decentralized content publishing and ownership
  • Decentralized application ownership / management
The hybrid model is very closely aligned to the collaborative model, with two significant exceptions: there is often a supporting steering committee, but it falls under a single intranet owner (or co-owners); and the role of IT is usually reduced from a collaborative owner to a committee member without ownership, but rather a support or enabler role for the business owner (often communications or HR). So while the collaborative model has a committee as the end intranet owner, the hybrid model puts the committee under an owner (though sometimes this business owner is in fact IT).

Tuesday, May 25, 2010

SharePoint 2010 – Remove save, cancel and top next buttons survey

To remove the save, cancel and the top next button from a survey, just put in this code in the NewForm.aspx and EditForm.aspx (easiest done by SharePoint Designer). Depending on which language your are running SharePoint, you have to change the value of the buttons in the script.