InC-Lib-Vendor

[Foster Zhang <>]

Dave,

 

I have discussed this with Elsevier tech support, it will become a problem for the Info provider, if people keep adding entitlement string for various purpose, it may become a performance issue for each login request to parse multi-valued attributes. The same problem with affiliation type attributes. Each university defines the values differently, and I had report from a retired professor that he cannot access ebscohost, because the I did not supply RETIREES as one of the valid affiliation type to ebsco.

 

Foster

 

From: David Kennedy [mailto:]
Sent: Thursday, August 06, 2009 11:22 PM
To: Foster Zhang
Cc: ; Andy Ingham
Subject: RE: [InC-Lib-Vendor] discussion on eduPersonEntitlement on incommon-participants list

 

I agree regarding OCLC

Regarding Elsevier, it seems like they should be able to provide a better fix than just removing the entitlement value requirement, like maybe being able to parse multi-valued attributes.  But, either way, as a customer, as long as I can set up access, I am happy.

Dave

-----
David Kennedy
Systems Programmer
Perkins Library, Duke University
(919) 613-6831

From:	Foster Zhang <>
To:	Andy Ingham <>, David Kennedy <>
Cc:	"" <>
Date:	08/06/2009 11:07 PM
Subject:	RE: [InC-Lib-Vendor] discussion on eduPersonEntitlement on incommon-participants list

 

---

It may have something to do with the problem I reported. After JHU added OCLC specific entitlement, sciencedirect and scopus stop working. It is a wise decision for Elsevier to not depended on entitlement value. It can reduce many problems caused by different vendors request different entitlement value.

OCLC's practice to have entitlement value coded with user account number should be stopped.

Foster Zhang
Johns Hopkins

-----Original Message-----
From: Andy Ingham []
Sent: Thursday, August 06, 2009 4:29 PM
To: David Kennedy
Cc: Foster Zhang;
Subject: Re: [InC-Lib-Vendor] discussion on eduPersonEntitlement on incommon-participants list

Thanks for pointing us to this.  Really interesting stuff, especially
the bit about Elsevier removing ALL requirements for entitlement
attributes for InCommon members; I agree that I'm stumped as to why they
would be willing to do so.

Andy

David Kennedy wrote:
> url for the list
> https://lists.incommonfederation.org/wws/info/incommon-participants
>
> url for the message thread
> https://lists.incommonfederation.org/wws/arc/incommon-participants/2009-07/msg00025.html
>
>
> Dave
>
> -----
> David Kennedy
> Systems Programmer
> Perkins Library, Duke University
> (919) 613-6831
>
>
>
> From:                  Foster Zhang <>
> To:                  David Kennedy <>,
> ""
> <>
> Date:                  08/05/2009 02:18 PM
> Subject:                  RE: [InC-Lib-Vendor] discussion on eduPersonEntitlement on
> incommon-participants list
>
>
> ------------------------------------------------------------------------
>
>
>
> What is the url?
>  
> Thanks
> Foster
>  
> *From:* David Kennedy [] *
> Sent:* Wednesday, August 05, 2009 1:53 PM*
> To:* *
> Subject:* [InC-Lib-Vendor] discussion on eduPersonEntitlement on
> incommon-participants list
>  
> I started a discussion on the incommon-participants list a week or so
> back entitled "eduPersonEntitlement use for enforcing library contracts
> within InCommon participants".  It might be worth looking at the
> archive, as I mention in there what our group is doing.
>
> Dave
>
> -----
> David Kennedy
> Systems Programmer
> Perkins Library, Duke University
> (919) 613-6831
>
>