Tuesday, January 27, 2009

Thing 3: Blog Search Engines

Hello, world.  After spending the weekend totally out of commission due to illness, I find myself returning to 23 Things @ NEFLIN feeling very behind.  All my good intentions to do Things 3 and 4 over the weekend in flames!

Oh, well.  No time like the present.  So back to business.

I spent a couple of lunch breaks last week exploring Technorati and some time this morning on Google Blog Search, comparing features, ease of use, relevance of search results, etc.

My search term was bengal cats.  This is a fairly new breed of domestic housecat that is becoming very popular because of the beauty of their exotic markings, which may resemble those of a cheetah, a jaguar, a snow leopard, or an ocelot.

Due to their growing popularity and inherently photogenic nature, I thought there would be a million blogs from which to choose.  But not so.  I did find some good ones (NOTE: define good as interesting to me) but not nearly as many as I'd have thought.

I have to say I found Google Blog Search infinitely easier to use than Technorati.  Technorati seems to be universally praised as among the most used and useful blog search tools, and I'm sure it is, but I found it not as transparent as I would have liked.

It appears to have been thoughtfully put together, with a plethora of features, the value of many of which I'm sure will become apparent to me in time.  I will definitely be back to explore Technorati further.  It just wasn't giving me the number of useful search hits I was expecting.

With a general search, the search term bengal cats returned nearly 800 hits, mostly blogposts that mentioned a bengal cat somewhere in the text rather than a blog devoted to the subject of bengal cats.  I sampled a few of them, but this was too large a pool.

I did a bit better with Technorati's advanced search when I entered my search phase into the find posts tagged field.  I got less than 70 hits--few enough to actually browse through.

I liked the videos that popped up.  There are a couple of hilarious ones featuring bengals vying for an exercise wheel: "Bengal Cats Fighting for the Exercise Wheel" and "3 Bengal Cats on Exercise Wheel."  I could watch those all day.  (I could also have found those simply by going to YouTube.)

I did come across one useful blog  which also publishes a magazine called Bengals Illustrated.  (They claim to have a swimsuit issue.)  Basically eye candy for bengal buffs.

My cavil is that I came across this one indirectly, in a link on one of the not-so-useful blog sites I visited.  The Bengals Illustrated blog did not come up on Technorati on its own.  Disappointing, as this was the most relevant site I found using this search engine.

Actually, besides the magazine and the exercise wheel videos, the two most worthwhile posts I encountered on Technorati were one entitled "Thirteen Rules for Dealing with Sociopaths," where a bengal cat is mentioned as the hapless victim of a neighbor's hyper-aggressive nonbengal cat) and another in which the blogger (Michael M) concludes that there is a 78% chance that his cats are plotting to kill him.

While funny, everything except the Bengals Illustrated blog were not exactly on topic.  Worse, they took a lot of digging to find.

Thank heavens I tried Google Blog Search next.  It was reassuringly simple to use and, for the bengal cats search at least, yielded more useful results more quickly.  Four relevant blogs popped up on the first page of search results.  Subsequent pages of search results were not as helpful as the first, but at least I got usable results fast.  For a beginner like me, that's important.

I think for now I'll probably turn to Google Blog Search for quick-and-dirty results and try Technorati when I need something more highly refined.  Quick forays into Blogpulse, Bloglines, and Ice Rocket yielded no useful results.  I look forward to exploring these further and trying out some of the other Blog Search Engines, but I feel I've spent enough time on Thing #3 and must forge ahead to Thing #4.

Enough said!


Sunday, January 18, 2009

Thing 2: Figuring Out Just What Is Web 2.0?

Thing 2 in 23 Things @ NEFLIN consisted of a viewing a YouTube video, a blogpost, and an online journal article, plus several extras (a series of five journal articles, another video, and a Wikipedia article).

It took me about five hours to complete: 3.5 for the reading / viewing and 1.5 for the blogpost.

I can see that if the time commitment is similar for future elements in 23 Things, I'm going to have to do them all at home on my own time.  There just isn't going to be time at work.  I find this troubling.

Now for my reactions:



The Stephen Abrams Kicks Off 23 Things at Murdoch University Library Video

I was interested to hear about all the new technologies Mr. Abrams is already incorporating into his life.  He must be rich and have oodles of free available time.

When the interviewer asked Mr. Abrams how a 23 Things participant might find time to explore the various technologies, he mentioned having previously smoked three packs of cigarettes a day before quitting.

A pack of cigarettes contains 20 cigarettes.  Three packs contain 60 cigarettes total.  If Mr. Abrams did indeed, as he stated, find 7 - 15 minutes per cigarette, that totals 7 - 15 hours per day spent smoking.

Mr. Abrams implied that all of us have hours and hours of time in our daily lives similarly devoted to unproductive pursuits that, if redirected to 23 Things, could enable us to participate without too much inconvenience.

I must protest.  I don't doubt Mr. Abrams' statement that he smoked three packs a day.  I'm sure he did.  But smoking is an activity that can be conducted while doing something else.  One can smoke while one works, while one drives, while one eats, etc.

If one gives up smoking, one still has to work, drive, eat, etc.  So the question becomes, if one gives up smoking, can one participate in 23 Things while still working, driving, eating, etc.?

I venture to say no.  23 Things is something to which one must give one's full attention.   So what exactly am I supposed to give up to make time for 23 Things?

My private life contains almost no discretionary time as it is.  If there's no time at work, I may not be able to finish the course.  This realization bothers me. 



John Blyberg's BlogPost about the Library 2.0 Debate

The main questions seem to be: Is Library 2.0 real?  Is it a big deal?  Is it inevitable?

I confess I don't quite see what the debate's about.  Web 2.0 is happening all around us.  If libraries don't adopt current trends in technology and adapt themselves to social expectations, we'll become irrelevant.  Nobody will use us.  What's to debate?

What I found even more interesting than the blogpost itself was reading through all the commentary at the end.  Interesting, but time-consuming.  Again, I find my thoughts turning to whether or not I'm going to have time to devote to 23 Things.



"The Ongoing Web Revolution" an unattributed article from Library Technology Report 43.5 (Sep - Oct 2007 issue)

I thought this article stated the case for Library 2.0 pretty clearly.

The two most interesting aspects for me were:


(1)  The video entitled "Web 2.0 . . . The Machine is Us/ing Us" by Michael Wesch, which I thought demonstrated the new accessibility and link-ability of information via the Web wonderfully well in contrast with the constraints of traditional print technology; and


(2)  The mention of Gene Smith's "Social Software Building Blocks" (identity, presence, relationships, conversations, groups, reputation, and sharing) along with the fundamental question, "How can library systems and library Web sites include these building blocks?"

These seven factors are just exactly what our users want, need, and expect.  It seems to me that our job is to figure out how to revamp library services to deliver them.



"Web 2.0: Where Will the Next Generation of the Web Take Libraries?" in Next Space: The OCLC Newsletter, No. 2, 2006 issue.

A.  "Away from Icebergs" by Rick Anderson

I like the three icebergs Mr. Anderson mentions:

(1)  Traditional print collections at the expense of other, newer types of collections.  I agree that libraries don't need as many books as they once did.  Other collections need funding, too.

(2)  Librarians as teachers.  Again, I agree that library staff don't have time to give the public in-depth, one-on-one tutoring on how to use library resources.  We need to choose resources that are self-explanatory and very easy to use so as to maximize both our own and our patrons' time.

(3)  The traditional "Come to Us" model of library service.  Again, I'm in complete agreement here.  Libraries no longer exercise the information monopoly they once did.  Our customers don't have to use us.  It would behoove libraries to make our services as inviting as possible and position them where potential patrons are most likely to encounter them and use us.  (Remember the old adage, "Location, location, location"?  Right now, that location is online.)


B.  "Into the New World of Librarianship" by Michael Stephens

Mr. Michaels's new world of librarianship sounds like a utopian ideal in an Obama-esque, "Yes, We Can" watershed era of dramatic change.  I'd love to work in a library such as the one he describes!

