Add address parameters to update/notify user job
We are a library in an institution that has one library but several locations/physical campuses. The students order material in Primo, and we send material from the library to the students by post (internal system) to their location.
The issue is that our SIS (Student information system) does not seperate the students by locaton, and does not offer any indication to where the stuydent is located in the user profile import to Alma. As it is, we have no possibility to see whether a student is located at the same campus as the library or at one of the others.
By using information from other systems we make users sets, and give them their own User group, with priviliges like ordering request delivered to work address.
With this we need to add an "work"/school address to all students at the other campuses.
At the moment we have to do this manually, as the Update/notify user job does not offer a parameter for adding an address.
Could it be added to the job an parameter to add Work address?
Camilla Pellegrini Meling
shared this idea
Hello All,
This idea has been closed as part of a cleanup process for ideas older than two years with fewer than 20 votes.
This cleanup process is necessary to streamline our idea management process and ensure that the most relevant and impactful ideas receive the attention they deserve. If you still feel strongly about this idea, you may submit it via the NERS process.
We value your feedback and encourage you to continue submitting and voting for ideas that you believe will enhance Alma.
Alma Product Team
-
Kurt Vollmerhause (QUT)
commented
Agreed! In addition, extending this to other Contact Info segments (including user's email addresses) would be highly regarded in order to avoid excessive manual input at the individual user record level.
Another use case is to add/update an existing personal email address to a generic 'work' email address, on a batch basis via Update/notify users job, prior to running a purge user records job. (That is, when the institutional Delete User Policy is set to Keep Fully Reportable, but it is _not_ desirable to include personal email details in Analytics in perpetuity)