This is an old revision of the document!
OpenAthens Maintenance
To allow patrons to log in to EDS, the 5C have adopted OpenAthens core.
Create Admins
Admin accounts are created in the same way as personal accounts for community borrowers but are separate from the data sent from IT to create accounts automatically for campus users. There is a second step to make a person account an admin for OpenAthens.
Accounts > Create > Personal Account
First Screen: Login
Prefix NetID with OA (for OpenAthens)
Leave login by email toggled to yes - share the username but explain they do not need to use it for login.
Leave default expiration
Always use the email activation code to user - this will allow them to set their own password.
Second Screen: Details
Third Screen: Optional Details
Fourth Screen: Permission Sets
Submit Account
The account now exists in the OpenAthens managed (local) directory but does not have admin access by default. This is a second step.
Access Services will be the primary point of contact to create managed directory accounts in OpenAthens for community borrowers. The creation of an account is the same as the first step for creating an admin.
Before creating an account in OpenAthens you must create the patrons user account in FOLIO first. Please follow any guidelines/workflows created by CUFF or locally by UMass' Access Services department.
Accounts > Create > Personal Account
First Screen: Login
Create a NetID style username for the patron using their first initial & last name
Leave login by email toggled to yes - share the username but explain they do not need to use it for login.
Leave default expiration
Always use the email activation code to user - this will allow them to set their own password.
Second Screen: Details
Third Screen: Optional Details
Assign the group: Community Borrowers
Set their externalSystemID to match the Folio field in the Extended Information accordion ( formatted as librarybarcode@umass.edu)
Do not use the remaining fields.
Fourth Screen: Permission Sets
Submit Account
Once the patron has set their password they will be able to login to use Discovery to place requests and view their account.
Config. Decisions
Jaime & Jack decided the following:
Account codes good for 30 days
Accounts expired after 12 months (of inactivity?)
Expired accounts are deleted after 365 days (cannot increase time)
DBHelp is support email across all of OA
Minimal reports from OA Core are being sent to Jaime & Jack to track certain things. (See Preferences > System Notifications)
-
Open Athens local sign in enabled
"Branding"
Not much is actually branded. Our public name is set to be “UMass Amherst Libraries” while our connection is called “UMass Amherst - Faculty, Staff, & Students” to allow a more clear login path on the OA WAYF page.
It is possible to update the email templates. Jack modified them to use UMass Libraries in place of OpenAthens and to directly reference DBHelp instead of using their sytnax.
Introductory Text: Appears in the OpenAthens local sign in page above form
Connection Selection Box Label: ??
Button Color: For sign in - use UMass branding.
Footer Text: Appears in the OpenAthens local sign in page below form
Sign in title & Hint: Only on OpenAthens local sign in page
On the “MyAthens” dashboard, which we expect patrons wouldn't really ever see - Jack did create a card with some basic information on how to contact the library.