NetNews Usenet Archive 1993 #3/NN_1993_3.iso/spool/bit/listserv/pacsl/3129

Text File | 1993-01-25 | 7.6 KB | 171 lines

Comments: Gated by [e-mail]
Path: sparky!uunet!paladin.american.edu!auvm!CS.UNR.EDU!FOSTER
X-Mailer: Mail User's Shell (7.2.5 10/14/92)
Approved-By:  Public-Access Computer Systems Forum <[e-mail]>
Message-ID: <9301221756.AA01924@pyramid>
Newsgroups: bit.listserv.pacs-l
Approved: [e-mail]
Date:         Mon, 25 Jan 1993 13:13:12 CDT
Sender:       Public-Access Computer Systems Forum <[e-mail]>
From:         Steve Foster <[e-mail]>
Subject:      veronica FAQ, part 2
Lines: 157

----------------------------Original message----------------------------
--------------------------------------------------------------------------
Q3:Why do I need to use "item descriptor" to get host and context
information?

A3:One simple answer to this is that three-times as many lines
would be needed on the screen to provide host and path information
as well as title information.  The menus returned by veronica are
often lengthy, even without this information.  Since the item-
description function is included in most gopher clients, its use
makes for more compact screens.

There is a deeper answer, of course ...

The veronica server is designed to work with the query-type item
of all gopher clients.  It can only return one set of data
in reply to each query, in accord with the gopher protocol.  There
is no chance for further negotiation between the client and server.
The veronica-search server could return visible lines about the
host and context of each item, but it would need to do so for all
items, tripling the size of the return as mentioned above.  The
only alternative is to design special gopher CLIENTS which  either
submit a follow-up query to the veronica server, requesting more
information, or which present the item-descriptor in more palatable
format.   Work is underway to define a client-server negotiation
protocol to allow followup queries, using the gopher+ clients and
servers.  Meanwhile, clients just are not capable of this feature.

And deeper yet ...

Context means many things ...  Is it adequate to know the host, path
and type of an item, or do you want to know the last update time,
the number of links to that item in the entire gopher network,
a unique internet-id for that data item, the names of veronica servers
referencing that item, and so forth?  The gopher+ protocol and other
emerging protocols will allow us to maintain some of this information.
The veronica developers at Nevada feel that it is preferable to use
these standards as they become available, rather than to define
ad-hoc document identifiers, etc. which are specific only to veronica.

--------------------------------------------------------------------------
Q4:How can I get my server into the veronica database?

A4:Explicit registration is generally not required.  The veronica
data-collection software will find your gopher server IF it is
registered with the Mother Gopher at Minnesota, OR IF it is
referenced on the menu of another gopher server which is registered
at Minnesota.  Of course, the veronica data-harvesting algorithm
will not be able to access your server if you have restricted access
to your local site.

-----------------------------------------------------------------------------
Q5:How can I keep my server OUT of the veronica database?

A5:Sometimes gopher-administrators do not want their site to be
indexed. The administrator of such a server will need to mail to
[e-mail], and request their site not be included.

This design is based on the well-founded assumption that any
registered gopher server, or a server accessible via the menu of
a registered server, is intended to be accessible to users at any
internet node.  The gopher protocol achieves its utility through
this sort of sharing; gopher servers are provided with the "-s"
option should it be necessary to implement site restrictions.

With the implementation of Gopher+ protocols, the veronica+
protocol will allow gopher administrators to set a
"veronica-index-off" flag.

--------------------------------------------------------------------------
Q6:How often is the database updated?

A6:Heretofore, the database was updated every two weeks.  A lot of
network traffic is generated by the indexing process.  We at U. Nevada
thought it not optimal to index more frequently.  Most likely, we
will index more often in future.

The veronica development team is working on a standard protocol
for locally-generated indexes, and a standardized method for
collating these indexes at a central data site.  The post-processed
dataset will then be redistributed to sites running veronica
query-engines.  This approach will greatly reduce the number of
gopher-walks and gopher-trees necessary to supply all veronica sites
with data.

--------------------------------------------------------------------------
Q7:Where can I get the software to run veronica?

A7:The NeXT-specific veronica retrieval software can be obtained
by anonymous ftp from veronica.scs.unr.edu, in the "veronica"
subdirectory.

The veronica development team is finishing up the WAIS indexing
programs and will have the software available via anonymous ftp
hopefully by the end of January 93.

The WAIS-veronica distribution will include small modifications to
the WAIS index builder, as well as a WAIS-index query engine.

The WAIS-indexed version is prefered for three reasons:
1.  runs on more platforms.
2.  runs faster.
3.  allows partial Boolean searches.

--------------------------------------------------------------------------
Q8:Where can I get the veronica data set?

A8:You can anonymous-ftp the full veronica dataset from
veronica.scs.unr.edu, in the "veronica" subdirectory.

This data has been processed to eliminate redundant references,
to avoid loops in the gopher network, and to remove most data
that is known to be highly transient.

If you are trying to set up a veronica server, PLEASE take a
copy of this data, rather than initiating more gopher-tree
processes.

---------------------------------------------------------------------------
Q9:Why can't I get a reply from a veronica server?

A9:The most common problem is that the gopher client "hangs" because
the  results of the veronica search includes items of some type
not recognized by the client.

For example, a search will commence and there is some indication
that it is working, like a spinning wheel on a Mac or on a Unix client.
However, when the wheel stops spinning the Gopher client says
"Nothing  available".

The problem is that some gopher clients can not handle certain objects
(e.g., a PC client is unable to understand a Unix sound file).
Many clients are written to treat as empty any directories containing
non-standard or unrecognized datatypes.

The solution will be in the Gopher+ protocol.   That protocol
will allow a client and server to have a "conversation" about
what types of data the client can and cannot handle.

---------------------------------------------------------------------------
Q10:What does "veronica" mean?

A10:very easy rodent-oriented net-wide index to computerized archives.

---------------------------------------------------------------------------
Q11:Why doesn't my server show up in veronica searches?

A11:Most commonly this is because your server was not accessible during
the time we last collected data.  We will now preserve older data
files, and use them in lieu of current data for those servers that
cannot be reached during the data harvest.

Be sure your server is registered with the Mother of Gophers, or is
referenced on the menu of a server which IS registered.  Be sure you
have not restricted off-site access.

If these don't work, send mail to [e-mail]