...
| Info |
|---|
Note: It was confirmed by Andrea Bainbridge (EXL) by email that a library Barcode, can be specified as primary ID. As long as the college system recognizes the barcode value as the primary ID, there should be no issues with the SIS integration. (And, there is no need to submit two fields with a duplicate value, or map the barcode field to more than one other Alma field.) |
Patron
...
File - Mandatory and Non-Mandatory Fields - Use Cases:
Element | Uses | Mandatory for Operation? |
|---|---|---|
Primary ID | Mandatory for physical circulation: loans, bookings, holds, reserves, fines, fees, blocks | Mandatory |
Email address | Notify patrons when requested items become available or if fines owed | Mandatory |
First Name | Mandatory | |
Last Name | Mandatory | |
Statistical categories (e.g., department, school, program) | Analytics: such as programs/departments can be mapped in Alma; Managing User Statistics allows reports to be filtered by users, by user group, category, and so forth. | |
Expiry date | Useful for cleaning out patron file. | |
Purge date | The date on which the user will be purged. See Purging Users. | |
Provide access to electronic resources via Primo VE from both on and off campus; use of Primo VE to create bookings/holds/ requests, etc., patrons store search results, history & favourites. | Must exist for all relevant users. | |
SIS match identifier | Considered external and will be overridden by the next synchronization with the SIS, keeping your patron file up-to-date Export fines/fees/blocks to Bursar system; | This 3rd party integrationsintegration allows Alma to retrieve relevant user information from the SIS, such as user names, passwords, and user identifiers. |
Provide alternate login for users |
...