Both campus and user group are required fields in the user details section of our implementation of Alma.
Each user will have one user group and one campus assigned.
In general, we use the campus field to associate a patron with their home library. The campus codes are based on (and are often, but not always, identical to) the library codes we use in Alma.
We are using campus to:
The campus code and campus name are not directly viewable by the patron.
Campus codes usually correspond to the city that the library is located in (e.g., "COLLEGEPRK"), while the campus name will correspond to the library name (e.g., "Betty Petersen Memorial Library").
We use the user group field to associate a patron with a group of users that has certain privileges. Most often, those user groups are also based on the patron's home library.
We are using user group to:
Patrons can view their user group in their My Library Card page by logging in, going to view My Library Card, and clicking on the Personal Details tab. The user group is listed as Patron Group, near the top of the tab.
The default user group is "EMPLOYEE", but typically a user group affiliated with a particular campus will be assigned where possible.
In general, each campus will have one or more corresponding user groups.
Most libraries have a corresponding "Public" and "Staff" user group (with user group codes ending in "PUB" or "STAFF", respectively). In this case, "Staff" means library personnel (both federal and affiliate staff), and "Public" typically means non-library NOAA personnel (both federal and affiliate staff).
Some campuses will only have one user group (e.g., SILVERSPRGX, which has only a public user group because the library staff are all part of SILVERSPRG).
There are also a number of generic user groups not routinely affiliated with a particular campus. Some of these are role-based user groups, like ILL, EMPLOYEE, or LIBSTAFF. Others are legacy status-based user groups that are a holdover from Sirsi (e.g,. BINDERY, DISPLAY, and INTRANSIT). Status-based groups are no longer necessary and should never be assigned to accounts held by individuals.
It is possible for a patron to have a campus that does not correspond directly to their user group (e.g., a campus of SEATTLEREG but a user group in "Seattle NWFSC Public"). Typically, however, we would handle this by making sure that both campuses had the same rules/permissions where possible, since keeping the user group and campus aligned helps ensure greater precision in statistics.
One of the reasons we define new user groups and/or campuses is to more accurately pinpoint and troubleshoot which users are entitled to access to which resources. Because of this, user groups may be useful in troubleshooting access to electronic resources.
User groups and campus information (or at least their precursor fields) are used in Open Athens to help identify the appropriate permission sets for each user.
We also assign user groups and campus through the patron load, so they are encoded into the patron load script.
We should create a new campus when:
Campuses are closely related to assignable patron groups in the patron load, so there may also be times when it makes sense to create a new campus if a new patron group will be assigned by the patron load script.
We should create a new user group when:
Table or Values | Change Type | System | Typically Required? | Why | When |
---|---|---|---|---|---|
Campus List | Campus | Alma | Yes | Define campus codes and display values | Add/Edit campus |
Library Information | Campus | Alma | No | Define libraries served for new campus | New physical location |
User Groups List | User Group | Alma | Yes | Define user group codes and display values | Add/Edit user group |
User Group/Record Type | User Group | Alma | Yes | Allow records to be created with new user group | Add user group |
Fulfillment Units/Fulfillment Rules | User Group | Alma | Yes | Allow users in user group to circulate materials and place requests | Add user group |
To edit or add new campus and user group values, you must have the General System Administrator permission in Alma.
All of the following steps are done from the Configuration menus in Alma. Make sure that Configuring: NOAA Library and Info Services (the institutional-level location) is selected from the dropdown at the top of the Configuration screen for all following steps (otherwise some menu options may not be visible.)
Notes:
To add a new campus:
The user record type/user group table controls which record types can be created with which user groups. New user groups must be added here so that they can be added to user records of the appropriate record types.
All user groups automatically assigned to patrons must have the Public type selected, because all records come in as the Public type through the patron load. We typically also add Staff to all patron user groups for the sake of compatibility. We do not usually add new user groups that are to be assigned to Contact or Organization records (these are used for Electronic Resources and are not for logging in or circulating materials).
If the user group is allowed to check out materials, they must be added to the appropriate Fulfillment Unit Rules for each fulfillment unit. Otherwise, they will not be allowed to borrow any materials.
Typically, most patron-load-assigned user groups will be in the "Employee" (non-library NOAA personnel) fulfillment rules.
If a user group has its own new policies, those policies should be created before editing the fulfillment unit rules. In most cases, new user groups should use existing policies (where possible).
To edit the rules: