<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: SEraja&#8230;.the biggest repository of events on the web?</title>
	<atom:link href="http://www.webyantra.net/2006/08/09/serajathe-biggest-repository-of-events-on-the-web/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.webyantra.net/2006/08/09/serajathe-biggest-repository-of-events-on-the-web/</link>
	<description>Ground Zero for Indian Web 2.0</description>
	<pubDate>Tue, 16 Mar 2010 19:04:35 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Satish Rajan</title>
		<link>http://www.webyantra.net/2006/08/09/serajathe-biggest-repository-of-events-on-the-web/comment-page-1/#comment-1209</link>
		<dc:creator>Satish Rajan</dc:creator>
		<pubDate>Mon, 28 Aug 2006 07:43:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.webyantra.net/2006/08/09/serajathe-biggest-repository-of-events-on-the-web/#comment-1209</guid>
		<description>Hi,

Thanks for your responses.

About the editorial process at SEraja, we have a dedicated inhouse content team that generates events using the automated crawler and then based on certain parameters, refines and completes the information aggregated. We know that the present content team setup is not scalable as more and more events get added into our system.

But, there are two ways we hope this will resolve itself. Firstly, more users would mean more people visiting the site and with the ability of collaborative enhancing of knowledge, the wiki way, the content should behave itself to a great extent without any editorial team intervention. Still the inhouse editors will have automated tools to pick out possible exceptions that will then be looked at and approved/disapproved.

The second way is that we plan to set up small editorial teams across the world based on the demand for events from that location and this in turn will allow us to cleanse and manage more content than from a central place with limited local knowledge.

In all, the editorial team is mainly involved only in the management of content that is auto generated. We hope that once the usage goes up, so will the self monitoring of the user added content and then the editors can merely monitor the content thus enabling scalability. The automated part of content generation should grow but in the ideal case be just a small percentage of the user generated content and this will reduce the expectations out of the editorial team.

Thanks again,

Regards,

Satish Rajan</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>Thanks for your responses.</p>
<p>About the editorial process at SEraja, we have a dedicated inhouse content team that generates events using the automated crawler and then based on certain parameters, refines and completes the information aggregated. We know that the present content team setup is not scalable as more and more events get added into our system.</p>
<p>But, there are two ways we hope this will resolve itself. Firstly, more users would mean more people visiting the site and with the ability of collaborative enhancing of knowledge, the wiki way, the content should behave itself to a great extent without any editorial team intervention. Still the inhouse editors will have automated tools to pick out possible exceptions that will then be looked at and approved/disapproved.</p>
<p>The second way is that we plan to set up small editorial teams across the world based on the demand for events from that location and this in turn will allow us to cleanse and manage more content than from a central place with limited local knowledge.</p>
<p>In all, the editorial team is mainly involved only in the management of content that is auto generated. We hope that once the usage goes up, so will the self monitoring of the user added content and then the editors can merely monitor the content thus enabling scalability. The automated part of content generation should grow but in the ideal case be just a small percentage of the user generated content and this will reduce the expectations out of the editorial team.</p>
<p>Thanks again,</p>
<p>Regards,</p>
<p>Satish Rajan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: amit</title>
		<link>http://www.webyantra.net/2006/08/09/serajathe-biggest-repository-of-events-on-the-web/comment-page-1/#comment-1065</link>
		<dc:creator>amit</dc:creator>
		<pubDate>Fri, 25 Aug 2006 06:25:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.webyantra.net/2006/08/09/serajathe-biggest-repository-of-events-on-the-web/#comment-1065</guid>
		<description>Gaurav,

"Also, from the product perspective - this shows quite a good mix of user-driven, editor-managed, robot-initiated."

I feel the way Seraja is aggregating data is quite unique. Though (as you point out) once they start scaling up, it might pose problems. It will be interesting to know what goes into the editor managed part of content creation. I mean, who does this and how? maybe Satish can give us some insights into this.

