Re: Scoping issues

[Karl Maria Fattig <kfattig at bowdoin dot edu>]

Elizabeth,

Apologies to the list for beating this dead horse. I do think that there 
are many libraries out there who don't know that this behavior is 
happening in their catalogs.

Thanks for the tips for workarounds.

Karl

Elizabeth Thomsen wrote:
> This is a very complicate and messy issue.  For more background, there 
> was a long discussion on this back in 2003, under the subject ": Losing 
> Scope from Pages Not on Innovative Server."  The problem affects search 
> boxes on pages not on the server, as well as individual links.
> http://innovativeusers.org/list/archives/2003/msg01173.html
>
> We used the Javascript solution that Rich Edwards describes in these 
> messages, which he could no doubt explain better than I can.   Mike 
> Copley documented a different approach for the Clearinghouse, which you 
> can see here:
> http://innovativeusers.org/cgi-bin/clearinghouse/view.pl?id=108
>
> I think III needs to give us much more information on how scoping works, 
> and why the scope needs to be set on the server at all.
>
> Elizabeth
>
>
> Karl Maria Fattig wrote:
>
> > Actually Ed, III's own documentation is wrong in this case. I've been 
> > told that they are going to correct this. It certainly gives the 
> > impression that one is able to create a persoistent link to a scoped 
> > searchset, but that is NOT the case.
> >
> > The part that is particularly misleading is:
> >
> > "For all searches, you can limit the search to a specific scope by 
> > appending the following to any of the URLs presented above:
> >
> > &searchscope=<scope number>"
> >
> > That's just not correct. It may actually display the search and in 
> > many cases it will work, but if the browser user hasn't established an 
> > Innopac sessionid via a cookie set from the Innopac catalog server 
> > prior to clicking on that link, the link will display a scoped browse, 
> > but the results pointed to in the browse index will not be scoped, and 
> > the browse links will point to "incorrect" records.
> >
> > BTW, we tried messing around with "get" vs "post" and that didn't make 
> > a difference. Perhaps though others have made this work? Is anyone out 
> > there able to demonstrate a scoped-search link into their catalog 
> > originating outside of the catalog?
> >
> > Thanks,
> >
> > Karl
> >
> > Ed Seedhouse wrote:
> >
> > > > What III has pointed out to us now is that because our library home 
> > > > page
> > > > is on a different server from our catalog, we cannot include a scope
> > > > dropdown from the home page.
> > >
> > >
> > >
> > >
> > > That can't be true if you are using the "get" method on the form.  
> > > According
> > > to the documentation at 
> > > http://csdirect.iii.com/faq/persistenturls.shtml you
> > > can use scopes with persistent url's and all the "get" method does is 
> > > tack
> > > stuff on the end of the url.
> > >
> > > You will have to create your own hand coded select box since you 
> > > can't use
> > > the scope token on other servers, and that means that if you change your
> > > scoping you will have to hand recode that page, but it is surely 
> > > do-able.
> > >
> > > Ed Seedhouse
> > > Greater Victoria Public Library
> > >
> > > --
> > > This message was distributed through the Innovative Users Group 
> > > INNOPAC list
> > > Public replies:  INNOPAC at innopacusers dot org
> > > Update your subscription options: 
> > > http://innopacusers.org/mailman/listinfo/innopac

--
Karl Maria Fattig
Technical Services Manager / Catalog Librarian
Interim Acquisitions Librarian
Hawthorne-Longfellow Library
Bowdoin College
3000 College Station
Brunswick, ME 04011-8421
207.725.3027 (vox)
207.725.3083 (fax)
151164662 (icq)
mailto:kfattig at bowdoin dot edu