broken access publishing

19
Broken Access Publishing OR How to make your site incompatible with library-intermediated workflows Simon Inger, September 2013 This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License

Upload: simon-inger

Post on 20-Jul-2015

193 views

Category:

Education


0 download

TRANSCRIPT

Page 1: Broken access publishing

Broken Access Publishing

ORHow to make your site incompatible with library-intermediated workflows

Simon Inger, September 2013

This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License

Page 2: Broken access publishing

Discovery and DeliveryLibrary Web Pages

Resource Discovery, e.g. Primo, Summon, EDS

Link Server/Resolver, e.g. SFX, Serials 360, EDS

Target

Page 3: Broken access publishing

Library Technology Components

• Library web pages– Direct readers to the most appropriate place to

start their content discovery• Resource Discovery Services (RDS)

– (Primo, Summon, EDS, a.k.a. web scale discovery)

– A&I are indexes of content and usually library-recommended

– Libraries invested much in multi-subject RDS• Link server/resolver

– Manages multiple incarnations of content

Page 4: Broken access publishing

Journals and MonographsLibrary Web Pages

Resource Discovery

Link Server/Resolver

Target

Page 5: Broken access publishing

A&ILibrary Web Pages

Resource Discovery

Link Server/Resolver

Target

Page 6: Broken access publishing

ReferenceLibrary Web Pages

Resource Discovery and Target

Link Server/Resolver

Secondary Target

Page 7: Broken access publishing

AuthenticationLibrary Web Pages,sometimes authenticated

Resource Discovery, authenticated

Link Server/Resolver, often authenticated

Target, often authenticated

Page 8: Broken access publishing

Case study 1 – UK university

• Preferred sign-in method for library is Shibboleth• Publisher supports Shibboleth• Publisher offers free alumni access if it can be monitored

– Publisher does not support Shibboleth attributes (which would report alumni)

– Publisher requires separate IP address• Library needs readers to use IP address access instead• Link server can only record one URL for each target, so on-

site and off-site users have to use proxy– (Proxy is in another country or cloud based and invalidates publisher’s

Google analytics)

• Library finds it cannot get 2 IP addresses from proxy provider

• Broken Access

Page 9: Broken access publishing

Case study 2 – university in Oman

• Entire country uses single IP gateway because of government censorship, so institutions indistinguishable

• Preferred sign-in method for library is Shibboleth• Publisher supports Shibboleth• Resource Discovery Service does not support Shibboleth• Library needs readers to use IP address access instead, via

a proxy• Publisher does not support proxies• Broken Access

Page 10: Broken access publishing

Case 3 – hospital in South Africa

• Whole regions of the medical sector in South Africa share IP addresses, so institutions indistinguishable

• Many remote workers, often out in the field• Library not advanced enough for Shibboleth• Publisher supports off-site access and proxies, but licence

demands that only off-site users use the proxy• Library’s only option anyway is to provide access for its

patrons via a proxy– Library either breaches licence or doesn’t buy product

• Broken Access

Page 11: Broken access publishing

Access Planning

Page 12: Broken access publishing

Shibboleth or AthensRe

ader •Unauth‐

enticated

•External SSO•OpenID•Facebook•Google•Yahoo Li

brary techno

logy •Library web 

pages

•SSO

•Proxy

Externaldiscovery •Google

•A&I

Publishe

r •WAYF

•WAYFless

•IP

•Content

Page 13: Broken access publishing

WAYFless via library technologyRe

ader •Unauth‐

enticated

•External SSO•OpenID•Facebook•Google•Yahoo Li

brary techno

logy •Library web 

pages

•SSO

•Proxy

Externaldiscovery •Google

•A&I

Publishe

r •WAYF

•WAYFless

•IP

•Content

Page 14: Broken access publishing

WAYFless with external SSORe

ader •Unauth‐

enticated

•External SSO•OpenID•Facebook•Google•Yahoo Li

brary techno

logy •Library web 

pages

•SSO

•Proxy

Externaldiscovery •Google

•A&I

Publishe

r •WAYF

•WAYFless

•IP

•Content

Page 15: Broken access publishing

Proxy and IP AccessRe

ader •Unauth‐

enticated

•External SSO•OpenID•Facebook•Google•Yahoo Li

brary techno

logy •Library web 

pages

•SSO

•Proxy

Externaldiscovery •Google

•A&I

Publishe

r •WAYF

•WAYFless

•IP

•Content

Page 16: Broken access publishing

Proxy via local SSORe

ader •Unauth‐

enticated

•External SSO•OpenID•Facebook•Google•Yahoo Li

brary techno

logy •Library web 

pages

•SSO

•Proxy

Externaldiscovery •Google

•A&I

Publishe

r •WAYF

•WAYFless

•IP

•Content

Page 17: Broken access publishing

Open Access

• This must all favour Open Access publishing, right?

• Yes and No.• If, in an Open Access future, libraries stay

intermediated, they are going to want to measure the utility of each title they link to, which means they will want usage statistics, which means the OA publisher will need to authenticate

• BUT – authentication can be much lighter and is more likely to be compatible

Page 18: Broken access publishing

Think How You Fit In, and Plan!Library Web Pages

Resource Discovery, e.g. Primo, Summon, EDS

Link Server/Resolver, e.g. SFX, Serials 360, EDS

Target

Page 19: Broken access publishing

Questions?

[email protected]@renewtraining.com