Empowered staff.  Progressive change.  Fiscal responsibility (as opposed to the unbridled consumerism of "technolust").  Transparency.  Accountability.  Sounds good!

Unfortunately, I wonder if the higher-ups at most libraries trust staff enough or give them sufficient credit to allow this to happen.

My unhappy impression of many other libraries, garnered from a few conversations and limited reading, is that most managers and administrators instruct their (often very bright, energetic and motivated) staff to shut up, do as they're told, and stop making suggestions.

Strangling feedback has, in my observation, been the first act of many new managers and administrators.  I think that's a pity.


C.  "To More Powerful Ways to Cooperate" by Chip Nilges.

This article advocates boldly for "Harnessing collective intelligence" for collaborative revision of libraries' missions and services.  I'm all for it.

I've heard this sentiment expressed elsewhere as, "None of us is smarter than all of us."  I have a little bit of trouble parsing that, so I like to reword it as, "No one among us is smarter than all of us working together."

I also love the idea of networking all libraries into a searchable WorldCat with no authorization required.  Resource sharing is so much more efficient than separate collections.

Ditto the idea of allowing users (not just library professionals) to collaborate in the library community cooperative.  Yes!

Mr. Nilges's third and fourth points ("release lightweight services" and "build better data") didn't resonate with me as immediately as did his earlier points.  But maybe I was just getting tired.


D.  "To Better Bibliographic Services" by John J. Riemer

This article was all about the need for federated searching to access all the many sorts of databases (a.k.a. information storage systems or "silos") in order to:

(1)  Make their data more efficiently available;

(2)  Make it available in nontraditional (nonlibrary) settings;

(3)  Incorporate Amazon.com and Google features (e.g., reviews, tagging, etc.) that users want / need / expect;

(4)  Simplify the creation of metadata; and

(5)  Eliminate reduplication of effort.

To all these points, I say, "Rock on!"


E.  "To a Temporary Place in Time" by Dr. Wendy Schultz

Dr. Schultz asserts that Library 2.0, like all trends, is transitory.

According to her, Library 1.0 offered books as commodity.

Library 2.0 seeks to package the commodity (meaning information / books) into product with librarians cast into the role of "experienced tour guides."

Library 3.0, she predicts, will offer service via Web 3D (virtual world technology) with librarians as VR information coaches.  These avatars will have the potential to become celebrity "superstars" based on the quality of their service.  That's a neat thought.

Another key point Dr. Schultz made is that despite the rise of virtual reality, bricks-and-mortar storefronts will continue to exist "if they offer a compelling experience."  (I.e., one that is authentic, humane, experiential, impassioned, relevant, and participatory.)

I found this point fascinating, because the litany of the seven attributes of a compelling library experience echoed eerily a list of personal core values I came up with in a recent library-related workshop I attended.  These are just the things a job needs to have in order for me to find it satisfying!

Finally, Dr. Schultz postulates that Library 4.0 will offer experience, becoming a sort of art salon, aesthetic environment, dream society, gymnasium of the mind, idea lab, and / or knowledge spa that will absorb and incorporate all previous library incarnations.

I loved all those descriptions and found her vision extremely exciting.  It's along the lines (though much more complete and better articulated) of something I--and I'm sure many others--have been thinking over for some time now.

Why does the library have to change (become something wholly other than what it already is)?   Why can't it simply grow?

As a child matures, does he metamorphose into an entirely new and alien being?  No, he's still recognizably who he always was, there's just more to him now than there used to be.

When the electric light bulb was invented, did candles suddenly (or even eventually) cease to be?  No, they're still around.  They work fine.  They're still good, and we still use them.

I like the idea of the library growing, becoming more complex, more varied, more user friendly.  I think that's a lot more accurate description than the more abstract and rather sweeping descriptor change.

Change can mean a lot of things, not all of them good.  I think growth has a much more positive connotation.



"Library 2.0" in Wikipedia

This article speaks of Library 2.0 as featuring user-centered and participatory library services, where information flows back from users to the library instead of using the old uni-directional information flow of previous models of library service.  (I.e., Library 1.0.)

