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.

Ex Libris adds social web features

I was glad to see an announcement that Ex Libris has added social web features into its latest release for Aleph 500, its integrated library system. (Seen via Lorcan Dempsey’s weblog.) I wish that this was something Endeavor Information Systems and other library systems vendors in the research and academic library marketplace were more proactive about including in their systems instead of leaving it to savvy users to create this stuff on their own. Or at least actively encourage user development of stuff like RSS feeds, tagging, etc.

RSS and Aleph online catalogs

A lot of people in the library blogosphere get excited when an ILS vendor announces some kind of RSS capability for their online catalogs. I wanted to mention here some excitement of my own when I recently discovered some interesting RSS functionality for the ILS I maintain (Ex Libris Aleph 500), developed by Peter Corrigan of the National University of Ireland, Galway, James Hardiman Library. Peter has implemented this in relation to A9.com’s OpenSearch technology.

See his entry at A9.com and also click here to see a sample search. (Note the orange icons for RSS and Permalink in the upper lefthand side.) Yes, this is cool!

I also read on the North American Aleph Users Group discussion list that the new product manager for Aleph, Katriel Reichman, is actively tracking and investigating the use of RSS in Ex Libris products, including SFX and MetaLib.

Lilly Fund loses 20% of value

An article in the Indianapolis Star reports that the Lilly Endowment lost 20% of its value last year. This is big news because this is the largest source of charitable funds in the whole state, and the Lilly Endowment is particularly generous to educational institutions like the one where I work. In fact, Lilly gave us millions for faculty development recently. This is only the latest grant they have given us. They also gave the money that allowed our library consortium to purchase a new integrated library system (Aleph 500), OpenURL resolver service (SFX), and metasearching tool (MetaLib). Part of the grant is also paying for software (ContentDM) and hardware for member libraries to build digital library collections.

Lecture @ UIUC GSLIS

Yesterday I was able to go to UIUC GSLIS at the invitation of Kathie and Bill Henderson to speak to their Technical Services Functions class. (This is the same class that I teach in online form in UIUC GSLIS’s LEEP curriculum.) They’ve invited me every year for the past 14 years. Each time I go, I thoroughly enjoy the time with their students.

The topic of my talk was “The Times, They Are a Changin…or, How to Thrive in an Age of Chaos and Opportunity in Technical Services Librarianship.” What I try to do is give a quick overview of my career path thus far, and then focus on electronic resources as the “hot” area. We usually spend a lot of time talking about user expectations in this era of the Google Mindset, and how libraries are coping with the demand for online full-text while simultaneously struggling to manage the “traditional” collection. I demo’d the ERM system that we developed at Taylor, known as the Taylor Periodical Administration System (TPAS), and also talked quite a bit about OpenURL and metasearching technologies.

There are about 14 students in this class. Some years the students really get into a good discussion, while other times, they seem content just to listen to a lecture. I prefer interaction and was pleased that this year there were a lot of questions. Especially in recent years, students have expressed some apprehension about the future of technical services librarianship, or uncertainty about job prospects in this specialty. This topic came up tangentially in yesterday’s session. One student asked, given what we had been talking about in terms of the predominance of e-resources and vendor tools that libraries are stuck with, what is stopping vendors from selling or marketing directly to researchers? (We had also been talking quite a bit about Google Scholar.) I thought this was an excellent question. It really asks the question, are libraries relevant anymore? Why should libraries assume they are even part of the equation for information consumers? Have libraries given up way too much ground, ground that they can never expect to recover? Very interesting questions. We spoke about the decision made by libraries about 100 years ago to stop trying to do article-level analytics in their cataloging practice, and how that resulted in the whole development of vendor solutions in the form of abstracting and indexing tools. Those tools have then developed into online form in the last 20 years or so, and then have been developed further to provide aggregated full-text content. We have lost control (if we ever had it) of the means of access to our resources.

Overall it was a very stimulating time and I ran out of time trying to cover everything. I wish we had had all day!

The Henderson’s had made lunch and invited Linda Smith, Associate Dean and one of my former professors, to eat with us. It was nice to chat with them about various things. One of the things I noticed this time in my campus visit was that development of various areas of the campus continues at a rapid pace. Some areas are hardly recognizable anymore, they have changed so much since I was a student there.

Periodical Management Systems

A while ago I mentioned that I had written an article for Serials Review on periodical management systems, and that I had been working for quite some time on such a system at my library. This topic continues to be of interest to a lot of folks. Recently there have been two or three threads on SERIALST related to this issue in which the predominant opinion seems to be that Serials Solutions walks on water. I haven’t used their services — the whole point of developing something locally is/was to do what they or competing services do for cheaper and do it better — but they seem to get consistently good press!

I have a meeting on Friday with a subset of PALNI libraries to demonstrate what we’ve been doing locally with this homegrown system. My hope is that at least a few other libraries within our consortium will join in using it. One good reason is that we all share SFX and the Taylor Periodical Administration System integrates SFX data, making it somewhat distinctive from other setups I’ve read about. My ultimate hope is to make the system freely available as open source because I believe that there are many libraries out there who simply can’t afford services from Serials Solutions, TDNet, Ebsco, and others. I think this is particularly true of many small college and university libraries, as well as some public libraries. A huge amount of credit for the whole system goes to one of my student workers, Matt Wissman, who has worked on it for over two years now. He is really gifted in database design, advanced web development, and other areas, and I am really going to miss him when he graduates next year.