Hi,
I'd be interested in reading more about that decision too, if a source link is available.

If libraries are truly going toward OpenAthens, especially vendor-mediated OpenAthens, there will need to be community support, guidelines, and best-practices from library colleagues on what end-user identifiable information should absolutely never be linked to it.

In sessions on OpenAthens by vendors, they've really excitedly shared how it will open up opportunities for e-resource analytics by connecting patron demographics. The potential unintended consequences of libraries paying with user data / becoming the product / failing to live the ALA Core value of providing patron privacy are not hard to imagine, and in my opinion something that must be avoided.

Julia


Julia Caffrey-Hill
(she/her/hers)
Web Services Librarian
Albert S. Cook Library
Towson University

 

-----Original Message-----
From: Code for Libraries <[log in to unmask]> On Behalf Of Hammer, Erich F
Sent: Monday, March 15, 2021 1:29 PM
To: [log in to unmask]
Subject: Re: [CODE4LIB] RA21/ seamlessaccess.org

[EXTERNAL EMAIL - USE CAUTION]

They are!?  When?  Source?

We're just now looking at testing SSO/SeamlessAccess with some of our largest vendors, but we have no illusions that we will be able to use it for all of them.  Several of the OpenAthens presenters at ER&L last week made no bones about needing to keep EZProxy for edge cases.  

Erich


On Monday, March 15, 2021 at 13:15, Kun Lin eloquently inscribed:

> Since OCLC is going to discontinue standalone EZProxy, anyone has 
> tried RA21/seamlessaccess?  Is it still just open to publisher so far?
> 
> Thanks
> Kun