Del.icio.us + Flickr = Cool Postcards

Perhaps this is another reason to install the del.icio.us extension on your public PCs?

Ed Vielmetti has a sneaky little way to send private postcards to people in your del.icio.us network. It goes like this:

  1. Tag a Flickr photo.
  2. Give it some tags.
  3. Include a For:[someone] tag.
  4. Write some neat descriptions.
  5. Click “do not share” on the top right hand corner of the tag form.

ta dah! Your flickr picture with a nice little description will appear in the person’s “links for you” section.

There’s a screen shot of the procedure in action at Ed Vielmetti’s Flickr Page. Jessamyn has already blogged about this as well.

Ok. So maybe Ed’s idea is a bit marginal. But here’s the kicker — at first it was just a little neato thing. Email by del.icio.us. Then you add Flickr and you have postcards — now you are cooking with gas!

What’s next? How about home delivery of documents using scanned docs? Highlighted. With notes. And stored in your del.icio.us with a comment. And a citation. For a collaborative research paper. There are possibilities here, and barriers (ie. copyright stuff) too. But the cool thing is that users are making services better.

Lots of fun to be had and lots of innovation at the same time. Yum!

Advertisements

Managing the Deli.cio.us Extension Problem

Since I went out on a limb by adding the “Deli.cio.us extension” to my “10 library 2.0 no-brainers” post, I thought I should at least explain a way you can remove the problem with people accessing other people’s bookmarks.

See, with Deli.cio.us, you always have the option to “not share” your bookmarks. If you selected some “not shared” bookmarks and do not either 1) logout or 2) erase cookies after shutting down Firefox, then the next person who uses the computer will have access to your “not shared” bookmarks. Or worse, they could sabotage the account.

