Thoughts on Structured/Unstructured and Shared Information Management using Wiki and other emerging technologies
Friday, June 20, 2003

A nice resource for combining Wikis and Weblogs:

Thursday, June 12, 2003

I keep talking about Structured editing in twiki. Let me give more information about it.

By structured data, I mean typical tables, trees and so on. However, there is more to what I have in mind:

A render of a table in HTML will require different information contents. Wikis make it possible to edit these contents easily. First, let me list different contents:

The challenge is to enable wiki environments to create organizational schema and extend it on continuous basis. For a smaller organization, we shouldn't require a separate database.
And when performance becomes an issue, the database should be in shadow i.e. no user intervention should be required in managing the database schema. It should be reflective of the schema specified in wiki environment.

Wiki environment will make it simple to manage information in distributed manner. For example, a table that can be specified in a topic may have INCLUDEs that come from other topics. So if you consider a user table, different sets of users are managed in different topics (probably under relevant group), and yet, you can have a centralized user table by appropriate INCLUDEs.

And you require capability to include columns as well. Let me give an example: In one topic, I may maintain user-id, user-name, email, phone-no. In another topic, which is maintained by some other people, they want to create a table with user-id, name, email, project name, role-in-project, and so on (i.e. project specific details.) And only a subset of users may be defined (only those belonging to the project.). This task is part of schema management. Topics can define and extend the schema, and make them available to other topics that will let the table be managed by INCLUDEing the topic schemas.

Advantages with respect to databases are many. Traditionally, the schemas are managed by applications, and databases are used underneath. And you can't easily generate new views and reports. Some specialized applications do provide such capability. But they all require that a database be used and managed. And this requires administrators for that purpose. Wiki environments push this functionality down to users. As a lead for small group in a big organization, I should be able to extend the organizational schema for my purposes. Wikis will allow us to do precisely this.

I have tried to experiment these ideas in twiki, using a modified Pollplugin, and Template toolkit. Only user specific information could be collected (i.e. each row has user-id as its key field.) But that is just a starting point; and a lot of things need to be understood and implemented.

About this blog
All realms of collaboration:
  • Wiki. Weblogs
  • New Integration Platforms for combined structured and unstructured information: Wiki, Portals, Email Clients,
  • Collaborative Document editing, Collaborative knowledge building
  • Email Interfaces to collaborative shares
  • Information organization, management, Publishing: In context of organizations, individuals, Opensource projects etc.
About me:
Name:Vinod Kulkarni

Subscribe to Bloglines


January 2003
February 2003
March 2003
April 2003
May 2003
June 2003
July 2003
September 2003
November 2003
December 2003
January 2004
February 2004
March 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
May 2005
June 2005
November 2005
December 2005
May 2006
June 2006
October 2006

Powered by Blogger