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.
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.