they only note that results of range searches are sorted according
>> to lexicography.)I find it most efficient to type a simple query,
>> usually without detailed Boolean arguments or, in general, date ranges.
>> Then, depending on the search results, I may modify my search sy
hey only note that results of range searches are sorted according
> to lexicography.)I find it most efficient to type a simple query,
> usually without detailed Boolean arguments or, in general, date ranges.
> Then, depending on the search results, I may modify my search syntax if I
>
may
modify my search syntax if I need to refine the search, but I usually
do this by adding arguments to by search query rather than using the
link to refine my search. Consequently, I only came across the
Advanced Search page option a couple of weeks ago. The feature that
I'd most like to
l say, Jeff!
Yep, the dupes are gone. Interestingly, I've been doing lots of
searches all evening and didn't notice when the change took place!
If I capitalize 'From:' for an author search, I see on the results page
that the system has "corrected" my search syntax to 'f
I've made two fixes to the search engine:
- prevented duplicates from appearing in the results
- case-insensitivity on our special field names in searches (date, from,
subject, message)
That tidies things up nicely.
Jeff
On Thu, Feb 18, 2010 at 10:57 PM, M. G. Devour wrote:
> Jeff,
>
> Th
Jeff,
Thanks for the overview. I'm going to be working on a new web site for
my group, so I may attempt something like that.
Mike D.
> An "advanced search" form would basically have a bunch of fields like
> "subject" and "date" and "from" then string them together into a query
> syntax describ
An "advanced search" form would basically have a bunch of fields like
"subject" and "date" and "from" then string them together into a query
syntax described below. Then redirect that query to the standard search URL.
Implementation would most likely be in PHP. Hard part isn't the programming,
it i
Yes, looks like there is a problem where we are displaying double search
results. We'll look at it this week and fix that right up.
MHonArc is all written in Perl. Lucene is built on Java, but we use it via
a Python wrapper. The Mail Archive's wrapping layers and sorting code is
written mostly
> Hi Mike. That's a very good point about the case sensitivity on the
> "from" and "date" directives. I'll see what I can do to fix that.
Thank you, Jeff. I figure that while it's all fresh for me, the things
I stumble on have the best chance of helping future users. Once I'm
used to it all I'
a high quality open-source
engine.
Jeff
On Tue, Feb 16, 2010 at 6:56 AM, M. G. Devour wrote:
> Well, I've been playing with my shiny new archive! Great stuff!
>
> I stumbled on a less than intuitive detail of the search syntax...
>
> First I tried:
>
> "From: M. G
Well, I've been playing with my shiny new archive! Great stuff!
I stumbled on a less than intuitive detail of the search syntax...
First I tried:
"From: M. G. Devour"
...and got messages in which I was quoted by others. Okay, not what I
thought I was going to get, but makes
11 matches
Mail list logo
