http://www.davidleeking.com/wp-content/themes/thesis_16

From the category archives:

Web Management

Showing Patrons the Door

by David Lee King on February 3, 2010

First, a funny story. When I lived in Nashville, I frequented a cool used record store. During one trip, I was trying to decide whether or not to buy a couple of old jazz cassette tapes (hey – I was on a tight budget).

The tiny shelf these cassette tapes were on was packed WAY too tightly, so when I tried to pull one cassette out to examine it, 2-3 others would fall out at the same time. And make lots of noise as they hit the floor (it was tile, of course). This happened a couple of times … in a row … and was pretty embarrassing!

So – to ease my embarrassment at not being able to figure out how to successfully pull a cassette tape off the shelf, a “helpful” shop security guard came over to me. He stood behind me, stared at me for a second, and said (and I quote) – “you’ve got 10 minutes, then you’d better be out of my store.” Then he walked away.

Boy, that helped. Thanks :-) That day, the store essentially “showed me the door” in no uncertain terms. Even though the problem wasn’t me – it was their tightly-packed shelf.

Now on to the title of this post, and to my point. Showing patrons the door? Yikes – we’d never do that (under normal circumstances, anyway)! Unlike the silly used record shop, librarians would never consciously walk up to a patron and tell them to leave if that patron was having trouble using something in the library … right?

I think we DO sometimes tell our patrons to leave when we make things difficult for them. We might as well be saying “here’s the door, don’t let it hit you on the way out.”

For example, if your library has a blog, do you moderate those comments? Quickly? I know of libraries that can go 1-2 weeks before they get around to moderating comments. In and of itself, moderating a comment is fine, as long as they are moderated fast (like within 1-4 hours). Blog posts are supposed to be the start of a conversation; comments continue that conversation. If those comments aren’t approved at least in the same day, you have essentially killed that conversation. To me, that sounds like showing patrons the door.

Is your website confusing? Do customers have to puzzle out what they need to do next while on your site? If so … your website is showing patrons the door. Same with our catalogs – a confusing catalog might just steer customers away from checking stuff out – and that’s one of our major, must-have services!

Do you let patrons sign up for a library card online (some libraries don’t)? How about having an online sign-up form that asks for WAY too much info? That’s a sure-fire way to show patrons the door.

What labels and naming schemes do you use on your site? Using heavy-duty librarian jargon might just be a great way to usher patrons towards the door.

How about not having a Facebook Page (or even blocking Facebook altogether)? Or simply doubting that your patrons use Facebook (without actually signing up for a Facebook account and checking)? Yet another way to show a group of very active, involved patrons the door.

Other ways to show patrons the door might include hard to find stuff on your website, hidden content, or even library services that aren’t mentioned anywhere on your website.

So – what do you think? What else shows patrons the door, and how can we fix that?

Pic by Cayusa

Share:
  • del.icio.us
  • Twitter
  • Facebook
  • email
  • Digg
  • FriendFeed
  • LinkedIn
  • Google Bookmarks
  • Technorati
  • BlinkList
  • Reddit
  • StumbleUpon
  • Tumblr
  • Netvibes
  • Ping.fm
  • MySpace
  • Print

{ 11 comments }

Designing the Digital Experience Presentation

by David Lee King on January 7, 2010

On Tuesday, I gave a Designing the Digital Experience presentation at Nassau Library System in New York. It was a fun time – lots of good questions and discussion!

So … here are the slides from that talk. Enjoy!

Share:
  • del.icio.us
  • Twitter
  • Facebook
  • email
  • Digg
  • FriendFeed
  • LinkedIn
  • Google Bookmarks
  • Technorati
  • BlinkList
  • Reddit
  • StumbleUpon
  • Tumblr
  • Netvibes
  • Ping.fm
  • MySpace
  • Print

{ 0 comments }

Check Your Signs!

by David Lee King on January 4, 2010

I was room 429 ...A couple months ago, I stayed at a hotel in Wisconsin with this sign … seems pretty useful, huh?

