Versions Compared

Key

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

"Walk-in users user" is a common term for people who are allowed to use your library but are not otherwise part of your organisation - e.g. a University Library might have an arrangement with the local community that the general public can access library resources if they come into the library buildings.

...

OpenAthens offers an account type known as an 'Access account' which is great for walk-in users because that type can be shared amongst multiple users and has an IP based restriction on it so that you can limit it to your network or even (with the help of your IT team) to the specific computers used by walk-in users. The IP restriction means that it is perfectly acceptable to do things such as post the credentials on a sign on the wall or similar.

...

Access account credentials are submitted in the same way as any other OpenAthens account, so your existing processes procedures can still apply

If you are using the LDAP or Sirsi connector

...

Restricting which resources an account can access

If your walk-in user users can only be allowed access to a subset of the resources that you subscribe to, you can restrict their access by using permission sets and restrictive mode. There are a couple of approaches:

...

Expand
titleExample for a single organisation
  1. If you do not already have any permission sets under the organisation you will need to create at least two
    1. One set for the walk-in users with the restricted set of resources allocated to it. Set its role as 'library-walk-in'.
    2. One or more sets for the regular users with the relevant resources allocated to them. The role for these is usually 'member'
  2. Create the access account(s) for your walk-in users, assigning the permission set you created (Accounts > Add > Access account)
  3. Allocate the other permission set(s) to the regular accounts if they are not already using them 
    1. For OpenAthens accounts this is done via search or list results and the actions button - see: Search actions
    2. For local connectors this is done via the permissions tab on your connection - see: Permission set rules
  4. If not already activated, turn on restrictive mode
Expand
titleExample using a dedicated sub-organisation
  1. Create a sub-organisation (Accounts > Add > Organisation). Do not assign it a unique identifier or scope.
  2. Impersonate that sub-organisation
  3. Create a permission set containing the resources available to walk-in users and set the role as 'library-walk-in'.
  4. Create the access account(s) for your walk-in users, assigning the permission set you created (Accounts > Add > Access account)
  5. Turn on restrictive mode (Preferences > Organisation)

A The main factor in choosing an approach is how you want things to appear in the reporting interface - the sub-org option will not include the walk-in users in reports unless you change the scope of the report to be all organisations, whereas the single organisation option will include them all together and include the walk-in users' in permission set reports. 

...