InCommon Library Services

At 4:00 PM -0700 7/16/08, Eggleston, Holly wrote:
> Hi all -
>
> Per Friday's conversation, here's a preliminary case study template 
> for writing up the current institutional pilots - to have the 
> initial audience for these studies librarians, giving a higher level 
> overview: outlining the institutional configurations and 
> authentication needs, focusing less on the technical specifics and 
> more on the implementation and how it affects the end user 
> experience.
>
> Please send your comments and ideas by end of day Wednesday - we'll 
> discuss at the 7/25 conference call.

Thanks Holly, for getting this started!

A couple of comments:

1) The document seems to divide into two sections -- a campus 
profile, and a pilot/project description. I'm wondering if it would 
be sensible to split these into separate documents?

2) In the profile section, I'd suggest adding a "current library 
services environment" section. Campuses would enter a description of 
their environment: eg use of a portal (eg Metalib), proxy and/or vpn 
for off-campus access, , link resolver, ILL, etc.

3) My sense is that sites are going to make changes to their 
environment in a stepwise, incremental fashion. They may have a sense 
of where they'd like to end up. But, this vision will likely be 
adjusted, based on what they learn along the way.

So I'm wondering if it would make sense to think in terms of campuses 
writing up multiple pilot/project descriptions over time, as they 
move stepwise thru this process?