Defining Use Cases for Federating Library Services

[Dean Woodbeck <>]

Thomas--

I think this is a good start, but I think it needs to be simplified. 
Lynn made a comment on a call a couple of weeks back that, paraphrasing, 
she needs information that she can use to garner support within the 
library and on campus. So, I think the use cases need to reflect that 
we're talking to people that don't necessarily understand federating.

I will take a stab at this, but may not have it posted until tomorrow 
(Fri) morning.

Dean



T. Howell wrote:
> "The basic use case for EZProxy integrated with Shibboleth involves a flow
> for interaction between a user and a Library website containing a listing of
> various web accessed resources and services, such as, but not limited to,
> various e-journals and research databases. This website uses the EZProxy
> application to proxy authorized access for users of the library thus
> allowing them to utilize resources and services. 
>  
> Users are intended to be able to login via some mechanism to authenticate
> themselves to a group with certain pre-defined authorization privileges
> based on a variety of attributes possibly associated with the user.
> The most basic grouping is an authorized patron or member of the community,
> which may be construed as including but not limited to staff, faculty,
> alumni and other groups. 
>  
> The browser user has a variety of possible starting points within the
> website that may take them to the external resource provider directly or
> which mediates via EZProxy. The threshold trigger for the event occurs when
> the interaction flow results in an attempt to access restricted resource."
>
>
> Hello Everyone,
>
> Please edit the above and with luck we will have at least this to present on
> Friday. If you feel I have left any valuable information out in my rewriting
> of the breakdown version of the use case please let me know. Thanks for all
> of your assistance!
>
>
> Sincerely;
> Thomas Howell.