Alfresco the first open-source Enterprise Content Management system?
ByI’ve recently been running a vendor assessment for an NGO (Non Government Organisation, Charity) called NetHope. They are looking to build a collaboration Intranet for all their member NGO’s (there’s currently 18 of them!) to share information and documents. Obviously, I included Alfresco in the vendor assessment, and also Plone, which is heavily supported by Oxfam who have invested heavily in the platform.
I have to admit, I hadn’t heard much about Plone before this project, and I was pretty interested to see what it could do. One of the interesting comments I saw on a few blogs and forums was a challenge to Alfresco’s claim to be the first open-source ECM system, as Plone has been around since 1999 and claims to also be an ECM system, whereas Alfresco has only been around since 2005.
After doing my assessment, I will admit Plone has many of the features you would expect from an ECM platform, it also provides a lot of great collaboration features, workflow and a multi-site web publishing system. However there is one crucial component missing: A document repository. As far as I could see from the out of the box system, there is no version control, documents are added as file page attachments, and there will be no full-text indexing of binary content uploaded to Plone (like PDF’s and Word Documents) until version 3.0. For an Enterprise Content Managment system, they’re all pretty key features that Alfresco does provide out of the box from pretty much the first version!
In addition, I have a couple of other reasons why Plone is not as “Enterprise” as Alfresco:
- Plone is written in Python, an object-oriented language which is not widely supported by industry, whereas Alfresco is written in Java, a common language used among enterprises.
- Plone runs on the Zope application server (also written in Python) which is also not common in industry as opposed to J2EE application servers that are found and supported in most organizations.
Plone has become a standard among many NGO’s worldwide for a number of years now, who have developed modules (called products in Plone) for the open source community, and as a result, it provides a lot of additional functionality, especially for collaboration, that Alfresco is still lacking. However, I think when you compare the two platforms, the core of Alfresco is definately what an ECM should have, and the other features will come with time as its very easy to extend. I would still support Alfresco’s claim to be the first open-source ECM!
I’ve been using Plone for some years now and the only drawback you may get is the python thing. It makes it difficult to find skilled plone developers because of that, while looking for SPRING developers is much more easier. You’re not right, however, when you say Plone has not full-text indexing capabilities for binary data such as PDF or DOC/PPT/XLS, etc. It’s not in the core, that’s true, but the TextIndexNG3 product does exactly what you are asking for. I’ve been using it for heavy-load web portals and works great (only in Linux though). The version control thing, yes.. there are some products but they are not quite there yet, I’m afraid. For most people (and NGOs), though, you’ll find easier to sell Plone with all the portal management stuff and multilingual support (linguaplone) than Alfresco, which has a more “framework” style, if you take my meaning. There is good news coming from Alfresco and Liferay that could make both products integrate seeminglessly and maybe fill the Alfresco’s CMS gap. So for now: – Web portals with some internal/secret/private document management and collaboration. Use Plone. – ECMs with integration with third applications and heavy use of version control and workflows. Use Alfresco.