Defining Use Cases for Federating Library Services

["T. Howell" <>]

Hello Everyone,

During today's call we agreed to work on a new three pronged plan (+ 1).
First we are in the process of migrating the existing work on use cases into
the more simplified form as per Dean's suggestion [the Access Management
Camp use cases]. Second we will be starting to reference and include some
case studies which we will link from use cases to the individual case
studies and/or suggested solutions. Finally we will create UML inspired
diagrams for each use case to help define the relationships which exist
"under the covers" between the steps in the flow described in use cases.
This page will also contain more alternatives to the basic use case.

Steve Carmody will be writing up a sample experience (bedtime story inspired
by Ann West) that can be used to communicate to non-technical people the
reasons and motivations for working with shibboleth.

We, Marc S., Thomas H., Dean W., and Tim M., will work on trying to solidify
once and for all the basic use case of EZProxy/Shibboleth. This will link to
a page that contain more advanced alternative (for example the Ares use case
given on today's phone call).

Here are some important links for the work we plan on doing over the next
week. Please contact the list with any questions, requests, or corrections. 

Thanks and have a great weekend!
Thomas.


This is the new format for all of the use cases:
<https://spaces.internet2.edu/display/inclibrary/Technology+Approaches+Organ
ized+by+Areas+of+Interest>

This is the new page for the flow diagram and the permutations on the basic
use case (note each use case will have its own follow-up page:
<https://spaces.internet2.edu/display/inclibrary/Library+Patron+wishes+to+ac
cess+a+journal+online>

This is the aggregation page for Case Studies (remember that we will also
link from the individual use cases to individual case study):
<https://spaces.internet2.edu/display/inclibrary/Case+Studies>