Eric,
 
I'm late in responding to this:
 
At 11:00 PM 1996/03/27 +0100, Eric Thomas wrote:
 
>Now,  version  1.8c  will  also   include  full  support  for  the  INDEX
>subscription option  (already written  and tested).  This includes  a new
>command that allows you to retrieve individual messages from the archives
>(this  command  is  used  internally  by the  INDEX  code,  but  will  be
>documented as  NDSU's experience with /SHIP  makes it clear that  this is
>something power users do find useful).  I imagine that we could implement
>a SEARCH  command that would  look for certain  words or phrases  in list
>archives,  and return  item  numbers that  can be  used  to retrieve  the
>postings in  question. Something similar  to SCAN, with a  simpler syntax
>than the  database functions.  This might provide  some relief  for sites
>that  use  the  database  functions  for simple  things,  and  it  should
>hopefully not alienate  the graphical-oriented customers because  it is a
>minor  development  that  nobody  will dream  of  labeling  a  "strategic
>direction" or anything like that. Comments?
 
Something like this would be *extremely* helpful.  I'd say that over 95
percent of our database searches are very simple requests that could be
satisfied by something similar to SCAN.  Most of our requests are searches
for names or email addresses.  People search for messages to or from someone
and then use /ship to retrieve the messages.
 
 
                               Peace,  Dan
 
<<  Daniel D. Wheeler - Education & Psychology, Univ. of Cincinnati  >>
<<  KIDLINK Director of Educational Services & Subscription Manager  >>
<<  Email: [log in to unmask]      URL: http://www.uc.edu/~wheeler/  >>