I agree that this is one of the hallmarks of Library 2.0 and also one of its most positive characteristics.

However, I'd also like to see more information flowing from staff and increased participation by staff as well as by users.  By virtue of their unique experience, staff are ideally positioned to give very valuable input into the transformation process libraries are currently undergoing.

In order to be able to do this, however, staff will have to be enabled to participate: not only encouraged to do so, but given time to do so.  Inviting staff to participate in 23 Things or Library 2.0 is exciting, but even more important is allotting them time to participate.

Right now it looks like I'll be doing 23 Things entirely on my days off from work.  Oh, well.  Who needs family interaction, personal hygiene, or sleep?  The Internet calls.

Saturday, January 17, 2009

Thing 1: Setting Up and Registering My Blog

Getting started with 23 Things @ NEFLIN by setting up and registering my blog was a little bit traumatic in that it took much longer and did not go as smoothly as I had expected.

Despite good intentions to dive in on Day 1 (Monday, 1/12), I could not find a moment to even log into the NEFLINs23Things blog until Friday (1/16).

Even then, the two-hour lunch break during which I had planned to accomplish Thing 1 evaporated in the face of multiple interruptions and contingencies requiring my urgent attention.  Alas.

I left work at 6:30 p.m. having barely managed to read through the instructions!

Undaunted, I raced home and bolted dinner while conscientiously rereading the directions.  My first pass had been so fragmentary, I was afraid maybe I'd missed something important.  Luckily, I hadn't, but this took a while to establish--and I was champing at the bit! 

After logging onto Blogger, establishing a Google account went fine.  I also enjoyed the Common Craft Show video on what a blog is.  I found it concise, informative, and charmingly low tech.

So far so good.  Things seemed to be getting back on track.

Then I encountered difficulty with the blog creation process.  Augh!

Thinking up an interesting, original name was time-consuming.  (The first several I tried were taken.  Rats!)  My family were interested in what I was doing and kept up a constant barrage of questions and suggestions which were alternately helpful and distracting.

At a couple of points during the process, I found I needed to back up and correct an earlier entry.  This seemed at first to be going okay.  I was allowed to proceed forward again after typing in a new squiggly word.

However, at one point, the system just seemed to seize up.  It wouldn't let me go any further forward, insisting that the name I'd finally chosen (after dutifully checking availability) was unusable.  It was about 9:30 p.m.  I was tired, frustrated, and fried.

"I'm starting over," I announced brokenly.

"We're going to bed," my family said, their electric toothbrushes buzzing.

"Fine.  Be that way," I muttered, closing my window and logging back into Blogger in despair, expecting to have to do it all over from scratch.

But I didn't have to!

By some miracle, my blog existed, named the name I had chosen.  My display name was wrong--the last change I'd made hadn't taken--but by stumbling around through the Profile settings, I was able to correct it.

I'd been assigned some sort of default template, having never made it that far in the process, but I was able to select a new one easily in Layout.

That done, I quit while I was ahead.  It was 10 p.m.  I was a basket case.  But I had a blog.

The rest is all denouement.  I logged back in the following day.  Tinkered a little with profile and settings, uploaded a picture.  (Fetching likeness, no?)  Then I registered and started posting.

So here I am.  It's done.  As with childbirth, you forget the bad parts.  It was worth it.  I'm looking forward to Thing 2.

The Meaning of My Blog's Name

Welcome to Techgnos, a new blog by an employee of the Alachua County Library District to report on my exploration of Web 2.0 technology through 23 Things @NEFLIN.

So what's up with the funny blog name?  (Say it TEK-nohss.  Ch to be pronounced like k.  G silent.  O long.  Hiss the s.)  Okay, so now it's pronounceable--but what's it supposed to mean?

Well, tech is the first syllable of technology, and gnos derives from gnosis, which means arcane knowledge.  A techno is someone with lots of technical knowledge.  A gnostic is an earnest seeker after hidden truths.

So I guess I hope the name suggests a quest for as-yet-undiscovered technological information, which is what 23 Things at NEFLIN embodies for me.