inc-lib-usecase - Shibbolized EZProxy - Basic Use Cases only
Subject: Defining Use Cases for Federating Library Services
List archive
- From: "T. Howell" <>
- To: <>
- Subject: Shibbolized EZProxy - Basic Use Cases only
- Date: Wed, 5 Aug 2009 14:48:32 -0500
Please respond inline in the e-mail.
Denote changed or additional lines with a *.
For example –
The browser user has a variety of possible
"launch points" that may take them to the external resource provider.
For Shib-enabled sites, the flow will * vary, depending on the user's starting
point. The List of Possible starting points includes: go directly to the site,
use a campus maintained navigation
Thanks;
Thomas.
__________________________________________________________________
Model Name :
Shibbolized EZProxy Description of the
Assumed Model:
A library is running a combination of EZProxy and Shibboleth with a flow for
interaction between library patron and EZproxy. EZP has three distinct phases of processing:
Assumption is that the local Shib IdP has optionally been configured to
allow authN by both
The browser user has a variety of possible "launch points" that
may take them to the external resource provider. For Shib-enabled sites, the
flow will vary, depending on the user's starting point. The list of possible
starting points includes: go directly to the site, use a campus maintained
navigation page (ex. http://dl.lib.brown.edu/eresources/index.php?task=alpha<r=S
); a campus maintained gateway of some sort (ex. metalib); a course home page
in an LMS; a google search. Note: The walk-in case is ignored in all of the use case models listed below
because it is described in greater detail as part of an assumed model type. Model Use Cases (Basic)
:
1. Use Case Name :
Use Case Description :
Primary actor(s) :
User Type :
Technology Type :
Vendor Type :
Precondition :
Trigger :
Basic flow :
2. Use Case Name:
Use Case Description:
Primary actor(s):
User Type:
Technology Type:
Vendor Type :
Precondition :
Trigger :
Basic flow :
3. Use Case Name :
Use Case Description :
Primary actor(s) :
User Type :
Technology Type :
Vendor Type :
Precondition :
Trigger :
Basic flow :
4.
Use Case Name:
Use Case Description:
Primary actor(s):
User Type:
Technology Type:
Vendor Type :
Precondition :
Trigger :
Basic flow :
|
- Shibbolized EZProxy - Basic Use Cases only, T. Howell, 08/05/2009
Archive powered by MHonArc 2.6.16.