Journal Archives at Mimas

Page last modified on 19 January 2015, at 06:37 PM (initially posted on 4 April 2012)

Journal Archives is a full text journal platform enabling users to cross search, browse and download millions of articles via a single easy-to-use interface.

Consolidating the journal archives licensed in perpetuity by JISC Collections on behalf of its members, it contains content from a wide range of subject areas including the sciences, social sciences, humanities, engineering and law.

Journal Archives is one of three platforms in the JISC eCollections service.

This service is available for subscription to UK HE, FE & research councils through JISC Collections.

JiscJournal ArchiveseduPersonScopedAffiliation


(where <XXX> is the Entity ID of your organisationšs Identity Provider).

You can use the WAYFless URL generator (WUGEN) tool to generate a WAYFless URL for your institition.

Go to the WAYFless URL generator (WUGEN) tool:
Select your institution as the "Identity Provider"
Select "Journal Archives" as the "Service Provider"
Accept the default target URL of ""

A WAYFless URL will be displayed for Journal Archives for your institution.


1. The only attribute that an identity provider must release for its users to be able to access many services that are licensed for use by everyone at a particular organisation is eduPersonScopedAffiliation. This is a scoped attribute, which might, for example, have the value "member" in scope "", often written as:

It is used for the basic authorisation decision: does subscribe to the service in question? If so, the user is allowed access. The service provider will maintain its own list of which organisations (scopes) can access its service. For allowed organisations, the federation's Technical Recommendations for Participants indicate that, in HE/FE, users with scoped affiliation values from the set {member, student, staff, faculty, employee} are typically authorised to access content licensed on the basis of the JISC Model Licence, while {affiliate, alum} are not.

While a Shibboleth identity provider can generate eduPersonScopedAffiliation statically by setting the required value in attribute-resolver.xml, this should only be done when it is known that all users are authorised. Otherwise, the value can be picked up from your LDAP / Active Directory as described on the IdP setup page.

Users of other IdP software should check their documentation.

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.