APML stands for Attention Profiling Markup Language.  Its purpose is to permit a standardized way to gather and transfer your interests from site to site across the web.  It is built using XML, and is definitely a new technology that may or may not catch on.  It could become an important element of using the web, because of the benefits it offers to users.

For example, Amazon.com tracks what you purchase, what is on your wish list, and even what you view (while logged in).  If you incorporated this into your APML file (which could be stored with an online service, on your computer or flash drive, etc.) your interests could be applied to other APML-compatable websites.

This has the potential, as with much web 2.0 technology, of creating privacy issues and complications.  It also could save users an incredible amount of time and effort, as resources relating to their interests would gain relevance and become much easier to find.  Think of the potential for searching news sites, link services such as Digg, and many other specialized discovery tools.

And yes, as John Fudrow suggests, it has a lot of potential for libraries.  Imagine how our users could benefit from this, especially when you add “suggested by others who liked this” and other social connectivity tools.

(Note regarding this post:  When you read this post, be sure to read the comments as well.  I did not state my case as well as I should, and end up sounding as though I don’t feel that LibGuides has as much value for libraries as they obviously do.) 

I don’t normally post “negative” about web sites or services; if I am not impressed by something being offered, I simply don’t blog about it. However, I have noticed a really interesting Library 2.0-related offering, and feel that it should be mentioned here.

LibGuides is a truly interesting and useful product. It offers a way for a library to implement many Web 2.0 tools via a service that is remotely hosted and configured, with content and features that you select.

It looks great, in many ways. They include tools for Facebook integration (great for academic libraries), showing RSS feeds on LibGuide pages, and built in instant messaging (IM) capabilities.

Why am I not happy with this offering? Two reasons.

Reason one is their pricing model. According to their FAQ page, their “annual license fee ranges from $899 to $2,499″. This, to me, is packaging Library 2.0 like a database subscription. True, they have done some excellent work in setting up page templates and integrating tools, but why should a library spend that amount of money to rent those services?

Let me provide an example. This blog is run on a hosted web server. The annual fee for this server is less than $50. This provides 1 GB of disk space, plus quite a few built-in tools such as a MySQL database, full e-mail management including listservs, site statistics, and a comfortable amount of site traffic. I have run several different websites on this company’s servers, and have been happy with their service.

What have I run on these sites? Standard web sites, wikis, a blog, a content management system (CMS), listservs, discussion forums, and custom search pages. There are only two things that I have wanted to install that I haven’t been able to, based on their security settings: I can’t host a WebDAV calendar (for shared group calendar software), and cannot install a library automation system, like Koha or Evergreen (so I have to play with Evergreen using a virtual server on my home computer).

Most Web 2.0 software has open source options available. This means that I can select a blog software, download it, install it to the web server, configure it, and there it is. Is this easy to do? Yes and no. Configuration, especially the database settings, can be fairly detailed. WordPress has very good instructions, and if you are comfortable with copying files from one place to another, and can follow a written guide you won’t have much trouble getting a blog up and running.

Wiki? Same type of installation. Want to run a listserv? Don’t need to install anything, just go to the sites control panel and set it up. What I am trying to say is that for $50, time, and some effort, your library can create a web presence that is just as rich as what is being offered via LibGuide.

Reason two, for those of you who are still with me, is their license agreement (Pdf). You pay them, they provide the service on their servers for one year. They can change anything about the agreement, and all they have to do to make you comply is notify you. You own your own data, and they will provide it to you within 30 days of cancellation, if you ask.

These are pretty standard clauses for many services and software. It is actually quite mild compared to some. It still doesn’t sit well with me that open and interactive services are packaged and controlled like this.

Sure, you could try them out for a year, decide not to renew, and only have an xml file with your content and data to show for it. Or you could get a hosted site, start a blog and a wiki (or a CMS with both built in) and build your site from scratch, adding content here and there, adding new programs and technologies as you go.

