Download Voyager with Unicode Technical User's Guide

Popacjob
NOTE:
Search logging takes up a lot of drive space. A single record is around 600
characters in length; saving 1,000 searches to the database requires 73
megabytes of hard-drive space. If you plan on keeping Search Logging activated
for any length of time, you should plan on regularly extracting information and
purging it from the database (by specifying option -p).
Setting Up OPAC Search Logging
Use the following to set up OPAC search logging.
1. Turn the Search Logging feature on.
In the /ini directory on the server (/m1/voyager/xxxdb), the voyager.ini
file contains a line reading
LOGSEARCH=
2. Place a Y after the equals sign to turn search logging on; or an N after the equals sign
to turn search logging off.
At the time of installation, search logging is turned off.
Optionally, you can set the identifier string for computers that will be running
OPAC. This string is in the opac.ini file of each WebVoyáge display directory
(vcit, zcit, z3950, and so on) and its format is as follows:
StatString=
Any text after the equals sign will be recorded in the OPAC_search_log table or
bib_usage_log table as the requesting OPAC clients’s ID number. It may be a
maximum of ten characters (including spaces). If left blank, the field will display as
WebOpac.
The string may be unique for each WebVoyáge display directory containing its
own opac.ini file (vcit, zcit, z3950, etc...), or you can assign the same
string to any number of display directories.
If OPAC is running on terminals from a server (WebVoyáge), all terminals
connecting to that server will return the same ID string.
In addition, regardless of whether the StatString= feature is in use, the IP
address of each requesting OPAC client will be recorded in the Client_ip field of
the OPAC_search_log table.
Endeavor Information Systems, Inc.
See notice on first page
February 2004
Voyager® with UnicodeTM
15-5