Except if you’re in room 429, like I was. I actually had to hunt a bit to find the room (it wasn’t obvious).

The point? Make sure to check your digital “signage” once in awhile. Make sure your labels and headings still make sense. Did you change the name of a room or a service? Make sure to change that name everywhere on your website, too.

Has your budget shrunk and you needed to drop a few databases? Make sure you removed those links on your database page (and any other page that mentions them, too).

Have you checked the driving directions to your library lately? At a previous job, I checked them out after starting, and discovered they were WRONG. So I actually hopped in my car, and drove around for awhile, taking notes of different ways to get to the library – and updated those directions.

Website maintenance never stops, huh?

Oh – and Happy New Year, too! I am looking forward to a fun, challenging 2010 – how about you?

Share:
  • del.icio.us
  • Twitter
  • Facebook
  • email
  • Digg
  • FriendFeed
  • LinkedIn
  • Google Bookmarks
  • Technorati
  • BlinkList
  • Reddit
  • StumbleUpon
  • Tumblr
  • Netvibes
  • Ping.fm
  • MySpace
  • Print

{ 3 comments }

Inviting Comments

by David Lee King on December 17, 2009

Sometimes, a blog post or article on a library website doesn’t get any comments. And that’s fine – not every post is comment-worthy, right? But there are ways to prompt, or “invite” visitors to comment … even by using the website’s built-in comment functionality. Let me show you what I mean.

Here are two examples – the first from my library’s website, and the second one from Atchison Public Library. Both of these examples are screenshots taken from the main page of both websites – each a teaser for an article.

Mine first (screenshot below):

no prompting

We let the comment functionality simply announce that no one has left a comment on this post (and darn it – it’s MY post!). We do that via the text “0 Comments.” This works fine – it’s what that functionality is supposed to do.

But check this out – here’s what Atchison Public Library does (screenshot below):

prompting for comments

See the difference? Atchison uses their lack of comments to … invite people to comment. They do this by prompting their website visitors to “be the first to comment.”

I know – it’s one of those little detail-y things. But it’s that type of detail, that focus on inviting patrons to participate, that just might prompt them … to participate. It might just convert that lurker into a more active participant.

Nothing wrong with that – good job, Atchison!

Share:
  • del.icio.us
  • Twitter
  • Facebook
  • email
  • Digg
  • FriendFeed
  • LinkedIn
  • Google Bookmarks
  • Technorati
  • BlinkList
  • Reddit
  • StumbleUpon
  • Tumblr
  • Netvibes
  • Ping.fm
  • MySpace
  • Print

{ 1 comment }

Widening your Nets, Decentralizing your Web Services

by David Lee King on December 9, 2009

Last summer while at ALA’s annual conference in the Chicago area, a couple friends and I were eating lunch at the Corner Bakery Cafe and saw this ad on one of the tables.

facebook URL ad

The interesting thing about the ad wasn’t so much the content itself (though I’m sure it’s good stuff). We got all geeked out over the URL associated with the ad. Why? Because they didn’t point to their website.

Instead, they pointed directly to their Facebook Page.

Think about that for a sec, because there are some pretty large implications for library web services. I know that many of us have worked for years to centralize all our websites, tools, and services into one place – preferably at www.mylibrarysnamegoeshere.org …. some of us have worked hard to get federated search tools to work on that library website, and have even integrated some of our library catalog content into our websites, as well.

But people aren’t visiting our websites (well, not in droves, anyway). They are going to other places, like Facebook (and YouTube, and Google, and …). And of course we should be active in some of those social sites. But what about pointing directly to those social sites … in an ad? That’s taking it one step further, isn’t it? Pointing directly AWAY from our website … to some social tool like Facebook?

This could work for libraries. If you have a Facebook Page, check out your Page demographics (Facebook provides some basic stats on Facebook Page visitors). Who’s your main audience in Facebook? Doing anything for that group of patrons already?

