Will be there J
From: David Kennedy
[mailto:]
Sent: Friday, October 02, 2009 12:36 PM
To: David Kennedy
Cc: Vries, Ale de (ELS-NYC);
Subject: Re: [InC-Lib-Vendor] InCommon Library Services / Elsevier -
conference call - 10/2 1PM ET
Reminder that we have a conference call today
at 1PM.
Dave
-----
David Kennedy
Application Developer
Perkins Library, Duke University
(919) 613-6831
|
From:
|
David
Kennedy <>
|
|
To:
|
|
|
Cc:
|
|
|
Date:
|
09/30/2009
09:02 PM
|
|
Subject:
|
[InC-Lib-Vendor]
InCommon Library Services / Elsevier - conference call - 10/2 1PM ET
|
Ale,
I am looking forward to our discussion on Friday. Please find below an
agenda for the call.
I have indicated some pre-reading; it would be helpful if you have a chance to
look at these documents. Also, you can find information about who we are
on our wiki: https://spaces.internet2.edu/display/inclibrary/Vendor+Subgroup
Dave
Call Details:
Friday, October 2, 2009 - 1PM EDT
866-411-0013 (US & Canada)
734-615-7474 (non-US/Canada)
Access code: 0122004#
AGENDA
Pre-reading:
https://spaces.internet2.edu/display/inclibrary/Best+Practices
https://spaces.internet2.edu/display/inclibrary/RegistryOfResources
Introductions
- including brief overview of InCommon Library Services Collaboration
Elsevier - overview of Shibboleth implementation
- usage of Shibboleth SP software (SessionInitiators?)
- implementation of WAYFless URLs and direct links to resources
- what has or hasn't worked
Topics for discussion:
Best Practices
- are these feasible for resource providers
- do these make sense
- thoughts on how to go about making this best practice amongst resource
providers
Implementation-specific question
- The URL structure for creating authenticated deep links to Elsevier platforms
is rather complicated. Can this be simplified, possibly with session
initiators?
What role should InCommon or the InCommon Library Services Collaboration play?
- policy setters
- documenters
- testers
- implementation documentation/assistance
Is there a desire/need for standardization across federation members' identity
provider implementations that would simplify the process for resource
providers' configurations?
What are we missing, especially things that you have learned from dealing with
other federations besides InCommon?
-----
David Kennedy
Application Developer
Perkins Library, Duke University
(919) 613-6831