So, adding Delicious might mean you should also have Firefox remove all cookies when the system closes. For FF 2.0 you do this thusly:

  1. Tool > options
  2. On the top bar, click “Privacy”
  3. Check “Always clear my private data when I close Firefox” under “Private Data.”
  4. No, you are not finished yet!
  5. Click “Settings”next to the check box you clicked in #3.
  6. Make sure “cookies” “saved passwords” and “authenticated sessions” are checked in the box (actually, it’s probably not that bad an idea to have all of these checked. This _is_ a public computer we are talking about.
  7. You can check the “Ask me before clearing private data” thing if you want. The cookies will not be a toggled option anyway.
  8. Do a tester. Login to your deli.cio.us account with the extension, and then see if you have to login after you restart Firefox. If you do, then it worked!
  9. If you are smart and have your system deep-freezed, you should not have to worry too much about people changing the settings.

Another option is to add “deli.cio.us” to the cookie exceptions list (the “exceptions” button is also in the “privacy” tab).

This, of course, is not fool-proof. But it should suffice to keep unwanted sharing of bookmarks from happening to your average user. Then again, I offer no guarantees here! Take my advice as is, please and see if it works for your particular configuration of computer!

Preparing Ourselves for an Open Source World

I have a lot of things in my mind that relate to the “Slow Library” movement these days.

With the release of the HUGE report on the Economic Impact of FLOSS on innovation and competitiveness of the EU ICT sector, I think Open Source is about to come out of the margins and into the mainstream.

Why? Well, largely because those who are aware of and have the capacity and knowledge to use & support open source software have large competitive advantages over those who use proprietary software.

But one thing that hit home for me, Mr. “Slow Library” advocate, was this recommendation (from the executive summary):

Avoid life-long vendor lock-in in educational systems by teaching students skills, not specific applications; encourage participation in FLOSS-like communities.

One way to apply this concept in the library school world is to teach databases and use different applications (Access, XML/XML-schema & MySQL for instance)  to demonstrate the same concepts.   In the open source world, to teach this way is no longer so cost-prohibitive.

In the Library 2.0 world, it may also mean saying “use Flickr” less and “Develop Online Networking Skills” more.   But how do you explain a skill and isn’t “use Flickr” a means to developing Online Networking Skills?  Learning to balance between applications to acquire knowledge and the necessary skills to store and retrieve knowledge has always been and will continue to be a skill for librarians of all sorts.   Knowledge Management ho!

This also reminds me of an article by Kathy Sierra about Users in “P” Mode.   Using the example of a camera always being in “P” mode, Kathy argues that some technological features are not used by users, not because the users don’t know how to change a mode technically, but because they do not understand why they would want to do it in the first place.

Another good example is anti-lock brakes in a car.   Everyone who can drive a car can use anti-lock brakes (uh — push the brake with your foot).   Not everyone understands what benefits anti-lock holds and in what circumstances someone may choose not to use them.

So, I recommended adding a deli.cio.us add-in to Firefox on public computers.   A neat feature that’s L2 enough, but what can I do to encourage the public to use it?   Sure the public knows how to click a button on a browser.   Most of the even technophobiest public understands how to “tag” — write a word in a text box.   Big deal.   What many customers or patrons may not know is what “tagging” does to improve their information experience.

So, while writing a list of “top 10 no-brainers” all of the sudden [ssp warning] turned this blog into the fastest growing blog on WordPress for January 25 (and the 66th most popular blog for that day)[/ssp], there is a non-tech side to all those applications that is necessary for implementing them effectively.

CMS Playdom — an Offering to Students and “non-John Blyberg” Librarians

Ok. So maybe you read Karen Coombs’s essay on “Building a Library Web Site on the Pillars of Web 2.0” or heard about the amazing things John Blyberg has done in turning your average library website into a fully-functional Web 2.0 integrated blazing super-powered mystify both users and librarians online cool device and you realize somewhere, like a certain goblin named Joshua has wondered that more librarians have to be thinking and understanding more about how a content management system works.

Well, here’s what I’m proposing. I am willing to let some people see what the back-end of Joomla looks like. I know, I know — John uses Drupal, which is also amazing, but Joomla is easier to install for now. I may get into Drupal later, anyway. And besides, Joomla narrowly beat out Drupal for the Open Source CMS Award. In my view, Joomla is better in one way [easier back-end interface] and Drupal is better in another [easier for coders to customize] — but that’s another whole blog post.

Here is my commitment. I am willing to let a maximum of 20 people see and ‘play’ with the backend of a Joomla-powered website on a test-server. You will get:

1. An “administrator” (not super-administrator) account.

2. Some limited willingness on my part to share some tips on how it works (via IM or otherwise).

3. Some willingness on my part to re-install the system if you manage to blow it up.

4. General forgiveness for #3 so long as you aren’t a hacker doing it on purpose.

5. Perhaps a look at some other CMSs like MediaWiki, e-Collab and zencart [and maybe Drupal].

What do I need from you? Just the following:

Send a name, institution name, desired username and some way for me to confirm that you are a librarian or library student at the institution you mention to ryan [underscore] deschamps123 [at] yahoo [dot] com.

That’s it. That’s my contribution to the library world. If I get lots of replies, my priorities will go this way:

1. Local first, then global. (Slow library movement stuff, ya know?)

2. Small libraries, then medium, then large.

3. Students first, then new librarians, then curious seasoned librarians.

That’s it! Just let me know.

My Top-ten Library 2.0 “No-brainers” for Public Libraries

toptenlow.jpg This is fairly straight-forward post. I was thinking about Library/Web 2.0 applications, hearing about projects that seemed to some to be a bit dubious or misguided and occassionally finding people being a bit dismissive in general about Web/Library 2.0.

I have sympathy with some of the Web/Library 2.0 skepticism. Not everyone has the resources, inclination or knowledge-base to develop high-powered services on Second Life or to design library based mash-ups and the like.

So, I thought I’d distill library 2.0 into 10 projects that I say are pretty much “no-brainers.” These are 10 things that are:

  • Low risk
  • Low cost
  • Low effort
  • Sure to provide added benefit to a good number of users
  • pretty much just common sense service enhancements AND
  • not likely to ruffle [needlessly] many technophobe feathers

In my view, if you do these 10 things (or some reasonable facimile) you have satisficed the Library 2.0 moniker sufficiently to say you are “L2.” You can always do more to be more user-centric, but doing these is enough to say you are decent.

Here they are:

1. Include Mozilla Firefox on all Public Computers.

Why is it L2?

It is open source, and has a whole bunch of cool add-ins, many of which are social-software-ish.

Why would my users want it?

Some would want it because Internet Explorer is too wonky and proprietary. I don’t want to get into why, but just trust me on that one. The other big reason is that many of your users may desire ad blockers, javascript disablers, and things like StumbleUpon, and Yoono a cool tool for surfing the web. You may not know or care what these add-ins are, but some of your users do and they will like the fact that they can add them when they visit you.

2. Add the Deli.cio.us Extension to Firefox as part of your suite

Why is it L2?

Delicious is a social bookmarking site. Social Bookmarking = Web2 Social Bookmarking in a Library = L2.

Why would my Users Want It?

It’s pretty simple. With no delicious, users can only bookmark to your PC which will probably get wiped by DeepFreeze the next time your user arrives. With delicious, all bookmarks go to the user’s delicious account. That means he/she can add to and access his/her bookmarks from anywhere. Access to bookmarks = easy access to desired information.

3. RSS feeds for library news and programs (minimum)

Why is it L2?

Well, users don’t have to visit your site to see what you are offering. More control to your user = L2.

Why would my Users Want it?

Is it better to have to go to the store to get your paper or to have it delivered? RSS is like having library and program news “delivered.” You can get fancier than this, but these two things are pretty straight-forward.

4. Have straight-forward guidelines for blogging (including a statement that you encourage staff to blog)

Why is it L2?

By encouraging blogging, you are taking your staff and sending them forth as evangelists for the library cause. By providing guidelines, you will also give people more confidence to express their opinions without fear of trepidation. The guidelines should be fairly simple: 1) respect the privacy of yourself and others, 2) don’t divulge confidential information, 3) don’t plagiarize or do things that are otherwise illegal, 4) be reasonably respectful of others. That sort of thing.

