Add Patron Proxy data to Analytics
It is seemingly impossible to query a list of current patron proxy relationships that have been established in Alma. This is a basic piece of reporting data that needs to be added to Analytics to help libraries keep their patron records up to date.
-
The User Details subject area has been enhanced with the following improvements:
You can now create reports with fields from different folders as is possible in other subject areas.
The User Measures dimension was added, which contains measure fields relating to the number of users.
The following fields were added under the User Details dimension:
Cataloger Level – the cataloger level of the patron
Patron Letters Opt In – the letters for which the patron has opted in
Patron Letters Opt Out – the letters for which the patron has opted out
Has Role Other Than Patron – indicates if the patron has a role other than Patron
Has Role Other Than Patron and Instructor – indicates if the patron has a role other than Patron and Instructor
Is Blocked – indicates if the patron is blocked
The Proxy For dimension was added, which contains fields that indicate for whom the patron is a proxy.
The names of the various Status, Type, and Note fields were expanded to include the dimension name to clarify which fields are intended.For more information please see the Alma June Release Notes:
https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2021/Alma_2021_Release_Notes?mon=202106BASE -
Anonymous commented
There is already an idea for this topic: https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/15015132-add-proxy-users-to-users-subject-area
For loan transactions, it is recorded in Analytics fulfillment subject area when this was done by a proxy user.
-
Ted Schwitzner commented
Proxy relationships should be present as a dimension under the Users subject area. At a minimum, attributes should include User ID and/or Primary ID for the user that is the proxy, then the User ID and/or Primary ID for the proxied user (i.e., Proxy For). Having the date the user was assigned as a proxy would also be useful.
If possible, loan transactions should also record when a proxy user was the person who charged the item.
If possible, requests should record when a proxy user places a request on behalf of their "proxy for" user.