Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


When you move existing users from OpenAthens accounts to using a local connector, the identifier that they present to a resource is changed. In most cases this does not make any difference to their experience in the resource, however but in some cases it can cause your users to lose saved settings. The two factors that can make a difference are:

  • One or more resources that you access link the users' targetedID to any kind of personalisation (e.g. saved searches, alerts), and
  • You have users who make use of the linked services


  1. Go to advanced search and craft a search to return all relevant accounts across your domain - e.g. active accounts that are not expired across you and all sub-organisations.

  2. From the results, select the checkboxes for the relevant accounts (the select all option may be what you need)

  3. Click the actions button that has appeared and use the download option. Depending on how many accounts you are dealing with, this may take a few seconds or several minutes. If you have a very large number of accounts, say 70,000 or more, you may not be able to download them all in one file.

  4. Once ready there will be a success box with a link to the file page. If you miss the select box, you can get there access the download file via the big downloads button on the homepage.

  5. Download the file to your computer - it is the data under persistentUID that you will need to add to your local accounts in your system. 


  1. Using your skill and judgement, match up the downloaded persistentUID data with the relevant users in your systems and add it to your directory.

  2. Ensure that the attribute holding this data will be passed to us when the user signs in

    1. LDAP - should just work

    2. SIRSI - you will usually need to repurpose an unused use one of the standard attribute such as patronInfo.alternativeID.

    3. ADFS, CAS, SAML - ensure the attribute is included in the ones you release to us

    4. API - the attribute and value only need to be in the payload for the relevant users