Why would my users want it?

Blogging staff are technically aware and community-engaged staff. Online users will enjoy seeing that their local librarian is blogging. Off-line users will benefit from more technically capable staff.

5. Have some kind of content managey system for staff information sharing

Why is it L2?

Content management is a way to let larger amounts of people add content to a website (internal or external). A wiki is a good kind of content management system, but you could also try something along the lines of an internal blog or other information sharing system. In short, a content management system invites collaboration, that means it’s L2.

Why would my users want it?

Similiar to number 5, L2 products for staff means smarter and more knowledgable staff. Example: say you have a “readers services wiki.” Prior to the wiki, you have to rely on the knowledge of individuals — and usually the ones who are on staff. How many times have you said “oh, this is a fantasy question — how I wish so-and-so were here. . ..”? Well, with the wiki, so-and-so could leave a list of great fantasy books — perhaps with brief descriptions and read-alikes to go with it. That means you can go to the wiki to see what so-and-so recommends for fantasy readers. Even better, “whosawitz” may be another fantasy fan from another branch who can add to the list. Pow — your reader’s advisory power just jumped exponentially.

6. Have a public blog and allow comments

Why is it L2?

Because it invites participation, fair and simple.

Why would my users want it?

Lots of reasons, including but not limited to 1) wanting and input on their library 2) getting answer to questions 3) getting to read interesting comments and how they are responded to 4) feeling like your website is not an automaton but that there are actually people running the show and 5) engaging other library-people in a discussion about their favorite place.

Moderate it all you want, but we are at the age where you need a blog with commenting power.

7. Collaborate with Partners using Google docs or Zoho

Why is it L2?

