Make "updated by" field configurable, not primary ID
There are many areas in Alma that will list the last Alma user to update something. These fields will display the primary identifier of the last updater, but we find this is not particularly helpful when we log in with our campus shib accounts, as this makes our employee ID number show up here. It would be more helpful if we could use Last Name, First Name or something similar in the Updated By fields.
Chris Bulock
shared this idea
-
Dean Seeman
commented
Yes this is a real privacy concern. Besides that, it is much more usable to see at a quick glance the names associated with an action (as opposed to an employee number).
-
Kerri Hicks
commented
Adding to the chorus here. It's not only not helpful when we don't have the name or other easily identifiable information there in the UI, it's a privacy risk to be sharing employees' unique ID barcodes, which can be used for other systems or campus services.
This could easily be dismissed as not too big a deal, since folks in fulfillment may have access to this information already, but folks in fulfillment are bound by an ethical responsibility of privacy in most libraries. Not everyone hacking the Primo front end may be charged with those same requirements.
-
Edward Bilodeau
commented
Sad to see that nothing has been done on this two years later. We just tripped over this issue and will have to hide the operator IDs (Config > User Mangement > General > Manage Operator Details Visibility) until ExLibris fixes this and allows us to specify a sharable identifier.
-
Paulina Harper
commented
Our IT dept would prefer we use a unique, but very long, string of letters and numbers as our unique identifiers in Alma/Primo, but if we do we will have the same problem as Chris. We would also like the "updated by" field to be configurable to use Last Name, First Name or something else human-identifiable.