If so, you might think of taking it one step further, and pointing them directly to the Facebook Page. Why?

  • This group already uses Facebook
  • Your Facebook Page comes ready-made for interaction – comments, discussions, and likes.
  • it can have an easy-to-remember URL (i.e., ours is facebook.com/topekalibrary)
  • For the customer, it’s a direct connection to the library. Once they “become a fan,” they get all your stuff… reminders, questions,comments, etc.

But even better – for us sneaky librarians, it’s also a direct connection to a segment of our customers. But not just any customers – these customers already use Facebook and actually LIKE to interact. If they have become a fan of your library, that means they like to interact … with the library.

So don’t be shy! Spread out your nets … decentralize those web services. Send out status updates. Ask questions. Start discussions. Get feedback about new services. And in the process, have fun interacting with a group that actually WANTS to interact.

Share:
  • del.icio.us
  • Twitter
  • Facebook
  • email
  • Digg
  • FriendFeed
  • LinkedIn
  • Google Bookmarks
  • Technorati
  • BlinkList
  • Reddit
  • StumbleUpon
  • Tumblr
  • Netvibes
  • Ping.fm
  • MySpace
  • Print

{ 2 comments }

Time to Update?

by David Lee King on December 8, 2009

Ever seen a library website that had many of the “normal things” in place, like the library catalog, a handy database link, and an easy way to ask questions … but the people in charge of the site had obviously forgotten to update some of the “little details?”

Here’s what I mean – take a peek at these two screenshots. Here’s the first one:

don't do this!

The “site best viewed with…” statement has a problem or two. First of all, it’s simply not true – I was viewing it FINE using Firefox on a much larger resolution.

Secondly (if the statement’s true), it makes “visiting the library” much harder for a pretty significant chunk of people. For example, at my library’s website, 68% of our web visitors use some form of IE – but that’s most likely weighted, since our 177 public PCs have IE installed, and everyone hits our website upon opening the browser. On my blog, only about 30% of you are using IE… again most likely skewed a bit, since y’all are amazing people who know your stuff (and like to use Chrome, Safari, Firefox, etc, etc, etc).

My point? If you design for one browser, you are in essence making the digital library visit harder for 30-50% of your customers. Would you do that with your physical library? Like make all the doorways 5ft 8 in high, so anyone taller than that would either have to stoop to go through (or would bump their heads) … and then put up signs that say “Library Best Entered by people under 5′ 8″ tall?” I’m guessing not.

[And one other tiny little thing here - if you don't want people to email reference questions to the web email address... don't put the address on the page. Just funnel everything through the large "Contact Us" link, and call it good.]

And one more very similar problem (sorry for the tiny text! Click the pic to see a larger version):

don't do this!

Same stuff, but worse:

  • There is no Netscape Communicator anymore
  • Copyright 2002-2007? What happened to 2008 and 2009?
  • 4.x browsers and above?

I’m guessing the main problem is that the footer has been ignored for at least 3 years, probably longer.

Why bring this up? It’s probably a good idea to check on those little hidden details of your website every so often. Do they still make sense? Does it still hold true? Is it even necessary? Think about it … and edit as needed.

Share:
  • del.icio.us
  • Twitter
  • Facebook
  • email
  • Digg
  • FriendFeed
  • LinkedIn
  • Google Bookmarks
  • Technorati
  • BlinkList
  • Reddit
  • StumbleUpon
  • Tumblr
  • Netvibes
  • Ping.fm
  • MySpace
  • Print

{ 5 comments }

Community Discussion Guidelines for our Digital Branch

by David Lee King on November 18, 2009

Remember my post from last summer about comments at my library’s website? Here’s a follow-up post to that earlier discussion.

Because of all those comments (some of which were mean, snarky and personal), we needed a good, fair, “official” way to deal with them. So I started poking around other websites with commenting policies and guidelines, and came up with a library version of commenting guidelines.

I ended up adapting ours from NPR’s Community Discussion Rules. Want to see a whole bunch of these? Check out  the Online Database of Social Media Policies – good stuff.

