The World Bank eLibrary
Page last modified on 07 December 2010, at 01:02 PM (initially posted on 7 December 2010)
This includes: Development Outreach, World Bank Economic Review and World Bank Research Observer journal articles published since 1996;Development Economics (DEC) policy research working papers published since 1995; e-books and reports dating as far as the 1970's (in the case of the World Development Reports), plus all new formal publications upon release.
|Publishing Technology||The World Bank eLibrary||eduPersonTargetedID|
The administrator of the institution needs to link the institutional registration to the organisation that is part of the UK Federation. This is done in the authentication page of the administration area.
2. Many services can make use of the eduPersonTargetedID attribute. This is a persistent opaque identifier, which enables service personalisation (remembering data about a user over different login sessions) without the service provider knowing who the user is. If the identity provider supplies the eduPersonTargetedID attribute, the session is treated similarly to an Athens personal account. Otherwise, the service's personalisation features (e.g., saved searches) may be disabled, though the service will still function in the same way as with Athens shared accounts. With some services (e.g., Zetoc Alert) this attribute is mandatory. If so, it is marked as "Required/Yes" in the table in Attribute Usage.
For a Shibboleth IdP, generation of eduPersonTargetedID in
attribute-resolver.xml is described on the IdP setup page.
Release of eduPersonTargetedID by
attribute-filter.xml is described further down the same page.
Users of other IdP software should check their documentation.
8. When a service provider permits or requires individual user registration, they will require the identity provider to present eduPersonTargetedID or eduPersonPrincipalName. This allows logins to be related back to the user's registration details.
NB: in general we recommend the use of eduPersonTargetedID as presentation of eduPersonPrincipalName has implications under the DPA. Configuration of eduPersonTargetedID is described in note 2 above.