<span style><font color="#222222" face="arial, sans-serif">As you mentioned, the user query is a mix of formal grammar (we want to support </font></span><span style>operators with precedence and brackets to control that) and more free </span><span style>form text. </span><span style> </span><div style>
I was suggesting some ways to improve the later.</div><div style>I am giving the links of the three pics, kindly go through it and you will have some idea as to what I was trying to say.</div><div style><a href="http://sehaj.my3gb.com/Pic1.PNG">http://sehaj.my3gb.com/Pic1.PNG</a>
</div><div style><a href="http://sehaj.my3gb.com/Pic2.PNG">http://sehaj.my3gb.com/Pic2.PNG</a>
</div><div style><a href="http://sehaj.my3gb.com/Pic3.PNG">http://sehaj.my3gb.com/Pic3.PNG</a>
</div><div style><br></div><div style>Maintaining logs will improve parser as the present query can be matched against the recent queries. This way, suppose for example, if we find the exact query, the time taken by search engine </div>
<div style>can be reduced. Also even if the exact query can't be found, this will help parser in making sane and better Query object trees by matching against some logs and using algorithms like longest common sub-sequence etc. This way query can be modified a bit to make more sense from the free form text.</div>
<div style><br></div><div style>These were the plans suggested to improve parser functioning. Please guide me, about the other ways in which the parser can be modified for better outputs.</div><div style><br></div><div style>
Note : The pics attached are from a patent document whose URL is <a href="http://www.google.co.in/patents?hl=en&lr=&vid=USPAT6766320&id=Q4MSAAAAEBAJ&oi=fnd&dq=query+parser+for+search+engine&printsec=abstract#v=onepage&q=query%20parser%20for%20search%20engine&f=false" target="_blank" style="color:rgb(17,85,204)">http://www.google.co.in/patents?hl=en&lr=&vid=USPAT6766320&id=Q4MSAAAAEBAJ&oi=fnd&dq=query+parser+for+search+engine&printsec=abstract#v=onepage&q=query%20parser%20for%20search%20engine&f=false</a> . This is just used to reflect the idea which are present in many search papers. </div>
<br><div class="gmail_quote">On Thu, Mar 22, 2012 at 1:56 PM, Olly Betts <span dir="ltr"><<a href="mailto:olly@survex.com">olly@survex.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Thu, Mar 22, 2012 at 01:20:06PM +0530, Sehaj Singh Kalra wrote:<br>
> I have sent a reply with some attached photographs but xapian mailing list<br>
> is saying that message is awaiting approval because it's size is big.<br>
<br>
</div>I'm not sure how photographs would be relevant, but anyway the size<br>
limit is in place for a reason. Please put large attachments on your<br>
website and send a link. That way only those who want them have to<br>
download them.<br>
<br>
Cheers,<br>
Olly<br>
</blockquote></div><br>