Our discussion guidelines are posted (via a link) beside the comment box on each page of our website. Here’s what it says:

*******************************

Community Discussion Guidelines:

Here are some guidelines to posting comments and content at Topeka & Shawnee County Public Library’s digital branch. The goal? To help you have fun!

We encourage comments:

  • We want to hear from you! Please post comments, questions, and other thoughts … as you think them. That’s what we’re here for.
  • Stay on Topic – stick to the subject and issues raised by the post, not the person who made it or others that commented on it
  • Think before you press the publish button. Remember that this is a public forum, and your words will be archived on this site and available for anyone to find for a long time – the web has a very long memory.
  • If you can’t be polite, don’t say it. Respect is the name of the game.  You must respect your fellow commenters.

Some Don’ts:

  • Don’t post copyrighted materials (articles, videos, audio, etc) that you do not have permission to reproduce or distribute.
  • Don’t post content that installs viruses, worms, malware, trojans, etc.
  • Don’t post content that is obscene, libelous, defamatory or hateful
  • Don’t post spam
  • Don’t post personal, real-life information such as home addresses and home phone numbers.

What will we do?

  • We’ll respond to comments, answer questions, and provide suggestions as appropriate.
  • Sometimes we’ll join a comment thread to help focus (or refocus) the discussion, or to get people talking.
  • If you break one of the guidelines above (or come close to it), we’ll email you and ask you to stop. We might also post a reminder to the discussion. If it continues, we will delete your comments and block you from posting.
  • We will remove any posts that are obviously commercial or otherwise spam-like.
  • We will remove content that puts us in legal jeopardy, such as potentially libelous or defamatory postings, or material posted in potential breach of copyright.
*********************************
Does your library or organization have similar policies or guidelines? Drop a link to them in the comments!
Share:
  • del.icio.us
  • Twitter
  • Facebook
  • email
  • Digg
  • FriendFeed
  • LinkedIn
  • Google Bookmarks
  • Technorati
  • BlinkList
  • Reddit
  • StumbleUpon
  • Tumblr
  • Netvibes
  • Ping.fm
  • MySpace
  • Print

{ 6 comments }

Photo Permissions at the Library

by David Lee King on November 10, 2009

Photo 6A couple of weeks ago, Jessamyn over at librarian.net posted about her experience with photo permissions at a library she was visiting. Interesting story – make sure to read the comments!

That reminded me that my  library recently redid our photo permission policy. Like many libraries, our previous photo policy required us to get everyone appearing in the photos to sign-off before we could use the photo … which was pretty hard to do. We ended up not taking many photos!

So, a group of us (admin, me, and a some of our marketing team) met with our lawyer to get some clarification … and ended up with a more flexible, modern photo permissions guidelines!

Here’s what we do now (reposted from our staff website):

A recent conversation with the library’s attorney led to some changes in how we proceed with taking pictures and/or video of our library customers. We hope this encourages more photographing and videotaping of library moments and publishing of them online.

When Do We Need to Use Photo Permission Forms?

For Models. For example, say you bring in your child, grandkid, cousin, friend, etc. and shoot photos of him or her, he or she is acting as a model and needs to sign a photo permission form.

For Close-ups. For example, you are holding a program. You take a close-up photo of one child because you love the expression on that child’s face. You need that child (or his or her parent in this case) to sign a photo permission form.

When Do I Not Need to Use the Form?

At programs held at the library. Want to take pictures at your program? Now it’s easier than ever. (yeah! no more backs-of-heads shots!) In lieu of photo permission forms, programers will need to announce at the beginning of each program that “the library may photograph or videotape you for library promotional purposes. Notify library staff if you do not want to be photographed.” HOWEVER,  if you zoom in for a close-up on one particular person in a large group, you will still need to get a photo permission form signed from that person.

In addition, Communications/Marketing has placed the following announcement in Oct./Nov.‘s connectnow, where it will be published with each edition. That does not mean you can neglect to make the announcement at the beginning of each program.

