content management

Delivering Portal and CMS as Service Part 2

Tenant Specific Content Okay the next issue to be aware of is about how actually the content is stored. So let's for the sake of simplicity assume the content is a "News Article" with fields like Headline, Byline and Body. A very good article on issues related to multi tenant data architecture is here.

EMC to acquire Document Sciences Corp

I have said before that ECM vendors should provide Document Composition features as this space is very closely related to content management. The folks at EMC seem to agree. EMC ended the year with the news of acquiring Document

Discussion on Standards at cmf2007

So I'm speaking at the very nice cmf2007 conference at Aarhus on Wednesday, November 7th. I'm actually delighted to be joined by Jukka Zitting and Steve Millidge. Jukka's on the expert group for JSRs 170 and 283 while Steve's on the expert group for JSRs

Standards in Content Technologies: Should you care?

Recently, there have been many discussions in the blogosphere regarding standards (or rather lack thereof) in the ECM space. Are standards useful? Or are they just a set of buzzwords used to get tick marks in RFPs and analyst reports? Should you prefer standards over proprietary features? I'll be speaking on this topic at

Standards and Content LifeCycle

For a lot of organizations, the content lifecycle includes much more than what typical ECM systems have to offer. Consider this scenario of an insurance company that offers different insurance products (life, auto etc) to their customers. People go to the website, compare products and select the one that they want to buy. They then enter their details etc which is fed to the backend systems where

What's in a name?

Quite a bit! Shishank Mathur has posted a list of some product names in the Portals and Content Management space and his interpretation of what the name means. Many of these products though have clearly evolved and the names do not reflect their current functionality. A quick peek in the history shows how Documentum has evolved from an EDMS to ECM - Here's

Goodbye 2006, Welcome 2007

2006 has been an exciting year for content technologies. Based on some of the interesting happenings, the following themes (in no particular order) have emerged that might have an impact on this space in coming years:

  1. Standards: or the lack of them was evident. Although portal standards (JSR-168, JSR-286)

What data should a CMS manage?

There are often cases when a website or portal needs to display content generated internally in the CMS along with content generated externally. Examples include showing news feeds from 3rd party content providers or displaying content from other applications like a CRM. So the question often asked is - Should this external content first get into the CMS and then delivered by the site OR should

Document Composition and ECM

Document Composition, as the name suggests is dynamic assembly of documents based on business rules and templates. Examples include creating insurance policies, credit card communications, customized investment advice, bill presentment and so on. Many of our clients, especially in the BFSI space have been asking for document compositions solutions. Most ECM solutions do not have document

Web Content Management for multilingual sites

I attended a Summit on Internationalisation, organized by W3C Indian Office. The conference focused on issues specific to Indian market and some of the solutions to these issues. Richard Ishida, the Internationalization Activity

XML feed