home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!agate!doc.ic.ac.uk!uknet!mucs!mcchpc.mcc.ac.uk!zlsiimw
- From: zlsiimw@mcchpc.mcc.ac.uk (Mark Whidby)
- Newsgroups: comp.infosystems.gopher
- Subject: Re: Waisindex a file containing keywords pointing to other files
- Keywords: waisindex keywords HyperText
- Message-ID: <6793@m1.cs.man.ac.uk>
- Date: 19 Nov 92 08:55:41 GMT
- References: <3338@accucx.cc.ruu.nl>
- Sender: news@cs.man.ac.uk
- Reply-To: M.Whidby@mcc.ac.uk
- Organization: Manchester Computing Centre
- Lines: 24
-
- In article <3338@accucx.cc.ruu.nl>, henny@accucx.cc.ruu.nl (Henny Bekker)
- writes:
- |>
- |> Hello All,
- |>
- |> I like to known if someone has succeeded in waisindex-ing a
- |> (short) file containing lines with keywords pointing to other (the
- |> real big ones) files..
- |> I like to use gopher as a frontend for it..
- |> Imagine:I have a file containing descriptions of titels of documents.
- |> I like to index the file with waisindex so that a 'hit' results
- |> not in a seacrch to the description but to the original file
- |> of the descriptions..
- |> I don't known how to implement this with waisindexing and gopher.. (if
- |> possible at all ??)
-
- The only thing I can think of is to ensure that the real files have as
- their first line the title of the file and then use the -t first_line
- option when you waisindex them. Forget about the short file. I don't
- know if this will work - best to try indexing a couple of files first
- and see what happens.
- --
- _____________________________________________________________
- Mark Whidby, Distributed Systems, Manchester Computing Centre
-