On 29 Jan 01, at 11:07, Gilles Detillieux wrote:
> 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">
That's how I have it now, ie, more or less like this; say I have
several types of reports, like Memos, Briefs, and Proceeedings,
each of which are valid for multiple groups, eg, Sales, Marketing,
and Accounting. I have each type of report in its own directory,
and each of these under the group dirs:
/home/html/reports/sales/memos
.../sales/briefs
.../sales/proceedings
.../marketing/memos
.../marketing/briefs
(I think you can see the pattern here :) This setup was fine, with
a single search form containing two selection boxes, one for report
type and one for group name. The code looks like this (sorry for
the wrapping):
<select name=restrict>
<option value="http://my.domain.com/reports">
All Reports
<option
value="http://my.domain.com/reports/sales/memos|http://my.domain.com
/reports/marketing/memos|http://my.domain.com/reports/accounting/mem
os">
Memos
<option
value="http://my.domain.com/reports/sales/briefs|http://my.domain.co
m/reports/marketing/briefs|http://my.domain.com/reports/accounting/b
riefs">
Briefs
<option
value="http://my.domain.com/reports/sales/proceedings|http://my.doma
in.com/reports/marketing/proceedings|http://my.domain.com/reports/ac
counting/proceedings">
Proceedings
</select>
The second select box (for group name) uses the exclude parameter
to keep out all but the selected group:
<select name=exclude>
<option value="">
All Groups
<option
value="http://my.domain.com/reports/marketing|http://my.domain.com/r
eports/accounting">
Sales
(and so on...)
This works fine, although it starts to get hairy as the number of
report types and groups increases. Now add a third level, say
region, and put the same structure above under at least two
regions. At this point, the only thing I could see to do was make
a separate search form (as above) for each region, although
everything is still in one database.
I must admit, I haven't been able to spend as much time with htdig
as I'd like (due to many other things to address) so I'm sure there
are things I'm missing. Could you please point them out, suggest
an alternative, or??
> 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.
Would you happen to know of any examples I could look at? Or have
any other suggestions?
Thanks a-plenty, Steve
*************************************************************
Steve Arnold http://home.earthlink.net/~sarnold418
Things go better with Linux and King Crimson.
_______________________________________________
htdig-general mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/htdig-general
