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.

My del.icio.us bookmarks for March 12th through March 29th

These are my links for March 12th through March 29th:

  • News Spot
  • How to Resolve a Conflict at Work – A brief but helpful outline of tips for resolving work-related conflicts. Most of this I’ve already known about but it is helpful to have them reiterated.
  • Thomson Topic Locator Version 1.2.0 –
  • Assembly Quest: My history with “open brethren” – An interesting post by a self-described member of "exclusive brethren" that discusses differences and similarities between "open" and "exclusive" brethren.
  • Voyager Server Utilities –

Merger fallout

Last week about 45 employees from Endeavor lost their jobs as a result of the merger with Ex Libris. Among them are friends and former co-workers. I am not surprised that some were laid off; what surprises me is why some were laid off and others kept their jobs. Some who kept their jobs don’t deserve it, in my opinion.

What else is clear from the merger is that not much aside from Voyager will be retained in terms of products from the Endeavor side of the equation. It appears that for example, Meridian customers will be migrated to Verde; Discovery: Resolver customers will be migrated to SFX; and Discovery: Search customers will be migrated to MetaLib. At least that is my understanding at this stage. Oh, I forgot: There is one other Endeavor product that appears to have staying power: Journals Onsite. I suppose the installed user community for that product as well as for Voyager was just too strong to ignore or alienate.

It is a weird situation. I’m still getting used to saying ‘Ex Libris’ instead of ‘Endeavor.’ I wonder how many customer libraries will actually migrate to new products at a time when many are already overstretched in terms of time and resources devoted to complex information management systems. I wonder about those employees from Endeavor who remain and how they will manage the transition and uncertainty, and the same thing from the Ex Libris side. Time will tell.

Selfishly I am thankful I was able to leave Endeavor when I did, and I am thankful to have a job, period.

Well, well, well

I was surprised to see the announcement, published earlier this afternoon, that Endeavor and Ex Libris would merge under the ownership of Francisco Partners, a private equity fund with a focus on technology. In fact, I am still going through all of the ramifications of this news and haven’t quite figured out what it might mean. For a more cogent and unbiased view, be sure to read Andrew Pace’s writeup about the news at his Hectic Pace blog.

I can’t be unbiased about this news. Not only have I worked with and implemented most of Ex Libris’s product suite, I have worked as an employee of Endeavor, most recently from September 2005 through April 2006 (and for about three years in an earlier stint with the company). I have friends in both organizations.

The news caught me off guard. Upon reflection, though, it shouldn’t have. My personal opinion is that no matter what the language of the press release might use, this is not truly a merger of two separate companies. Instead it is a de facto acknowledgement of defeat by Elsevier, Endeavor’s parent company, in the longstanding battle for the high-end, large academic research libraries market. Ex Libris has certainly won the war, with mostly better products, better technology, and better support. My sense is that Elsevier has not received a satisfactory return on its investment in Endeavor; that its strategy, at least as I could see, to utilize Endeavor’s technology to boost its capability to deliver its content, has not been successful.

Of course there is almost a complete overlap of products between the two companies and so the speculation will center on which products will survive. Andrew Pace makes some predictions and I think he is probably correct. We could both be wrong but I agree with Andrew, that Endeavor’s Meridian and Discovery products will soon be history. What is less certain of course is the fate of Endeavor’s Voyager product vs. Ex Libris’s Aleph 500. Each system has its strengths but overall I believe that the Voyager product has a slight edge in terms of ease of implementation and use. We’ll see what unfolds in the coming months. (I have absolutely no “inside” knowledge about any of this. I am just as much in “guess mode” as anyone else.)

More personally, I wonder what will happen to many friends and acquaintences who work for Endeavor. As one would expect, the press release does not go into detail on this aspect of the deal except to say that Ex Libris’s existing Chicago office will be moved into the office space currently used by Endeavor. That office space is right next to O’Hare airport and is ideally situated for easy access for customers. I seriously doubt that everyone’s jobs will be retained as a result of this merger. I especially doubt that the development staff at Endeavor will remain intact. This is the area where I used to work.

It has been clear to me for some time that something big needed to happen at Endeavor if it was to survive. Now I know what that “something” is!

Professionalism, or lack thereof

In the past few weeks there were a lot of emails posted to a closed discussion list for customers who use Endeavor’s Voyager system that expressed various degrees of dissatisfaction with the software and the company. The discussion grew out of the need for customers to vote on enhancements for the next major release of the software. The list of possible enhancements was pared down quite a bit and another mitigating factor was that the enhancement process had been defunct, basically, for the past few years.

A lot of excellent points were made by many of Endeavor’s customers. Among them was the desire for more open, interactive communication between the company and its customers. One suggestion for improving this communication was for the company to publish a blog. There had been some movement on Endeavor’s part to do this last year but for whatever reason, nothing happened.

Basically what people see as problematic with the software, and how it is supported, parallels in many ways what I’ve heard customers of other systems vendors complain about. Customers feel that basic functionalities aren’t there, that development of improvements is slow to non-existent, that there is an increasing sense of lack of return on investment. Sometimes I get a little frustrated with those who complain so much about Voyager because many of them seem to think that Voyager is far worse than other systems when in fact, it isn’t. Not that it is “the best” or perfect; far from it. But there is a bit too much of the “grass is greener on the other side of the fence” type of thinking. For instance, there is a perception that one main competitor, Aleph 500 from Ex Libris, is a much better product. The fact is, it has its particular strengths but it also has a large number of flaws, and Aleph customers find a lot to complain about, too.

