OCLC tries to checkmate

This past week I heard rumors about pending changes to OCLC’s policy governing use of records contributed to WorldCat. There was every reason to be concerned about these changes even before the details of what they contain were “leaked.” I just finished reading a post by Terry Reese on this topic, and Terry makes very good points. Basically, based on what I’ve read, I agree that OCLC is trying to checkmate the likes of LibraryThing and others by monopolizing control over library-generated metadata. Oh right, I forgot, this is “for the benefit of its members.” Ugh. Please, folks, wake up and smell the coffee on this.  I find it interesting that Terry raises comparisons with Microsoft (and AT&T), something that I’ve done many times in the past.

VuFind @ CARLI

Whoohoo! I was quite excited to stumble upon the news that the CARLI consortium here in Illinois is trying out the VuFind software as a new front end for its Ex Libris Voyager catalog. I had no idea they were doing this; I knew (thanks to one of my students) that they were also trialling WorldCat Local, but I didn’t realize they were also looking at VuFind.

image-0057.jpg

Some initial thoughts: I am especially pleased that a major consortium with some really big library collections is looking closely at an open source solution. I like what I see so far in some of the searches that I’ve done in the system: the ability to tag, cite, utilize the Google Book Search API, add to favorites, etc. OpenURL linking is built in as well.

Applying new lipstick on an old pig

One of my work responsibilities is to maintain the Voyager integrated library system from Ex Libris. A new release (7.0) is now available and one of the features that is getting the most publicity is the new web interface to the catalog. It features dramatic architectural and feature improvements from its predecessor, as well as adding new features that weren’t possible before. The Voyager product manager and folks from Ex Libris customer support have posted several enthusiastic reports on new features to come on the Voyager discussion list (closed to customers only), and I think they are doing a fairly good job of trying to build excitement. Except that all that I’ve heard and seen so far leaves me cold.

Why? Well, although I definitely agree that there is much to like about the new interface, it’s not really that new. During my last stint at what was then Endeavor Information Systems three years ago, I participated in user studies at some existing Voyager customer sites that were based this same interface. The functionality and changes I see in the Voyager 7.0 web interface (a.k.a. WebVoyage) were all designed and finalized, as far as I can tell, three years ago. That’s light years in technology time.

Worse still, the things that are so “exciting” about this new interface (persistent URLs! WHoooHeee! — different “skins”! Oh my! — a truly simple, Google-like basic search! Isn’t that original!) are features that have been available and taken for granted in other systems for years. And they are ones that in some cases have been implemented better than what I have seen so far in Ex Libris’s Voyager offering.

Sorry, but this is just a new flavor of lipstick applied to an old pig. It would take a lot more than this to get me excited about this particular product again.

I detest marketers [Updated]

[I actually wrote this post earlier today and published it. Then I thought better of my initial impulse and unpublished it. Inquiries about the "missing post" prompted me to publish it again but this time I've anonymized it a bit.]

Today I experienced yet another example of Web -2.0 in action. I heard via the [insert a well known integrated library system here] discussion list that a recording of a webinar on the upcoming release was freely available to view. I thought to myself, Ok, I doubt this’ll wow me but hey, since it’s a webinar and freely available, why not take a look? I clicked on the link provided in the email. Big mistake.

First of all, the company who owns and markets [insert a well known integrated library system here], requires anyone who wishes to view this “freely available” webinar to register. Required fields include phone number, email address, and so forth. I don’t know about you but any time I am required to submit this kind of information, my scalp prickles and I think to myself, “Oh yay, now I get on the radar from a sales or marketing person to give me a call.” That’s the last thing I need or want. I just want to watch the dang webinar, ok?! Keep in mind that the announcement about this “freely available” webinar was distributed to a customer-only, closed discussion list. Said ILS vendor already has all of my contact information. Why should they bother me by asking for it again?

Second of all, after I took the plunge and registered, what do I get? An automated message from a marketing/sales person saying basically, “Thanks for registering and we’ll let you know if you can actually view this ‘freely available’ webinar after we review your registration information carefully to see if you are actually worthy of it.” Insert teeth gnashing here.

I strongly regret my action. I don’t need to see this; I was mildly interested, that’s all. I don’t need or care for a vetting process from a company’s product/sales/marketing yahoos. ILS vendor, you have shown in a very blatant way how little you “get it.” Do not EVER make it difficult for a good customer to access and use whatever information he or she needs or wants. Simply provide it with no questions asked. There are many far less obvious ways of doing your job and understanding or tracking customer interest than the way you’ve chosen.

P.S. I received a response from this company when I emailed a much more polite version of the above to the discussion list mentioned above. The marketing person pointed out concerns about sensitive information leaking to competitors and noted that since my email address ends with a .com my registration was scrutinized more carefully as a result. This person also mentioned that registration was deemed necessary because contact information can change over time.

Here is my reply, fwiw: “Thank you for your response. I can understand the underlying methods and reasoning used with this approach, but I do not think they are customer friendly. And that was really my point in raising the issue. I understand the competitive concerns; as you pointed out, I work for a .com also. But really, there are other ways to cover your bases in that regard than what has been chosen. In this Web 2.0 era, customers are used to a much more open and readily available flow of information. Even though corporations try their best to suppress or control information about them or their products, the truth is, they never will succeed in this day and age. And I personally feel that they shouldn’t even really make that attempt. Times have changed and the negative perceptions engendered by a marketing approach like yours may prove far more costly to you than whatever competitive advantage you might stand to lose by being more open in the way you share information.”

The future of corporate websites

I really like this statement by Jeremiah Owyang, The Web Strategist, in a post discussing the new My Starbuck’s website:

“The future of corporate websites enable customers to submit, define, and vote for next-generation products in collaboration with product teams.”

Man, wouldn’t it be nice if this was what we in libraries could experience with our vendors? I am a huge proponent of open source tools in libraries, including open source library systems like Koha and Evergreen. I wonder though if they would be gaining as much ground in the marketplace if library systems vendors were already doing what Jeremiah suggests.