Defining Use Cases for Federating Library Services

["Dale,Andy" <>]

Yes... point very well taken... I will make another pass and ensure that
the flows match each other exactly including naming so they can easily
map to each other. 

-----Original Message-----
From: Steven Carmody [] 
Sent: Friday, November 06, 2009 10:01 AM
To: 
Subject: Re: [InC-Lib-UseCase] flow diagram, simple EZP use case

On 11/6/09 10:46 AM, Dale,Andy wrote:
> Based on my discussion with Steve, I drew up this flow diagram. As you
> can see I only included the sequence diagram for the Primary Flow...
let
> me know what you think.
>
>    
Andy ... thanks very much -- I think these diagrams will be *extremely* 
helpful to deployers.

A comment:

-- the IP Auth access diagram shows one of the paths thru the Basic 
EZProxy flow,,,, consequently, I think we should  be *extremely* careful

to ensure that the flow and  steps in the two diagrams are *exactly the 
same*, so that sites/people trying to understand what we're describing 
will have an easier time understanding our proposed model, and seeing 
how one diagram is a subset of the other.

for instance, the Basic EZP flow contains several decision boxes before 
redirecting the user to local IDP; the IP Auth diagram omits these 
decisions... I think its ok to have the IP Auth diagram show only  one 
path thru the Basic EZP diagram; but I think it should a complete single

path.

I can certainly understand an argument that omitting some steps and 
simplifying the diagram makes it easier to understand.... but I think 
this is more than balanced by the need for consistency between the 
diagrams, so people can see how they fit together...