Defining Use Cases for Federating Library Services

[LLG5 <>]

On Nov 6, 2009, at 1:39 PM,  wrote:

> At 1:25 PM -0500 11/6/09, Dale,Andy wrote:
> > > here's my understanding of the flow -- user is at abstracts
> > > site, clicks OpenURl button, is redirected to campus link
> > > resolver, is redirected to campus EZP (with target = deep
> > > link), EZP determines whether or not
> > > target is shib enabled, EZP follows std logic....
> >
> > How does the abstracts site know which campus to send me to?
> > Did I have to authenticate to access the abstracts site?
>
> I believe that works the way that you described... the user arrives  
> at the abstracts site coming from an IP address assigned to the  
> campus (either by using a machine connected to the campus network,  
> or via a campus based proxy)  ..... and "somehow" the abstracts site  
> has a list of the IP addresses owned by the campus....
>
> but, again, it would be great to have a librarian confirm this....

	I am not a librarian but I can describe how this process works at  
Penn State with SFX.  Penn State uses both SFX (Open URL Resolver) and  
MetaLib (Federated Search and gateway to Vendor resources).      Our  
patrons generally access the abstracts via Metalib or SFX.  Off campus  
users are automatically directed through the EZproxy server to access  
the abstract site from these products. (Both Metalib and SFX are  
Ezproxy aware).    At the abstract site, there is a SFX button which  
leads the patron to SFX server at Penn State; this URL doesn't have to  
be Ezproxy aware because SFX is.   This all hinges on the IP addresses  
being registered with the Vendor and configured correctly in Metalib  
and SFX.