Re: Scoping problems due to caching

[Nancy Smith <smithnj@xxxxxxxxxx>]

Hi, Terry.
Do you include a RESET_SCOPE=1 option in your WWWOptions file?  This causes a reset to the original login scope when the StartOver button is selected.

--Nancy
------------------------
Nancy Smith
smithnj@xxxxxxxxxx
MUSC Library Systems
843/792-1679
843/792-2520 (fax)
------------------------

_On Friday, October 31, 2003 11:58 AM -0500 "Ballard, Terry Prof." <Terry.Ballard@xxxxxxxxxx> wrote:



	We are having an interesting problem with scoping, which we use to generate separate OPACs for our law library and for specific areas in the university library. It's fine as long as you stay within a scope, but if you use scoping, data spills over next time you use the original scope.  It's easy to spot, because the Keyword and subject searches display the scope that is active. We find that we can temporarily get back on track by clearing the cache file. I've tried the obvious fixes such as setting & upsetting lockscope. I know there is a fix because I've seen other libraries with scoping that don't have this problem.  Anybody out there seen this? Thanks in advance.
	
	Terry Ballard

	  <http://innopacusers.org/list/listinfo/innopac>

J?$?{t^&
?&:z?ws0O?l?+7y"?~?7zej)~?7v?y&?}*i'6*'~k?6w}8b3y2?{|3wb2?n?{a. {a{r'?+?K.?.)|M8p~X,4{'?-??r
4?x'
Zr??.)u+^*./{.n?
b"?(???)i?z;?"8?+-~X,6)?x'
Z