RE: Accessing Gale products through the Wam proxy

["Albritton, Henry" <Halbritton@xxxxxxxxxx>]

Hello:
 
We have no problems accessing the numerous Gale databases. Our only problem
is that
the WAM statistics program credits all of the hits to the first alphabetical
database (Biography and
Genealogy Master Index). Database IDs and tokesn were assigned to all of them
in the forward table.
 
Is there an "easy" way to get the proper statistics for Gale database usage
without 
salvaging the entire proxy server forward table?
 
Any help would be appreciated.
 
 
Henry L. Albritton
Library Systems
Norfolk State University
 

	-----Original Message----- 
	From: innopac-bounces@xxxxxxxxxx on behalf of Carolyn McDonald 
	Sent: Wed 5/19/2004 8:42 PM 
	To: IUG INNOPAC List 
	Cc: 
	Subject: RE: Accessing Gale products through the Wam proxy
	
	

	John,
	
	It is difficult to be specific without exact details, but we are
using
	some Gale databases through WAM proxy (using rewrite), and we have
none
	of the sorts of problems you describe.
	
	>From the brief information you have given us, I would be looking to
find
	out if there are ANY setup or configuration differences about the
	library network or any external proxy environment. Also, is it the
	initial connection that is so slow, or is it subsequent pages when
	searching etc? That might give you some clues.
	
	Carolyn McDonald
	Library IT Co-ordinator
	Murdoch University Library
	Perth, Western Australia
	email: C.Mcdonald@xxxxxxxxxx
	phone: 61 8 9360 6273
	
	
	
	-----Original Message-----
	From: John Goodyear [mailto:John.Goodyear@xxxxxxxxxx]
	Sent: Thursday, 20 May 2004 7:31 AM
	To: IUG INNOPAC List
	Subject: Accessing Gale products through the Wam proxy
	
	
	Hi,
	
	I've checked the archives and don't find anything about this
particular
	problem.
	We're having issues with accessing our Gale products through our WAM
	proxy.
	They are usually slow as molasses, often to the point of timing out.
	But
	not always, occasionally they zip right through. If we bypass the
proxy
	and
	go straight to the db, it's all pretty much acceptable.  It happens
to
	internal users in the library, maybe more than the remote users.  At
	least
	that's who I'm hearing it from.
	
	Gale tells me no one else has this problem.  Of course I feel much
	better
	after hearing that.  III thinks it's our network, which I doubt.
Other
	products don't have this problem.  At least nowhere near this bad.
	We've
	had a Gale tech here and our network folks are tuned in.
	
	The delay happens with first accessing the db and/or with bringing
back
	search results.  Sometimes one piece, other times the other.
	
	I would imagine there are other III/Gale clients out there with this
	same
	arrangement that we use.  Any ideas?  Wild guesses?  Of course if any
	one
	just knows the answer, jump right in.
	
	Thanks,
	
	John Goodyear
	Library Database Manager
	Pima Community College
	Tucson, AZ
	jgoodyear@xxxxxxxxxx
	520.206.4613
	
	--
	This message was distributed through the Innovative Users Group
INNOPAC
	list
	Public replies:  INNOPAC@xxxxxxxxxx
	Update your subscription options:
	http://innopacusers.org/mailman/listinfo/innopac
	
	--
	This message was distributed through the Innovative Users Group
INNOPAC list
	Public replies:  INNOPAC@xxxxxxxxxx
	Update your subscription options:
http://innopacusers.org/mailman/listinfo/innopac