Launching to our mutual customers

We can offer to help with communications both to alert customers to the availability of a new publisher / resource and any information that might be needed to ease a transition (e.g. if we’re moving customers off a proxied version).

This could include direct emails to mutual customers, news items, and inclusion in the library customer newsletter. You can also join our Listserv to keep up with the community discussion

Newsletter: https://www.openathens.net/communications/

Listserv: https://www.openathens.net/listserv/

Our team is happy to help with proof-reading, initial launch communications and onboarding of existing mutual customers.

Example news items

Emails

When contacting your customers directly, some things to consider are:

rather than treating it as a special occasion, consider including the same preferred method for getting them set up at your end that you specified under IdP support in the SP dashboard. (See: Edit an application) e.g:
- “… by accessing the SSO tab in your subscription manager”, or
- “… by emailing your customerID, entityID and scope to support@…”
Libraries in the OpenAthens federation would benefit from knowing the resource display name so they can easily find you in their catalogue - e.g.
- “… find us in your catalogue as J.Jonah Jameson Journals”
Let them know which attributes you need them to send so they can set up their end - this should match what’s in the Attributes tab in the SP dashboard - e.g..
- “Either urn:oid:1.3.6.1.4.1.5923.1.1.1.10 or urn:oasis:name:tc:SAML:attribute:pairwise-id
  And urn:oid:1.3.6.1.4.1.5923.1.1.1.9”

Other federations

If you’re using Keystone, don’t forget that you can use it in multiple federations and for direct 1:1 connections from customers who aren’t in a federation.

See:

OpenAthens logos

If you want to use our logo on your website or any publications, see: https://www.openathens.net/resource-hub/logos/