InC-Lib-Vendor

["Hamparian,Don" <>]

Hi Dave, see below. I manage the group responsible for product-side planning for IDM.

 

Don Hamparian

Manager OCLC Grid Portfolio

OCLC

614.764.6017 (voice)

614.975.5750 (mobile)

IM, IP Phone (Skype) donhamp2

ICQ: 412-913-446

http://worldcat.org/devnet

 

 

 

>From: David Kennedy [mailto:]
> Sent: Tuesday, September 01, 2009 5:02 PM
> To: Zavar,Jason
> Cc: ; Shibboleth
> Subject: RE: [InC-Lib-Vendor] RE: OCLC and InCommon Library Services Collaboration

 

> I reached out to my colleague, Andy Dale and he provided some
> > additional comments. See below.
> >  
> > >> Is the urn:mace:dir:entitlement:common-lib-terms  an attribute
> > value that OCLC would consider accepting?
> > Absolutely YES – We need to collect more information like this email
> > and understand what our members and customers need. We will go to
> > considerable effort to reduce barriers to access library resources
> > and services. If this is a barrier; we will remove it.
>
> Jason,
>
> Can you provide an update on the above?  Is there a timeline for FirstSearch to use the standard common-lib-terms eduPersonEntitlement value instead of the OCLC-specific value?
>
> Thanks
> Dave
>

 

Dave, we are implementing a new way to access licensed content currently available via FirstSearch. It will be part of the worldcat.org service and more specifically built on that technology platform (which is a different one then First Search).

 

We aren’t planning to make this change for First Search. However, for the worldcat.org-based platform, we are implementing a replacement Service Provider facility.  We are now just discussing this very topic – how to take inbound attributes and map them to our list of institutions.  If you don’t mind, I’d like to discuss this with you in some more detail. Would you be interested in a conference call within the next few weeks?

 

What we do know is the way we do this for First Search is not the way we want to do it in our new facility :-).

>
> -----
> David Kennedy
> Application Developer
> Perkins Library, Duke University
> (919) 613-6831
>

[snip…]

 

> >
> > In response to your question, direct linking to resources are
> > basically persistent URLs directly to resources, as opposed to URLs
> > just to search screens.  Our question is whether or not there is a
> > way to craft persistent URLs to resources, such that the URLs to
> > these resources are WAYFless.
> > So, for instance, if you had a resource that lived at:
> > http://firstsearch.oclc.org/resources/foo
> > and you had a WAYFless URL syntax that made use of a
> > SessionInitiator that lived at:
> > https://firstsearch.oclc.org/Shib/SessionInitiator
> > then direct Shibboleth-authenticated links to resources would look
> > something like this for duke:
> > https://firstsearch.oclc.org/Shib/SessionInitiator?
> > providerId=urn:mace:incommon:duke.edu&target=http://
> > firstsearch.oclc.org/resources/foo
> >

We have a plan for WAYFless URLs we are discussing internally. I’d like to discuss that with you during our conference call if that works for you.

 

> > This feature is very desirable for libraries, because we have the
> > ability to craft these URLs from our own systems (link resolvers,
> > course home pages, metalib, etc) (by sending them through ezproxy
> > and using SPUEdit directives) in order that end users can experience
> > authenticated access directly to resources.
> >
> > Dave
> >
> > -----