amit</description>
		<content:encoded><![CDATA[<p>Gaurav,</p>
<p>&#8220;Also, from the product perspective - this shows quite a good mix of user-driven, editor-managed, robot-initiated.&#8221;</p>
<p>I feel the way Seraja is aggregating data is quite unique. Though (as you point out) once they start scaling up, it might pose problems. It will be interesting to know what goes into the editor managed part of content creation. I mean, who does this and how? maybe Satish can give us some insights into this.</p>
<p>amit</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gaurav</title>
		<link>http://www.webyantra.net/2006/08/09/serajathe-biggest-repository-of-events-on-the-web/comment-page-1/#comment-1061</link>
		<dc:creator>Gaurav</dc:creator>
		<pubDate>Fri, 25 Aug 2006 01:29:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.webyantra.net/2006/08/09/serajathe-biggest-repository-of-events-on-the-web/#comment-1061</guid>
		<description>1. I like Satish and Ramesh's conceptualization of the EventWeb and thinking of the web with a new form of basic data. While we it is immensely difficult to change consumer behavior, I believe it is implementations of concepts such as these that will lead to some reduction in the web's complexity.  Thanks everyone for some really good thought on this post. 

2. Also, from the product perspective - this shows quite a good mix of user-driven, editor-managed, robot-initiated. 

3. (as a word of caution though, won't success mean that the current internal company editorial process will get unwieldy?)</description>
		<content:encoded><![CDATA[<p>1. I like Satish and Ramesh&#8217;s conceptualization of the EventWeb and thinking of the web with a new form of basic data. While we it is immensely difficult to change consumer behavior, I believe it is implementations of concepts such as these that will lead to some reduction in the web&#8217;s complexity.  Thanks everyone for some really good thought on this post. </p>
<p>2. Also, from the product perspective - this shows quite a good mix of user-driven, editor-managed, robot-initiated. </p>
<p>3. (as a word of caution though, won&#8217;t success mean that the current internal company editorial process will get unwieldy?)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ramesh</title>
		<link>http://www.webyantra.net/2006/08/09/serajathe-biggest-repository-of-events-on-the-web/comment-page-1/#comment-332</link>
		<dc:creator>Ramesh</dc:creator>
		<pubDate>Fri, 11 Aug 2006 14:44:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.webyantra.net/2006/08/09/serajathe-biggest-repository-of-events-on-the-web/#comment-332</guid>
		<description>Great discussion.  

One important fact that has not come up in this discussion and the original post is that SEraja is 'EventWeb', not just events.  It is the Web of events that makes them a lot more interesting.  The Web is a lot more powerful in case of events than it is in case of documents that led to the DocumentWeb also called WWW.  Events naturally are related and lead to understanding that is otherwise not possible.

Another important thing is that 'calendar of events' like in Eventful or EventsinIndia represents only a very minor fraction (say 1-2%) of events that we take interest.  News, history, movies, etc are all past events and our life is full of those and their effects on us thru the EventWeb.

By the way, I am doing a series on EventWeb to make sure that the problem mentioned in the last sentence of the post ('The casual website visitor is unlikely to be able to comprehend the full range of SErajaâ€™s capabilities from the websiteâ€™s content.') can be taken care of.  And, I started that much before I saw this post.  It is at 
http://ngs.ics.uci.edu/blog/</description>
		<content:encoded><![CDATA[<p>Great discussion.  </p>
<p>One important fact that has not come up in this discussion and the original post is that SEraja is &#8216;EventWeb&#8217;, not just events.  It is the Web of events that makes them a lot more interesting.  The Web is a lot more powerful in case of events than it is in case of documents that led to the DocumentWeb also called <a href="http://WWW" rel="nofollow">http://WWW</a>.  Events naturally are related and lead to understanding that is otherwise not possible.</p>
<p>Another important thing is that &#8216;calendar of events&#8217; like in Eventful or EventsinIndia represents only a very minor fraction (say 1-2%) of events that we take interest.  News, history, movies, etc are all past events and our life is full of those and their effects on us thru the EventWeb.</p>
<p>By the way, I am doing a series on EventWeb to make sure that the problem mentioned in the last sentence of the post (&#8217;The casual website visitor is unlikely to be able to comprehend the full range of SErajaâ€™s capabilities from the websiteâ€™s content.&#8217;) can be taken care of.  And, I started that much before I saw this post.  It is at<br />
<a href="http://ngs.ics.uci.edu/blog/" rel="nofollow">http://ngs.ics.uci.edu/blog/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ramesh Jain&#8217;s Blog &#187; Blog Archive &#187; SEraja</title>
		<link>http://www.webyantra.net/2006/08/09/serajathe-biggest-repository-of-events-on-the-web/comment-page-1/#comment-330</link>
		<dc:creator>Ramesh Jain&#8217;s Blog &#187; Blog Archive &#187; SEraja</dc:creator>
		<pubDate>Fri, 11 Aug 2006 14:08:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.webyantra.net/2006/08/09/serajathe-biggest-repository-of-events-on-the-web/#comment-330</guid>
		<description>[...] Webyantra has a coverage of SEraja &#8211; I agree that in the current stage of the development &#8212; a very early stage &#8212; I think this is a very well conceptualized product and it addresses a very basic human need. However, I spent quite some time going through the website and in my opinion, some of the communication about the product and how it works, needs to be explained better. [...]</description>
		<content:encoded><![CDATA[<p>[...] Webyantra has a coverage of SEraja &#8211; I agree that in the current stage of the development &#8212; a very early stage &#8212; I think this is a very well conceptualized product and it addresses a very basic human need. However, I spent quite some time going through the website and in my opinion, some of the communication about the product and how it works, needs to be explained better. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Satish Rajan</title>
		<link>http://www.webyantra.net/2006/08/09/serajathe-biggest-repository-of-events-on-the-web/comment-page-1/#comment-323</link>
		<dc:creator>Satish Rajan</dc:creator>
		<pubDate>Fri, 11 Aug 2006 09:54:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.webyantra.net/2006/08/09/serajathe-biggest-repository-of-events-on-the-web/#comment-323</guid>
		<description>"How do you pronounce SEraja?"

Well, again, we leave it open to the comfort of the person using it. There are two ways in which I have seen people pronounce the name.

1. Some people call it "C-raja" (as one word). This is what we, at SEraja, prefer to call it.

2. Due to the capitalization of the first two alphabets, some people have come to pronounce it as "Ess, E, Raja" as in three distinct words.

Rajesh,

As to why one would publish, "The first time I saw a Kannada Movie and felt like watching a captionless comic bookâ€ as an event may depend. In my view, this was a very memorable event in my life and I have a couple of photographs and a short audio clip capturing my reactions at that time. I would post this on SEraja as a "Private" event for memory sake. I may even post this as a "Public" event as a funny moment in life, maybe even a serious note to emphasis on the "In Rome do as the Romans do" idea. There are many reasons why I may post it, but capturing an event that still remains fresh in my memory on to a platform where I can attach experiences to it, share it with a group or all or even keep it private or even create an activity around it for a select group of people ("Have you ever watched a movie, not knowing what's going on?"), is enticing and open to an array of uses only limited by our imagination.

Amit,

It has been a conscious decision to keep the search bar to the lower part of the page for the following reasons:

1. We wanted to shift the focus from "Searching" of events to "Exploring" of events. There are some more new ideas on the burner that will help us with this. We are hoping to bring relevance in the top half of the page to the visitor (like IP mapping of the events on the homepage) so that search is used only when required. We are working on the premise that not all experience need to begin with a search. "I don't know what I want, but I know I want something." (This will also help in cross consumption, "I came looking for something, but found something else more interesting.")

2. We thought that the search function should be used only after consuming the contents on the page, not as the starting point, wherein we could reach a stage where the user will ignore the rest of the content and just go to the search bar. (Every user should feel that he will find something useful at our site whenever he visits, rather than visiting only when he needs something specific). (to draw a limited parallel, how easy has it become for us to ignore the ads in yahoo mail or hotmail.)

Thanks for your questions...

Cheers</description>
		<content:encoded><![CDATA[<p>&#8220;How do you pronounce SEraja?&#8221;</p>
<p>Well, again, we leave it open to the comfort of the person using it. There are two ways in which I have seen people pronounce the name.</p>
<p>1. Some people call it &#8220;C-raja&#8221; (as one word). This is what we, at SEraja, prefer to call it.</p>
<p>2. Due to the capitalization of the first two alphabets, some people have come to pronounce it as &#8220;Ess, E, Raja&#8221; as in three distinct words.</p>
<p>Rajesh,</p>
<p>As to why one would publish, &#8220;The first time I saw a Kannada Movie and felt like watching a captionless comic bookâ€ as an event may depend. In my view, this was a very memorable event in my life and I have a couple of photographs and a short audio clip capturing my reactions at that time. I would post this on SEraja as a &#8220;Private&#8221; event for memory sake. I may even post this as a &#8220;Public&#8221; event as a funny moment in life, maybe even a serious note to emphasis on the &#8220;In Rome do as the Romans do&#8221; idea. There are many reasons why I may post it, but capturing an event that still remains fresh in my memory on to a platform where I can attach experiences to it, share it with a group or all or even keep it private or even create an activity around it for a select group of people (&#8221;Have you ever watched a movie, not knowing what&#8217;s going on?&#8221;), is enticing and open to an array of uses only limited by our imagination.</p>
<p>Amit,</p>
<p>It has been a conscious decision to keep the search bar to the lower part of the page for the following reasons:</p>
<p>1. We wanted to shift the focus from &#8220;Searching&#8221; of events to &#8220;Exploring&#8221; of events. There are some more new ideas on the burner that will help us with this. We are hoping to bring relevance in the top half of the page to the visitor (like IP mapping of the events on the homepage) so that search is used only when required. We are working on the premise that not all experience need to begin with a search. &#8220;I don&#8217;t know what I want, but I know I want something.&#8221; (This will also help in cross consumption, &#8220;I came looking for something, but found something else more interesting.&#8221;)</p>
<p>2. We thought that the search function should be used only after consuming the contents on the page, not as the starting point, wherein we could reach a stage where the user will ignore the rest of the content and just go to the search bar. (Every user should feel that he will find something useful at our site whenever he visits, rather than visiting only when he needs something specific). (to draw a limited parallel, how easy has it become for us to ignore the ads in yahoo mail or hotmail.)</p>
<p>Thanks for your questions&#8230;</p>
<p>Cheers</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: amit</title>
		<link>http://www.webyantra.net/2006/08/09/serajathe-biggest-repository-of-events-on-the-web/comment-page-1/#comment-320</link>
		<dc:creator>amit</dc:creator>
		<pubDate>Fri, 11 Aug 2006 06:15:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.webyantra.net/2006/08/09/serajathe-biggest-repository-of-events-on-the-web/#comment-320</guid>
		<description>Rajesh,

You've asked something, that I was wanting to ask Satish i.e. how do you pronounce SEraja .

Satish,

One quick question- the search box (that basically defines a search engine), is at the bottom of the homepage. Should it not be at the top of the page for maximum eye contact. Or its intentionally kept at the bottom?

amit</description>
		<content:encoded><![CDATA[<p>Rajesh,</p>
<p>You&#8217;ve asked something, that I was wanting to ask Satish i.e. how do you pronounce SEraja .</p>
<p>Satish,</p>
<p>One quick question- the search box (that basically defines a search engine), is at the bottom of the homepage. Should it not be at the top of the page for maximum eye contact. Or its intentionally kept at the bottom?</p>
<p>amit</p>
]]></content:encoded>
	</item>
</channel>
</rss>
