Social Glass

We’ve been doing some work within my group to build an E2.0 (or at least a partial E2.0) collaboration system. Initially we’ve concentrated on using open source technologies for budgetary and other reasons. The solution is currently very wiki based although we’re starting to make use of Enterprise Search and Social Bookmarking.

But in doing my research on open source options, it strikes me as odd that no one has created an open source E2.0 application that integrates Mediawiki (wiki), Wordpress (blogging), bbPress (discussion), elgg (social networking) and scuttle (social bookmarking). All of these are PHP-based and open source, so integrating them would seem like an obvious thing to do.

I know that Avenue-A-Razorfish has tweaked Mediawiki to integrate more E2.0 features, but it doesn’t seem that they’ve released the fruits of their effort to the public.

The technical challenge to overcome with integration of disparate applications would be:

• Single Sign-on: Users login once and are then logged in to each application
• Integrated Tags: Each application has its own concept of tag. Tags need to be shared.
• Look and Feel: Styles and themes need to be the same across the suite to give the appearance of cohesiveness.
• I’m sure there are more…

Spikesource did something similar with Suite Two which is worth checking out if you haven’t already.
Maybe I’ll rise to the challenge, brush up on my PHP programming skills, and give it a shot.

I don’t generally write technical posts, but the geek inside me wanted to share some insights into how to “mashup” Google Enterprise Search and Social Bookmarking. Here’s what you’ll need:

• A Google Mini or Google Search Appliance
• Scuttle - an open source, delicious-like social bookmarking application
• Xalan - a Java-based, open source XSLT engine

The Value Proposition
The idea behind this is this: when a user performs a search, each of the results on the page display social bookmarking information (tags and “saved by” count) if that URL has been bookmarked by somebody within the enterprise. This helps the searcher make an more informed choice when deciding which content to look at. If somebody else inside the enterprise has found a relevant content item to be helpful then perhaps the searcher should look at it first. It also exposes the searcher to others within the enterprise who have a mutual interest in the content being looked for.

Technical Mumbo Jumbo
Out of the box the Google Search Appliance provides a great amount of flexibility in modifying how search page behaves and feels. This is done through modifying the default XSLT (which produces a UI nearly identical to google.com). So, ideally all I’d have to do to include scuttle into the search results is use the document() XSLT function invoke a scuttle API that returns XML data about the URL (including the tag list and saved by count). I could then aggregate this XML with Google results XML displaying a seamless result to the user. Unfortunately the Google Search Appliance XSLT engine does not support the document() function, so I’m left to run an external XSLT engine - hence Xalan.

So, here’s what I did:

1. Downloaded Xalan and made some minor tweaks to the “SimpleServlet” demo application (class and package name change, modified the configuration to use my XSLT and invoke the Google Search Appliance to retrieve the results in XML format).
2. Packaged the modified version of the “SimpleServlet” and deployed it on my Tomcat instance.
3. Copied the Default XSLT style sheet from the Google Search Appliance, and modified it starting at line 2398 (the XSLT template for a snippet) adding code to invoke the Scuttle API and incorporate tags and saved by count at the bottom of the snippet. Saved the XSLT and bundled it with my “SimpleServlet” war file.
4. Copied the scuttle “posts_get.php” API and made a new API that returns bookmark information for a given URL.

That’s it. Users now access my custom web application to perform enterprise searches (instead if using the default GSA frontend), but so far so good. Hopefully one day Google will support the document() function so we can do integration like this using the XSLT engine on the appliance. That would certainly make life a lot easier.

I recently pondered over the myriad applications and services Google has acquired and produced over recent months and realized that they are well positioned to dominate the Enterprise 2.0 market. The best way to illustrate is to give a simple rundown of how Google addresses the Enterprise 2.0 SLATES approach (I’m not going to argue the value of SLATES as I and others have done that before):

• Search: Google Enterprise Search
• Links: Page Rank
• Authoring: Google Apps for the Enterprise, JotSpot, Blogger, YouTube
• Tags (Social Bookmarking): Google Base
• Extensions: Adsense
• Signals: Google Reader, Feedburner

We musn’t forget Orkut, Google’s Social Networking application (Social Networking is one key element that is missing from SLATES), as this could easily be bundled into the commercial offering as well.

All of these applications are, or can be, converted for commercial use using either the cheaper SaaS model for economies of scale as Google has done with Google Apps, or packaged as a more expensive Appliance. In my experience larger companies feel better when they control their data, so the appliance option for them might be more compelling.

As a consumer, we already get single sign on to most of these applications. For example, when I sign in to GMail I can access Google Reader or Google Base without signing in again, and this cohesiveness is fundamental for user acceptance of any Enterprise 2.0 solution.

I also see a lot of potential for Adsense in the Extensions camp, where instead of promoting ads as one would do in the consumer world, companies will promote presentations, deadlines, important documents and highlight employee contributions using Adsense technology.

Enterprise YouTube could also significantly change the way people blog inside the firewall. Imagine your engineering team recording and uploading their status updates on a biweekly basis, or your boss sending you an email with a video message about his meeting in Shanghai yesterday, and having all of these video blogs stored in a searcheable repository.

As of now all Google really offers in the Enterprise 2.0 space is Enterprise Search (and I think Search is the first and most important element), and Docs and Spreadsheets (online, collaborative versions of Excel and Word). I’d bet money that Google will come to the market with a more compelling offering in the near term.

I wrote about Clearspace a few months ago and was recently given the chance to take a second look. Clearspace is made by Jive Software, a company that appeared on the horizon in 2001 and did a lot of work with Sun Microsystems at that time. They survived the economic downturn after 9/11 and have recently emerged as a leading contender in the Enterprise 2.0 arena. Enterprise Web 2 and Dion Hinchliffe have recently written positively about Jive’s offering.

Why is Jive worth a look? Clearspace is an application that provides a cohesive set of Enterprise 2.0 capabilities including blogs, wikis, tagging, social profiles and document management. By “cohesive” I mean to point out that it’s not a loosely coupled set of disparate applications. And I emphasize document management as many corporate citizens I’ve spoken to about Enterprise 2.0 note this to be a capability that is lacking in most solutions. Document management is crucial to maturing content and innovation.

Clearspace also has an impressive “reputation generation” system (which is very customizable) and I can see a lot of relevance here when trying to create incentives for contribution. Imagine attributing a dollar value to a user’s reputation when bonuses are allocated at year end.

But perhaps the greatest feature Clearspace brings to the market is its monolithic security model. Enterprises that have invested in Directory Services (such as Active Directory) can integrate these into Clearspace and properly secure content inside the application using pre-established roles and groups. From my experience security is the number one concern around Enterprise 2.0 so this is a big selling point.

Jive also realizes that Enterprise 2.0 extends beyond the firewall to external parties (i.e. business partners). They provide an intriguing mechanism for pushing content into a SaaS cloud for temporary external collaboration, then pulling the output of said activity back behind the firewall for protection.

One downside is the seat-based licensing model. Enterprise 2.0 prides itself on organic growth and adoption, and this is hindered if companies have to buy more licenses before knowledge workers can use the system.

Jive also takes a philosophical stance on social networking, saying networking for the sake of it doesn’t add much value (i.e. how much value do you get out of LinkedIn if you’re not a recruiter?) and that we should instead focus on social productivity - the collaborative benefits one gains by being connected to people (as I understand it). Personally I think social networking has benefits in its own right, especially when we think of creating networks based on groups of interest of subject matter expertise, and I think this is likely a key component to the discovery process.

Regardless, Jive is definitely worth a look!