[ List Archives Home ] [ Thread index for 2008 ]
[ Date index for 2008 ]
[ Author index for 2008 ]
[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
- Date: Wed, 26 Jan 2000 16:05:10 -0700
- From: Tom Tyler <bdldmaster@xxxxxxxxxx>
- Subject: Re: Web Access Management options
Sara,
Re: WAM - URL Verify options problems
We encountered a real problem with this
feature this week. We set up for the
automatic URL verification to be done on a
weekly basis (Monday AM at 2:00). This
product creates two output files: a
.../screens/urlverify.html file and a review
file of bibs for all problem records
encountered in the verification process.
In our system, there is a limit on the
maximum size of all files in the /screens
directory - ca. 1 million bytes. Our
urlverify.html file was 1.6 million bytes.
The result -- our system hung up, records in
a payfile were lost, and things generally
came to a grinding halt.
While I have no way to say absolutely that
the URL verify software caused the problems,
I think that this was the case.
You should know that all GPO created PURLs in
bib records are reported as errors; this
causes a vastly inflated html file of
reported errors.
Tom Tyler
Associate Director for Budget & Technical
Planning
University of Denver Library
Denver, CO 80208
ttyler@xxxxxxxxxx
-----Original Message-----
From: Sara Brownmiller
<snb@xxxxxxxxxx>
To: innopac@xxxxxxxxxx
<innopac@xxxxxxxxxx>
Date: Wednesday, January 26, 2000 3:39 PM
Subject: Web Access Management options
The University of Oregon Library will soon be
implementing III's Web
Access Management. I would appreciate
hearing from others using this
module about the pros/cons of the command
link option versus the proxy
server option. Below are some questions we
have:
1. Does use of the command link, with all
database urls pointing to the
III server, put a heavy load on your system?
2. It seems that the command link option is
more transparent to the user,
not having to configure a proxy in their
browser. Do users have a lot of
trouble setting up the proxy preferences? Do
your public service or
systems staff spend a lot of time helping
patrons troubleshoot this
process?
3. Is anyone using a mix of the command
link/proxy server options?
4. Are there issues or problem areas that
were particularly troublesome
when you implement Web Access Management that
you can provide advice
about?
thanks for your thoughts.
Sara
Sara Brownmiller snb@xxxxxxxxxx
Systems/Women's Studies Librarian
541/346-2368
University of Oregon Library 541/346-3485
(fax)
1299 University of Oregon
Eugene, OR 97403-1299