David Lee King |
Privacy Part 2 – what’s the problem again? Posted: 15 Dec 2010 01:14 PM PST My post titled Anonymity, libraries and websites received quite a variety of comments – thanks for that! The comments cover the whole nine yards – everything from “well, of course David – yay for transparency” to “no, we’d never do that, and don’t ask us to” – quite a range there! The main issue seems to be two things:
I’m going to deal with those issues, in separate posts. Last names first! So – some of you aren’t comfortable with sharing your last names or your photos online for work-related stuff, and said so in the comments of the Anonymity post. I was able to group the objections into three loose categories. Let’s take a peek at each of them: Loose issue #1: Is your last name private info? Quite a few commenters think that sharing your last name in public – while at work – is somehow an invasion of privacy. Not sure I can agree with that, and here’s why:
But more to the point for work-related stuff. At my library anyway, we regularly send our staff out into the community, to do things like presentations, storytimes at schools, meetings, committee and community group work, etc. We expect those staff to provide their names, their business cards, their email address, etc. It’s simply part of the job. So is it any different when doing actual library-related work on the library’s website? Given what my library does … nope. Loose issue #2: Is sharing your last name for work-related things a choice? A couple of commenters said this:
OK – I’ll state up-front that if anyone’s life or well-being is in actual danger, of course there should be an opt-out for those very rare situations. Otherwise, a library should set their expectations, then follow them. Period. Here’s what Stephen Lusk, our HR manager, said when I asked him about the whole choice thing. He said “sure, they have a choice. They don't have to work here.” Then he and Gina (our library director) went on to talk about how good managers and good libraries set expectations on work-related activities, then follow those up with annual reviews, etc. Which brings me to Andy’s comment: “In my system, we are county employees and we wear county employee ID badges. It has our full name on them. Some have taken to making a tag to go over this so that it just shows the first name; others have opted to wear it with just the back showing (hiding their name).” Silly though it might seem, that’s a pretty petty performance issue that should be dealt with up-front. If your library requires staff to wear name badges with both names, then it’s simply a requirement of the job. Just like the dress code policy (if your library has one). Loose issue #3 – poor leadership And Andy’s comment really blends into this last loose issue – that of bad leadership. Here’s a comment from threegoodrats – “At my first job out of library school, we wore name tags with our first and last names. When I started getting obscene phone calls from a patron, we got new name tags with just first names.” A few other commenters said similar things – there was a policy or a guideline in place, one problem cropped up, and the library … changed the policy or guideline to deal with that single issue, rather deal with the exception that happened (i.e., stalkers). One library moved staff around to different branches rather than dealing with a patron problem. That’s bad leadership. Deal with the real issues, guys. Yes – sometimes the work is harder, or it might take longer. But in the end, it’s usually the best thing to do. Next post – let’s deal head-on with those pesky stalkers! pic by Marcus Vegas Share:Related Posts |
You are subscribed to email updates from David Lee King To stop receiving these emails, you may unsubscribe now. | Email delivery powered by Google |
Google Inc., 20 West Kinzie, Chicago IL USA 60610 |
0 comments:
Post a Comment