lynx-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: LYNX-DEV Re: FAQ update


From: Al Gilman
Subject: Re: LYNX-DEV Re: FAQ update
Date: Sat, 7 Dec 1996 09:04:16 -0500 (EST)

  From: address@hidden (Larry W. Virden, x2487)
  
  My dream interface for a novice would have the novice select from
  a variety of high level possible areas of asking questions, refining
  as they move along until they hit the answers we have.  If they get to
  an other which has no answer, that page would allow them to enter their
  question, send it along to the FAQ keepers, then do a concept search
  against all Lynx doc and, if no hits result, then do a concept search
  against all lynx-users messages and finally against all lynx-dev messages.
  
Very much what I was thinking.  That's why I want a search engine
somewhere so it can do a joint search of both the docs and the
mail; and I want a link to it worked into the H)elp pages at the
right point.  [And I want the H)elp pages and searching screen
tested and approved by our speech-interfaced users.]

One minor fiddle: The thing to make the default is the search of
all resources, with some heuristic or learned knowledge used to
prioritize hits.  We could have heuristics biasing the system in
favor of hits in Help over random hits in lynx-dev (in the
default).  The user needing help doesn't know which shell to look
under to find the pea.

  Perhaps each page of links would also have a place where the user could
  indicate that a particular message or file helped them resolve their
  problem - giving the faq maintainer assistance in writing an answer.
  -- 

[IMHO, in the blue sky version...]
The first place it goes is into a knowledge base that affects the 
weights used to prioritize hits on future searches.

And the manual resource-writers will want to know, too.
;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;

reply via email to

[Prev in Thread] Current Thread [Next in Thread]