“Programs, events and classes are photographed or videotaped for library promotional purposes. Notify library staff if you prefer not to be photographed.”

That is not to take the place of the official announcement at the beginning of each event.

So – much easier paperwork for us (as in almost none). Also, this allows us to walk around the library and take random shots that we can use on our website, etc. This of course just applies to library staff. Patrons can take photos in our library – no problems. If they are setting up a formal photo session (we have that once in awhile) or if they are local news organizations, they need to talk to our head of marketing and communications first.

That’s what we do, anyway. What types of permissions does your library need for photographs at the library?

Share:
  • del.icio.us
  • Twitter
  • Facebook
  • email
  • Digg
  • FriendFeed
  • LinkedIn
  • Google Bookmarks
  • Technorati
  • BlinkList
  • Reddit
  • StumbleUpon
  • Tumblr
  • Netvibes
  • Ping.fm
  • MySpace
  • Print

{ 24 comments }

IL2009: Experience Design Makeover

by David Lee King on October 28, 2009

Here’s my Tuesday morning presentation on Experience Design Makeovers for library websites. Even better – some of the presentation was livestreamed here and here!

Enjoy!

Share:
  • del.icio.us
  • Twitter
  • Facebook
  • email
  • Digg
  • FriendFeed
  • LinkedIn
  • Google Bookmarks
  • Technorati
  • BlinkList
  • Reddit
  • StumbleUpon
  • Tumblr
  • Netvibes
  • Ping.fm
  • MySpace
  • Print

{ 3 comments }

Conversation is Experience

by David Lee King on October 8, 2009

Some web designers, especially those with a marketing or graphic design background, say they want to build an experience – but their designed experience, no matter who the website is for, tends to be designed like a movie or a rockstar’s website  – heavy on the Flash, on the intro page (complete with low-pitched ominous music), and it makes cute noises when you click on a link.

That’s great for a movie or a rockstar website. But most of us are building library, organization and company websites. What type of “experiences” should we be creating for those types of websites?

Conversation Spaces

Visitors to your website want to talk – with you, and with each other. Are you providing conversation spaces? The web is FULL of conversation now – check out Amazon, most newspaper and TV news sites, YouTube, this blog, Facebook, Twitter – all spaces where conversation can happen. And conversation DOES happen, because that’s what people do. We like to talk, we like to share, we like to voice our opinion (as I hope some of you do in the comments!).


So, my simple digital experience tip for today is this – make sure to create conversation spaces on your websites. Places like comment boxes, online forums or discussion groups around a topic, Twitter accounts for feedback, online places to Ask a Librarian, etc.

Enable Conversations

Also remember to actually enable conversations once you build the space. What’s that mean? In my library’s case, we allow unmoderated comments to fly free and easy onto our digital branch. I know what some of you are thinking – “OMG, David! Don’t you have a TON of cussing, swearing, name-calling, and other highly inappropriate things being posted? How could you EVER allow that!???!!??”

Um. No. We simply don’t have that. Yes, once in awhile we have some negative comments. But why would we moderate or not show those? Instead, we respond appropriately.

But some of you will need to moderate comments for one reason or the other (i.e., those old-fashioned city attorneys who haven’t yet discovered the joys of Facebook). If you DO moderate comments, make sure to do it quickly. Same day is good. Same hour is best. Why? Because it’s a CONVERSATION. If someone starts a conversation and you don’t get around to moderating the comment for a few days … well, you have killed the conversation. And that’s really no conversation at all.

pic by Adventures in Librarianship

Share:
  • del.icio.us
  • Twitter
  • Facebook
  • email
  • Digg
  • FriendFeed
  • LinkedIn
  • Google Bookmarks
  • Technorati
  • BlinkList
  • Reddit
  • StumbleUpon
  • Tumblr
  • Netvibes
  • Ping.fm
  • MySpace
  • Print

{ 2 comments }