Speaking of India..Spelling names right

I recently happened to browse through Craig Storti's Speaking of India:Bridging the Communication Gap When Working With Indians and while I must applaud Craig for his attempt to explain the difference between Indians and Westerners and how they perceive each other, he appeared to have missed out one key point that is Westerners don't always catch and Indians never let go off and that is 'Spelling names right'.

In the book, Craig quotes the CEO of Infosys, one of India's largest, globally recognised software power house as follows
"India has always been seen as a country of promise and potential,” notes Mamdan Nilekani, CEO of Infosys"

All good in the above sentence except Mamdan is actually spelt Nandan. A big blooper and not the best way to put your foot forward in India or in any country for that matter. Yup, when it comes to communication. Indians are as touchy as the rest of the world.

Connecting Infomation Dumps

I work for a traditional management consulting firm which is just beginning to embrace Web2.0 and its principles of blogging and Wikis. Today was a momentous day in the sense that I was involved setting up the corporate Wiki space where we (or rather projects) could create pages and collaborate using the functionality offered by the Wiki. Some of the managers I discussed the Wiki with, were skeptical about using the Wiki to blog about projects, upload documents and collaborate. The reason for their lack of enthusiasm was the presence of other traditional collaboration tools that have been used by previous projects to maintain project documents and track progress and there was not one but several such tools. As a result, there were several silos of information that were isolated and to a certain extent unusable as not everyone knew about their existence.

Reality check time.Information will continue to exist on File Servers, Email folders, Intranets, Wikis, Content Management Systems and local file systems . A good part of this data will be duplicated, redundant and even in some cases, out-dated. How does one connect these different sources and make data usable and easily manageable. Google Enterprise piggybacking on a Google search appliance can make finding information inside an organization easier but a search solution is not the key. The key is manageability.

While moving information out of every source into a central repository and forcing the workforce to use the central source is out of the question, it brings to the fore front, the need for pluggable interfaces that can connect information across these silos based on content and more importantly update information across several sources when information in one source changed is the need of the hour.

Such a system while in essence would be a Content Management System (CMS) that would manage content held by other CMSs, File Servers and other similar sources, it would need to identify and group together 'similar' data. In such a scenario, Tagging could act as a glue between these disparate sources of data. Moving one step forward, a bookmarking software such as Scuttle could be used to tie in various sources and formats of 'similar' data.

Lucene.. still needs Google?

While reading up on Lucene, which is advertised as a 'high performance, scalable,powerful and accurate' search engine , I noticed that the search function available on the hosting Apache site was 'Search this site with Google'. Wouldn't a search want to use itself for the very purpose it existed??

Needless to say, it doesn't inspire much confidence in all those who want to use it. Watch this space for more.