Google docs is pretty much a wiki with a few added security controls.

Why would my users [actually community partners] want it?

With no fuss over document formats and versions, you will all literally be on the same page. The chat feature is a nice addition as well.

8. Keep a flickr page with some interesting pictures of library programs etc.

Why is it L2?

It’s Flickr and people can see all the wonderful things going on at the library.

Why would my users want it?

Well, they get to see pictures of the library in action and get an idea of what’s going on even if they can’t make it on a regular basis. Further, your library staff (who are now blogging) could reference these pictures in their blogs.

9. Make sure Instant Messaging, Gaming, YouTube or allowed on your PCs

Why is it L2?

Well, it’s not L2 actually, but it is a mandatory requirement of calling yourself L2.

Why would my users want it?

Remember Dirty Dancing and how misunderstanding all those uptight parents were with the rather level-headed and quite remarkable and creative dancing kids? Well, IM, Gaming, YouTube and etc. are doing more for those young brains than you think. The major issues with these tools (1. monopolization of resources and 2. innappropriate use) are not inherent to Web 2.0 services. Got a PUC-potato? Well, restrict their time limits, citing equity of access. Got a porn-watcher? Well, have your internet use policy ready (which I’ll bet a dime a dozen says something about appropriate use in a public space). Don’t blow a positive library experience for the majority because you have a few rule-breakers.

10. Engage teens with technology

Why is it L2?

Engaging teens with technology will almost inevitably lead to using one of the technologies mentioned in #9 in a program or service.

Why would my users want it?

Well, there’s the teen-users who will come to use the library as a place to hang out. Then there are the citizens who will be glad those teens have a place to hang out. And lastly, parents will be happy to see their teens doing something productive, learning new skills and meeting new friends. It’s pretty basic.

That’s that. Do these 10 fairly simple things and you can call yourself L2. It’s not all, but it is enough given limited resources, knowledge or organizational inclination.

Most of these things take few resources on the part of the library. Numbers 6, 9 & 10 probably would take up the most resources, but they are also fairly core services so I think the cost is worth it. Numbers 5 & 7 may even save you resources compared to what you are probably doing in their place. 6 & 9 are probably going to be the hardest to convince management staff who are risk-averse or technically unaware, but they are not huge calls in the grand scheme of things, and the case for support should not be horrendous.

All in all, there are a wide range of Web 2.0 applications that are not risky or costly to implement, and at the same time they are bound to be effective. Even a “costly” web 2 service such as creating a video blog is not that costly in the end (a few thousand for equipment & software and some time to edit the movies). The point here is that you do not have to blow people’s minds to be L2.

Although, of course, I always encourage the occassional attempt at mind-blowing with the right preparation and thought.

Creating The “Right” Network — Using Diversity to be “Slow”

I do not link to Kathy Sierra’s blog enough. She writes amazing and helpful advice about design, coding and well, just making your users happy.

But her recent post, “The Dumbness of Crowds” definitely has me thinking these days about gathering networks and growing yourself. In it, Sierra laments that people have mistranslated James Surowiecki’s The Wisdom of Crowds (a book that my wife has promised me for, of all things, Valentine’s Day) and basically has taken the flavor out of individuals.

She then goes through a brilliant litany of differences between what she calls “Collective intelligence” and “The Dumbness of Crowds.” Here’s an example:

“Collective Intelligence” is about getting input and ideas from many different people and perspectives.

“Dumbness of Crowds” is blindly averaging the input of many different people, and expecting a breakthrough.
(It’s not always the averaging that’s the problem it’s the
blindly part)

Now I’ve written recently on “Me-too-ism” in the Web 2.0 world”, basically arguing that we want people who will be committed to a cause to the extent that they want to shut out dissenting voices. The important thing about that discussion is that you do not necessarily want them to succeed in shutting out those voices. In that article I made a solid claim for the philosopher — the person who will make solid calls on the group behavior and moderate the field.

