Engineering Village now available through the Federation
Page last modified on 08 April 2020, at 10:15 AM (initially posted on 1 November 2013)
Engineering Village links to multiple engineering literature databases from a range of trusted sources: Scholarly journals, trade publications, patents, government reports, reference books, conference proceedings and more. Powerful search tools plus an intuitive user interface boosts research productivity. Hyperlinked records and full-text links give researchers meaningful results through a more comprehensive view of the information.
|Elsevier Science||Engineering Village||eduPersonTargetedID||2,6||No.|
WAYFless URL: Detailed description of WAYFless URL syntax can be found here https://service.elsevier.com/app/answers/detail/a_id/28537/supporthub/elsevieraccess. If your Shibboleth SSO service URL is https://idp.test.institution.edu/shibboleth, and you want to direct user to Engineering Village then the session initiation URL or WAYFless URL for this is:
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.
6. Some services (e.g., ScienceDirect) grant access based on the name (entityID) of the identity provider used, rather than on the basis of user attributes. Therefore, it is not necessary to release any user attributes to such services to gain basic access, though some services may make use of additional attributes if they are supplied; for example, ScienceDirect can make use of eduPersonTargetedID.