Week 14 Best Practices

Before you start that blog, Wiki, or other Web 2.0 project, you may want to consider and answer the following questions. By following these steps your Web 2.0 project is more likely to be a success.

1. Why are the Tools Being Used?

Why is the library creating this Web 2.0 service? What need does it address?

§         Does the blog replace infrequent news releases and newsletters?

§         Does your Wiki explain how to search better than before?

§         Does the Folksonomy help people find information?

§         Do photos provide access to a rare collection?

 If you can’t answer these questions, then stop and re-consider your plans. Without a clear answer, your great plans will end up in a corner collecting dust once the “wow” factor wears off.

2. Know Your Tools  

Know your blogs from your Wikis and media sharing. Trying to blog with a Wiki or media share with a Folksonomy is the equivalent of trying to nail two boards together with a saw. Blogs are for communication, Wikis for knowledge creation, and RSS for delivery of that information. To become familiar with these tools, the library should examine the work of other libraries that have successfully implemented these tools, both by looking at their sites and by talking to their staff.

3. Be Professional 

You wouldn’t go to a job interview in your jeans would you? Then why blog with someone else’s URL? The domain name you choose is among the first impressions you make. Some blogs may be free but it is not professional to “piggyback” on them for use by a library. Look for tools or services that let you create content at your URL. It may cost a bit more, but like that well-tailored suit, it will show the library has put time and effort behind the service being offered.

4. Standards

Technical standards may be ignored by many users but the library should be aware that they exist for a reason. By following W3C and other standards, it is more likely that users will be able to access your tools. This is important as not everyone uses Internet Explorer and assuming so is likely to impair the functionality for some users. Libraries should also remember the visually impaired and others with special needs may require the use of Web 2.0 to contact the library. Therefore, alternative text describing visuals is important.

5. Support your Staff

With the excitement of a new tool we often forget that people are what make the library great. Staff interacts with the tools and patrons on a daily basis. Management should lead staff through changes including providing plenty of training and the support of management. This includes management and staff realizing that time should be scheduled for Web 2.0 activities the same way reference desk time is scheduled. Saying staff will work on it “soon” does not cut it, “soon” never arrives.

6. Put it in Writing 

Every website needs a privacy and security policy. Web 2.0 websites also need a content policy. These polices should be in a prominent place at the top of the main page for each  Web 2.0 tool. Policies should follow known standards and be clearly written in plain language. If users sign up for a service, they should be informed about their, and the library’s, rights and responsibilities, and of any limitations.

7. Spread the Word

Even if you do everything else right, a website must be known. Don’t be afraid to let people know about your Web 2.0 projects through some old-fashioned communications.

Encourage local media to write articles and run public service announcements.

Create “Web 2.0 ready” banners and pins, and hold a kick-off party to show users what they can do now with these new tools. Include door prizes for users that explore and create content using Web 2.0 tools.

 Considering these questions does not guarantee success but by following these suggestions, your Web 2.0 project is likely to be more effective, outliving anything that is simply thrown up. Remember if it is worth doing, it is worth doing right.