RE: [htdig] Searches on Date Ranges

mike grommet (
Tue, 30 Mar 1999 11:35:41 -0600

I feel tho that the sorting on date capability is needed, in many cases.
(not to mention, in my current project <g>)

I believe that many of the expensive commercial search engine alternatives
allow this capability... I know that Ultraseek does, but egads they want a
of money for that software.

htdig is a great package nd most of the framework already exists from what
I can see in the code, we just have to hammer out the implementation details

It seems to me that date+time is not so much useful as just date.
No one is indexing on the fly anyway right? So I assume we could just zero
out the
hrs, mins, second fields of the date+time?

I would expect the entering of dates
using month, day, year select boxes (1 each). Then, htsearch can piece them
together into one long string
for the comparison?

Also, we definately need to consider the possibility of the user
entering in an invalid date, such as Feb 30, and such.

More opinions?

-----Original Message-----
From: Torsten Neuer []
Sent: Tuesday, March 30, 1999 10:32 AM
Subject: Re: [htdig] Searches on Date Ranges

On Die, 30 Mär 1999, Geoff Hutchison wrote:
>On Mon, 29 Mar 1999 wrote:
>> Doesn't the HTTP header give you the file modification date? And I
>> sure hope it's in the format YYYY so it will work next year, too ;-)
>No, that's not the problem. We already get the date of the documents from
>the HTTP header. The problem is how you get the date from the *search
>form* since the most obvious solution (a text field for users to input a
>date) requires working out the date format.
>So my question is this: do we just limit the format? If so, what do we
>use? If not, how do we figure out the format used?

I think it should be up to the creator of the form how (s)he handles
input and formatting of time/date. Just provide a couple of variables
where to store the stuff. ISO time/date format will probably work
best because of its sortability.

That way one could use ISO time/date formatted values or ranges to
be directly passed to htsearch in some easy form whereas in a more
complex form time/date input could be done with some nifty form
fields, passed on to a wrapper that checks the entry, ISOifies it
and passes it on to htsearch.

IMHO htsearch should not be overloaded with features, but stay with
good ol' *nix philosophy of being a small tool that handles a part
of a problem. Other tools can do the rest. That would make htsearch
much handier in general and not restrict its use to a specific case.

just my 2 cc,

InWise - Wirtschaftlich-Wissenschaftlicher Internet Service GmbH
Waldhofstraße 14                            Tel: +49-4101-403605
D-25474 Ellerbek                            Fax: +49-4101-403606
E-Mail:            Internet:

------------------------------------ To unsubscribe from the htdig mailing list, send a message to containing the single word "unsubscribe" in the SUBJECT of the message.

------------------------------------ To unsubscribe from the htdig mailing list, send a message to containing the single word "unsubscribe" in the SUBJECT of the message.

This archive was generated by hypermail 2.0b3 on Tue Mar 30 1999 - 11:35:15 PST