In other places there have been challenges to defences of “Group Think” as well. The implication is that a diligently critical mind can be the solution to “really bad” groupthink (meaning desiring unity to a violent or propagandic extent) .

My position is that cultures develop and “Group think” is not something that someone can overcome so easily.

Assumptions and “Group think” happen out of necessity — they are a survival mechanism in humans to coordinate behaviors. Humans, even the most solitary ones, are a social animal. We depend on others for our survival. It has gotten to the extent that a disaster tens of thousands of miles away will have serious impacts on my own domestic choices. War in Iraq causes gas prices to go up and I walk to work more.

But I have to agree that we do not want a society that assumes something to be true simply because the majority believe it. Stephen Colbert satirically coined “truthiness” and “wikiality” to poke fun at the very notion that something must be right if some kind of consensus can be built about it. I just don’t think that critical thinking is the solution to the problem. I think that acceptence of diversity (which, I admit, does require some critical thinking — but it requires an open heart more) is the solution.

Acceptence of diversity is hard because it requires that you accept and face those things that make you uncomfortable. When someone sees the world differently from you, the reaction will be fear, irritation, boredom, and anxiety. That’s why I admire people like Norah Vincent. Her book Self-made Man describes her experience of portraying a man and going to the places where she was least comfortable (raunchy strip-bars, bowling alleys etc.) so to understand them better.

That’s what I think bloggers should do to prevent a “bad” Group Think society. The people who make us most upset or uncomfortable might be the best ones to keep us in check in our beliefs. These are the people you want commenting on your blogs (assuming they apply reasonable standards of decency — no threats, needless ad hominems and trolls etc.).

Having groups of people following the same thoughts and assumptions is not a problem. Having everyone with the same thoughts and assumptions (other than broad-based ethical values like “respect for life”) would be bad. That’s why I propose the following for anyone building a knowledge network for themselves.

  1. Read the blogs of those with whom you disagree. Lots of library non-users think librarians are nothing but overpaid book-shelvers. Aren’t these people a better window to our souls than the biggest library advocates?
  2. Welcome dissenters in your own blog. If they contradict everything you say, so what? There’s nothing they can do to stop you from writing your own posts and comments. If they get out of hand, just ignore them and let them have the last word. The last word is not always the best word.
  3. Assume a Charitable Reading of a bad comment, or even better — assume your dissenter is right! Even if you end up being right in the end, your dissenter has done you the favor of identifying gaps in your argument that you may be able to fill.
  4. Befriend the weirdo. There’s a line in The Tipping Point that the most interesting and important people to talk to in a crowd are the people who appear out of place. If you are ever at a meeting of suits and a goth appears, it’s the goth that you want to talk to. It’s the goth that will be able to uncover your own proclivities toward groupthink and sameness. I’m not sure where you find the weirdo in the blog world, but this might be a start.
  5. Deal with illegalities accordingly, but don’t hold a grudge. A grudge is groupthink in action. Worse, a grudge probably also means that you are thinking about your opponent alot more than your opponent thinks about you.

If Web 2.0 emphasizes community, then the blogger needs to think hard about what community means to him or her. In my view community is not a straight-forward “majority wins” kind of world, although the majority probably should win most times. Community to me means arguments and grievances, negotiation and disputes combined with a fair deal of comraderie and friendship. Heck, even throw some love and relationships in there too. The ideal world is one where you get all sorts of views from all sorts of places.

I can only hope that this blog may someday gather this sort of “community” one day.

5 Things in Under Five Words

I’ve been tagged by Kathryn Greenhill for this mutated meme. Five [more] things you didn’t know about me, but in less than 5 words each:

  1. Won the Louis Vagianos Medal
  2. Pho is a favorite snack.
  3. Played necrophile in Levin Play.
  4. I’m a pretty good curler.
  5. Wanna pen a CIL in.

Apologies in advance for tagging these people (no pressure at all to come through on this)! Meredith, David, Jenny, Susan and Walt.