Printer friendly page for this section
How does the OpenURL Router link users to the correct resolver?
The Router links users to the correct resolver by identifying their institution, which can be done in several ways:
- IP address
- The IP address of the user's computer can identify their institution, subject to the usual restriction of IP checking (e.g. the user must be on campus or using an identifiable web proxy). The IP address is always available, so it is particularly useful where the referring service does not have an Athens login.
- Domain name
- Domain names can be used in the same way as IP addresses. Because this uses the definitive DNS data it can be easier to configure than IP address checking (if your IP address ranges are complex), but it does require that the user's computer is correctly DNS registered.
- WAYF
- A 'Where Are You From' page is presented to the user. The user selects their institution from a list, and this is remembered for the session. This is, in effect, mirroring the first step of a UK federation login.
We also intend to implement identification mechanisms for any other method of authentication/authorisation that comes into use within the JISC IE.
What about users from institutions that have no resolver?
If a user's institution can be identified, but that institution does not have a resolver registered at openurl.ac.uk, then the user is given a choice of open access resolvers. These currently include GetCopy at EDINA.
Does this mean the OpenURL Router gives the whole world access to your resolver?
The OpenURL Router enables service providers to discover that you have a resolver, but it does not confer any access rights. Most OpenURL Resolvers do not have acess restrictions, but if you choose to implement access control then this will be unaffected by the Router.
