Note: The draft presentation file is now available under the Attachments tab on this page.
===============================================================
Take aways
- Adding shib to to a library access control infrastructure adds value (even in a hybrid env),
- Address the various "perception" issues that are floating thru librarian space
- Convince the audience that the deploy is doable
Problem definition
- Need improve the library community's ability to easily access licensed, off-site resources
Why this is compelling - what is wrong with the current situation
- Key points that others think would be compelling to the internet 2 audience?
- Should we outline other advantages of implementing shib (consistency of logins across campus/library/vendors, ability to license resources for subgroups, etc) as actual problems in the 'Problem Definition' section above, or mention them more as side benefits of addressing the core issue of offsite access?
Vision of the future - how should this work
- What do we want our environments to look like or act like
How do we get there
+ User scenario walkthrough (With UW / EZProxy solution?)
- Public access workstation
- Multiple resource use
- Use of link resolvers
+ Address key issues in place
- Understanding the hybrid environment (some shib'ed, some not)
- Allowing both personalized and guest access
- State of Vendor adoption
+ Business process issues
- managing permissions
- policy/standards for attribute release
- library users who need access but who are not in the campus directory
- Difficulty/resources/effort needed for implementation
+ Protecting user privacy
- attribute release
- unique IdP for vendor/user combinations
- need for graceful logout process for kiosks
+ Browser User Experience navigating the WAYF
- on campus
- link resolvers
Next steps
- Resources available
- How to get involved