I am not saying that we as customers should just be satisfied with the software we have. Rather, I am saying that we should realize that it’s not just one vendor or one product in the library marketplace that is problematic. As far as I can tell, having worked closely with three or four of the major systems vendors’ products, none of them is even close to being excellent at what they are supposed to do. I strongly believe that we need to continue to push for improvements but also understand a broader perspective about library software and the forces at work in the marketplace. Sometimes we as customers get so caught up in our own pet peeves and widgety functionality that we think is so important, that we completely lose sight of the broader landscape in terms of shifts in technology, in market demand, in user needs and expectations, etc.

The worst part of it is that many of the discussions we have with or about the vendors we use only serve to expose a pretty ugly side to our profession. For years on the closed discussion list for Voyager there has been a small handful of librarians who take every opportunity they can to make this discussion list a stage where they express how much they think they know and how much they despise the company and/or its software. I don’t have a problem with people expressing frustrations and venting in face-to-face venues. I also think a lot of what they have to complain about is legitimate and noteworthy. What I have a huge problem with is the lack of professionalism these individuals show in how they approach the problem. I believe that the dialog between library vendors and customers should be mutually respectful with a focus on issues rather than individuals, and with a balanced perspective of give-and-take. Sadly, in some quarters, this is completely lacking and as a result, the behavior and attitudes of a few librarian colleagues taints the whole profession.

My big news

My big news is that I will shortly begin a new job. Yesterday I accepted a job offer from one of the world’s largest pharmaceutical companies, to manage their library’s systems as well as their technical services operation. I am really excited about this opportunity. I’ve worked for two large, academic research libraries, for a small college library, and for a library systems vendor. Now I will find out what it’s like to work in a corporate library environment. I submitted my resignation today at Endeavor Information Systems, Inc., and my last day there will be May 17. I start my new job on May 22. In the new job I will still be tied somewhat to Endeavor but in a new and different way. This corporate library uses most of Endeavor’s software products, including Voyager (a traditional integrated library system consisting of an online catalog and other stuff), Meridian (their electronic resources management system, or ERMS), Discovery: Finder (formerly, ENCompass for Resource Access, which is a federated search tool), and Discovery: Resolver (formerly, LinkFinderPlus, Endeavor’s OpenURL service).

This opportunity is a real answer to prayer. Now my family and I have a sense of direction, of where we’re going in the coming months. It’s going to be pretty stressful because we will be looking for a new home, a new community to live in, and moving again. At the same time I will be starting a new job, teaching a graduate course, and finishing up a book chapter.

Some interesting sessions at EndUser 2006

I may work for Endeavor but I do not intend or want to be a free cheerleader for them here. Yet I can’t resist mentioning a list of presentations planned for EndUser 2006, Endeavor’s upcoming user group conference, that are squarely in the “sweet spot” of discussions that have been going on about social software in libraries (a.k.a. Library 2.0), making library data work harder, and using the ILS in new and innovative ways:

  • Ross Singer (well known as maintainer of the Dilettante’s Ball blog, frequent speaker and commentor on library/systems issues who works in library technology at Georgia Tech) will give a presentation on “Declunkifying your Z-Server: Implementing SRW/U, OpenSearch and other web services to your Voyager server”
  • “Social software (instant messaging, RSS, blogs, wikis, folksonomies, social bookmarking) and libraries” will be discussed by Edward M. Corrado of The College of New Jersey, and James Robertson of NJIT (New Jersey Institute of Technology)
  • Daniel Forsman of Örebro universitet will talk about “Extended features in webvoyage – forwarded searches and RSS feeds”
  • Adrienne Butler from Oklahoma Dept. of Libraries is going to give a presentation on “Writing A Search Plugin for WebVoyage”
  • “Mending the Gap between the Library’s Electronic [and] Print Collections Using [the] Semantic Web” will be the focus of a talk given by Amanda Xu, Andrew Sankowski, and others from St. Johns University

I am really looking forward to these and other presentations.

Questions about tagging

I don’t think I’ve mentioned this before, but I have been experimenting for a while now with tagging my posts using Technorati tags. I’ve settled on using Flock as my preferred blogging platform, at least in part because of the ease with which I can associate tags and categories with each post. (By the way, I also love the way that I can use Flock to access my Flickr account and associate tags with my photos and/or quickly insert them into blog postings.) I’ve mentioned in the past that I am somewhat dubious about tagging, but I also can see some of its benefits from the user perspective. The jury is still out. In the meantime, I have some tagging questions that are nagging me. Maybe I am simply exhibiting the anal retentive stereotype of someone with a library cataloging background, who knows?!

  1. Does it matter that there is frequent divergence in how others are tagging the same concept or entity? I’m not even talking about using different (more specific or more general) words. Even when we use the same terms, we can input them in different ways. To illustrate, here is one recent example I’ve come across: “library 2.0″ (what I’ve used) vs. “library2.0″ (notice that lack of a space in between “library” and “2.0″). Then there is the use of capitalization or lack thereof. E.g. “Library 2.0″ vs. “library 2.0″. I don’t view this as mattering that much, but it may matter in certain situations.
  2. I love the concept of developing a tag cloud, and am intrigued by the work of some to tie this into the library online catalog. See, e.g., the work being done at the University Libraries at George Mason University using subject headings extracted from a Voyager system. This is just one example; there are many others. What I am not clear on, though, is whether this is really the answer or solution to the inherent disparity in tags used by different people. Does this disparity not really matter? Of course, there has always been disparity in library cataloging, even when using subject thesauri like LCSH.
  3. It seems that different services develop their own sets of tags. E.g. there are Technorati tags, del.icio.us tags, Flickr tags, and even LibraryThing tags. It seems logical to think about über tags, that allow the user to map between disparate systems. Is that (or would that be) beneficial? A sort of Dublin Core for the tagging world? Is anyone developing something like this or even thinking about it, or am I way off?

There are other niggly things that I can’t think of right now, but if I can remember them later, I’ll jot them down and ask about them in a separate post.