Re: UMI, Lexis-Nexis and Infotrac errors with new rewriting WAM
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Date: Thu, 23 May 2002 08:42:42 -0700
- From: Karen Johnson <johnsonka@xxxxxxxxxx>
- Subject: Re: UMI, Lexis-Nexis and Infotrac errors with new rewriting WAM
Yesterday around 11:00 a.m. we began getting 502 Bad Gateway with all our
databases that we access through the proxy server, even though they were
being accessed locally. I reported this to III. The problem self-resolved
before I got an answer. I was told that they didn't do anything and hadn't
identified the cause They thought it might be our local network
problem. In the light of your report, that seems unlikely.
At 06:21 PM 5/22/2002 -0700, you wrote:
>We are experiencing severe problems with these databases and I wanted to
>check if it was our machine/network/accounts or whether others were having
>the same problems. Any responses positive or negative would be greatly
>With UMI, we cannot access the ProQuest databases, but instead get a 502 -
>Bad Gateway message which indicates a communication problem between the
>proxy server and the ProQuest servers. We have no problems accessing these
>databases directly. I'm inclined to think that this is a problem on the
>UMI side, but I want external confirmation before I try to get something
>from there tech support.
>Our URIs are constructed like so [ABI-Inform]:
>but we have also tried
>all to no avail.
>I'm unsure when this started, but it is pretty imperative that we get it
>With the Universe products on Lexis-Nexis, we cannot use the format for
>print and email functions. Again, we do not have this problem if we
>connect directly to the Lexis-Nexis servers.
>Lexis-Nexis has been completely unresponsive about this. I believe that it
>is traceable to the form that does the reformatting as it includes a full
>URI to the referring page and that appears to be the only difference
>between the two access methods. If I can get confirmation from other
>folks, I might be able to push this through to Lexis-Nexis.
>Finally, with Infotrac (Expanded Academic ASAP), we cannot use the
>individual journal links included with our most recent SerialSSolutions
>list, unless the machine in question already has the cookies set for
>accessing our infotrac account _and_ if we edit the link to include our
>account information (which SS did not do...). This is important to us
>because we wipe the cookies on our public machines every time they are
>SS sent us a link like so:
>Which we edited like so:
>The second link will take you to the list of our infotrac databases the
>first time and then as long as the infotrac cookies are still set, the
>next time you click on one, it will take you directly to the hits for that
>journal. Without the account information, the link works intermittently
>works in IE, but including the account information works always if the
>cookies have been set.
>I tried to talk to 'tech-support' at GaleGroup and they basically said
>this couldn't be done at all and directed me to point to the database
>homepage, but I was wondering if anyone had figured out how to alter the
>URI so that the cookies do not have to be set beforehand to make this
>work. If we can't make this work, I'll update the SS links back to
>pointing at the database page instead.
>Library Systems Manager III
>Santa Clara University
>500 El Camino Real
>Santa Clara CA 95053-0500
>"If you're half-evil, nothing soothes you more than to
>think the person you are opposed to is totally evil."
> - - Norman Mailer
>This message was distributed through the Innovative Users Group INNOPAC list
>Public replies: INNOPAC@xxxxxxxxxx
>Update your subscription options:
Director of Library Systems
University of San Francisco
2130 Fulton St.
San Francisco, CA 94117