Social rubber, meeting content management road – Alfresco / Jive Toolkit

Functional Overview, aka “What will it do?”

As announced at Gartner’s Portals, Collaboration & Content Summit this week, the integration (known as the “Jive Toolkit”) is a set of pre-built components that allows Jive to store documents in Alfresco while still offering all of the same social features as “native” Jive documents (commenting, rating, discussions, etc.). While not yet all-encompassing – Jive’s “social” content cannot yet be stored or managed within Alfresco – the Toolkit will provide a foundational level of document-centric integration, allowing implementers to focus on more use-case specific integrations as required (hence the positioning as a “toolkit”, rather than a fully fledged solution).

Sometimes technology surprises us, but this example of integration between a social platform and content management system is something we’ve been anticipating.

Incidentally, I’ve been talking about architecting for collaboration and there is a currently active discussion on my post about broken mental models in the way many people try to manage intranets.

I also noticed that this isn’t a pure CMIS based integration, which highlights opportunities for better support from social platforms to support it and also that CMIS needs to be improved to support the needs of social platforms.

Clearly, there is still a little way to go but we’re heading in the right direction.

3 thoughts on “Social rubber, meeting content management road – Alfresco / Jive Toolkit

  1. Looks like a pretty similar scenario to all the Sharepoint->Documentum bridges we’ve seen over the past few years.

  2. Yes, at this stage it is very similar. However, what’s important here is the integration of a native social business application (partly) through CMIS. For organisations using these solutions, it means they no longer need to exist outside the formal information management environment, but can expect to be integrated. The trick will not be to let the underlying EDRMS drive the architecture of the social platforms (as we will be back where we started).

  3. Yep, and that’s where the “Devil’s in the details” section hits home – with considerably different implementations of things like security models under the hood, there are still limitations given where CMIS is at. It’ll be interesting to see if the next iteration of CMIS helps to reduce (or resolve) these types of issues.At any rate, it’s great to see these types of integrations getting out there in the wild. I know of one org using Alfresco and Jive I’d like to see move on this integration 😉

Comments are closed.