Even if you hire someone as a consultant to do the installation and initial training (find people in your area who do this, or want to learn… try contacting web design instructors at your local community college for potential contacts), you can do a great deal in a relatively short time span. Even if you spent $500 for someone (and you shouldn’t even need to go that high), once set up the software and technology is yours for just the annual web hosting fee. Just be sure to learn as much as you can about how everything works, and learning what your site’s potential can be.

And after all of this, if you don’t want the hassle or cost of the hosted web service, you can still do many Library 2.0 functions through other sites. Blogs are available simply by registering at Wordpress or Bloglines. Similar options exist for IM. You can find hosted wiki and CMS sites, but these are mostly paid solutions.

I strongly suggest that every library examine their options for the range of 2.0 technology, and adopt those which will best fit your environment. It doesn’t need to cost much; it doesn’t need a limiting license agreement; it does need to give you the flexibility and the power to connect your services with your customers.

And if you want to see a positive review of LibGuides, which highlights the great points of the site, check out BiblioTech Web

Steven Bell – It’s a Mad Mad Mad Mad Web 2.0 World : Hidden Treasure or Just More Pressure? (Powerpoint) (Handout)

The title is adapted from It’s a Mad Mad Mad Mad World, the “epic comedy” film from 1963. He likened our (libraries) search for “Library 2.0″ to the frantic search for the “big W” in the film, even showing a couple of clips.

He recommended a Wired magazine article by Chris Anderson called People Power.

A manifestation of the second-generation web is User Generated Content (which strikes me as a good summation of the change taking place).

Business Week’s June 11, 2007 issue of Inside Innovation has an incredible set of charts showing demographics of those using and generating content.

He recommended an article from the v.25#2 issue of Library Hi-Tech called Taking the information to the public through Library 2.0 (abstract only; sounds like an ILL opportunity).

He pointed out a blog post by David Lee King called How Can We Change the Unchangeable, or David’s Rant.

He showed several video clips of library staff scenarios (think of those training movies you see with acted examples):

• Library Director/Admin reacting to a librarian’s blogging
• Co-workers discussing the possibilities of a Wiki
• Instant Messaging as a library tool

His main points were to try out new technology, be open-minded about staff using technology, and recognize that much of Library 2.0 technology involves a time investment, but is otherwise low-risk (and low-cost).

His caveats were to focus on identifying problems needing solutions, find technology with the potential to solve those problems, learn about the technology, and practice.

He referred to an article in the April 2004 American Libraries titled A Dozen Solutions to all Library Problems (which makes some great points with a dose of humor).

Design thinking – libraries approaching problems like designers approaching problems

Library revolution: designers went directly to patrons – how they use library, what they want to do but cannot, etc. They did not use the library staff as a primary resource for the design.

Stages for implementing change:

1. Reflect, analyze, diagnose and design
2. Imagine and visualize
3. Model plan and prototype
4. Implement

Designing Better Libraries (one of Steven’s blogs)

He used an interesting prop to illustrate increased tension associated with technology: a block of wood with a bolt partly screwed into it… he uses a ratchet to tighten the bolt… increasing the tension.

“Reverse the Technology Ratchet”

• consider the opportunity costs
• Balance experimentation and investment of time
• pick your edge – leading or trail
• identify your compassionate pioneers
• reverse mentoring (relatively new library people training established people on newer methods)
• make a plan and let it guide (but there are exceptions)

Website: Steven Bell’s Keeping Up Website

We must learn to evolve

Example: Change. Deal with It. (a.k.a. Jim Carroll’s squirrel experiment)

He concluded with a quote from David Bishop, Charles Deering McCormick University Librarian at Northwestern University, Evanston, Illinois:

We have watched whole professions go out of business as a result of changes in technology. Libraries are not immune. Change must happen soon and across the board if libraries of all types are to remain viable.

Notes: This was essentially a keynote, and did not go in-depth on any topic. It hit many points, and used a great deal of humor to do so. It was a great start for the conference, and the end quote sets the tone for one of the later sessions.