According to Stephen L Arnold:
> On 26 Jan 01, at 15:46, Ronald Edward Petty wrote:
> > if u have a file that is in both exclude and restricted, will it show? ex.
> > http://www.asdf.com/asdf is the exclude http://www.asdf.com/asdf/fdsa is
> > the restricted...
>
> In this case, the first one (since it is one level up from the
> second). What you need to do is something like this:
>
> Say you have two directory trees of files under the same root, such
> as:
>
> http://www.asdf.com/reports/asdf/foo
> /bar
> ...
> http://www.asdf.com/reports/fdsa/foo
> /bar
> ...
> and so on. Or maybe you just have the two (or more) top-level
> directories to separate different topics (or whatever). The
> restrict and exclude parameters could be used to provide more
> granular selection of where to search for certain things by
> restricting the search to a specific subset. You can also split
> things into multiple databases as well. In the specific example
> above, you may need to use multiple search forms, each with its own
> set of exclude/restrict settings. In my experience thus far, the
> directory trees above can only go two levels deep for a single
> search form, because you only have the two parameters to work with
> (ie, restrict and exclude). If someone has a creative solution to
> this, I'd love to hear it.
The restrict and exclude parameters aren't quite as limited as you
make them out to be. While you can't have any exceptions to the
exclude parameter (anything that matches the exclude pattern will be
excluded, regardless of whether it also matches the restrict pattern),
you're not restricted in terms of the number of directories or number
of directory levels.
You can have multiple directories listed in the restrict or exclude
parameter values, by separating them with a vertical bar (|), e.g.:
<input name="restrict" value="/reports/asdf/foo|/memos/fdsa/bar">
You can also have multiple definitions of these parameters, which get
merged into a common pattern, as of version 3.1.0. This allows you
to use <select multiple> lists or checkboxes to set the restrict and
exclude parameters.
So, there's a lot you can do without having to go to multiple databases
and multiple config files.
> For example, how did they do the custom search form at SDSU (the
> one to search the course catalog):
>
> http://www.sdsu.edu/cgi-bin/schedule/command=search_form
>
> Do they use a custom version of the htdig code, or is it a
> completely different piece of software? That's a nice detailed
> search form, and it would be really cool to be to use something
> like that...
I can't say for sure, but from the look of it I'd guess it has nothing
to do with htdig or htsearch at all. It looks to me like it would query
some other type of database. htdig and htsearch aren't really designed
for querying multiple fields in this way.
--
Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]>
Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/~grdetil
Dept. Physiology, U. of Manitoba Phone: (204)789-3766
Winnipeg, MB R3E 3J7 (Canada) Fax: (204)789-3930
_______________________________________________
htdig-general mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/htdig-general
