Statistical Report for Voyager

2011 Survey Results 2010 Survey Results 2009 Survey Results 2008 Survey Results 2007 Survey Results
Product: Voyager Response Distribution Statistics
CategoryResponses 0 1 2 3 4 5 6 7 8 9 ModeMeanMedian
ILS Satisfaction154 1 4 17 5 18 27 56 22 4 76.077
Company Satisfaction154 1 1 4 10 12 16 22 54 27 7 76.217
Support Satisfaction152 3 7 11 5 18 23 47 30 8 76.167
Support Improvement149 2 2 4 7 13 62 16 19 15 9 55.525
Company Loyalty154 5 2 12 10 30 17 34 24 20 76.107
Open Source Interest152 25 16 16 16 12 21 17 13 10 6 03.794

CategoryTotalYespercent
Considering new ILS154 5938.31%
Considering new Interface154 6139.61%
System Installed on time?154 13889.61%
Product: Voyager Response Distribution Statistics
CategoryResponses 0 1 2 3 4 5 6 7 8 9 ModeMeanMedian
ILS Satisfaction123 4 3 10 25 25 42 13 1 76.016
Company Satisfaction123 1 5 5 11 18 30 39 13 1 75.906
Support Satisfaction120 4 4 4 11 21 32 23 20 1 65.796
Support Improvement118 3 3 6 11 52 14 18 11 55.335
Company Loyalty121 2 3 4 5 13 27 15 28 17 7 75.776
Open Source Interest120 11 16 16 14 9 18 9 8 9 10 54.074

CategoryTotalYespercent
Considering new ILS124 4032.26%
Considering new Interface124 6451.61%
System Installed on time?124 10685.48%
Average Collection size: 1095582
Product: Voyager Response Distribution Statistics
CategoryResponses 0 1 2 3 4 5 6 7 8 9 ModeMeanMedian
ILS Satisfaction164 8 10 9 31 39 41 22 4 75.916
Company Satisfaction162 1 1 7 12 17 23 35 45 19 2 75.736
Support Satisfaction162 1 3 11 15 12 20 26 44 25 5 75.726
Support Improvement153 2 5 8 8 18 54 17 17 18 6 55.275
Company Loyalty160 11 5 5 11 14 22 20 42 17 13 75.516
Open Source Interest164 24 19 23 11 8 23 16 19 12 9 03.974

CategoryTotalYespercent
Considering new ILS164 3118.90%
Considering new Interface164 8954.27%
System Installed on time?164 14286.59%
Product: Voyager Response Distribution Statistics
CategoryResponses 0 1 2 3 4 5 6 7 8 9 ModeMeanMedian
ILS Satisfaction87 6 5 8 5 23 21 17 2 66.016
Company Satisfaction87 1 1 5 9 5 16 15 23 11 1 75.596
Support Satisfaction87 1 4 3 10 5 13 19 14 14 4 65.576
Support Improvement0 not applicable
Company Loyalty87 5 3 10 7 7 12 11 13 13 6 75.145
Open Source Interest86 10 7 10 6 4 14 7 10 4 14 54.665

CategoryTotalYespercent
Considering new ILS87 1921.84%
Considering new Interface87 4045.98%
System Installed on time?87 8395.40%
Product: Voyager Response Distribution Statistics
CategoryResponses 0 1 2 3 4 5 6 7 8 9 ModeMeanMedian
ILS Satisfaction83 1 3 12 3 17 19 22 5 1 75.516
Company Satisfaction110 1 5 9 14 13 17 24 21 5 1 64.935
Support Satisfaction108 4 5 9 13 14 14 18 19 10 2 74.885
Support Improvement0 not applicable
Company Loyalty105 16 2 11 13 9 25 9 8 6 6 54.155
Open Source Interest107 10 8 12 12 13 12 15 12 6 7 64.354

CategoryTotalYespercent
Considering new ILS111 2421.62%
Considering new Interface111 5347.75%
System Installed on time?111 10.90%

Comments

Unfortunately, price will be a major factor in what system we decide to go with in the future. (Type: State)

While it may be beneficial to analyze the current ILS market, lack of funding support blocks us. (Type: Academic)

In process of implementing Ex Libris' Primo (Type: Academic)

On the discovery interface question, you neglected an option. We have purchased one, but have not yet implemented it. (Type: Academic)

We are still working out glitches with Primo Search and Discovery System. We implemented around [...]. It has been more difficult and tedious than envisioned to pull together various databases into one search. (Type: Academic)

Actively using the [...] implemented VuFind interface. (Type: Academic)

We are very disappointed with ExLibris' change in policy to not help customers with their Solaris OS upgrades. This has left us out in the cold and scrambling to find a contractor when this service used to be provided for an extra fee. We need the OS upgrade before we can upgrade Voyager. ExL is also now performing all Voyager upgrades on Israeli time which is not helpful to a US customer. These two factors will push us off our local server and onto their hosted solution next year, which seemed to have been their plan all along... (Type: Academic)

Part of consortial search for discovery product; highly dependent on budget considerations and ongoing state merger of management of higher education entities (community colleges and state universities) (Type: Academic)

ILS's have outlived their usefulness, but we are stuck with our current ILS until the consortium decides to make a change. Were we free to make the decision on our own, we would be migrating to a cloud-based system within the next year. (Type: Academic)

Answers above are based on membership in a large academic consortium. The future ILS plans are still very much in discussion with no firm date for concrete planning. (Type: Academic)

Development of Voyager seems to be limited to Primo functionality only, reinforcing interdependency of the products. No benefits for Voyager customers who do not have Primo. (Type: Academic)

e had the money we would get EDS tomorrow. We currently have EHIS - EBSCO's federated searching product. (Type: Academic)

We have a partial discovery interface using Xerxes 2.0 as the front end to our suite of Ebscohost databases, but the [...] libraries are looking at a systemwide subscription to one of the more comprehensive back-end indexes. (Type: Academic)

We are currently involved in a Shared LMS Services feasibility study for the whole of the country of Wales in the UK. (Type: Academic)

It's hard to believe library automation started out so bad, and hasn't advanced much over a couple of decades. Library data has a stunningly low level of complexity compared to medical, stock & bond, etc. data--yet Ex Libris et al. seems not to muster the computing skills of even a high school senior or university freshman. The ILS is the public face of our libraries, and the current pack of vendors are reinforcing the opinion amongst the public that libraries are dinosaurs. (Type: Academic)

We moved to a hosted catalog--advantages still outweigh the disadvantages (lack of control, frustration during downtime). (Type: Academic)

We moved our ILS to be hosted by ExLibris. The hosted system has been more unstable than we anticipated. (Type: Academic)

Many of our ILS decisions are consortially driven. (Type: Academic)

Lack of staff hinders our ability to consider open source products. (Type: Medical)

We moved our Voyager instance to the cloud this year (hosted by Ex Libris). While I am glad to no longer have to worry about maintaining the physical server and the backup, there have been trade-offs, most notably having to deal with timeouts caused by connecting through the university firewall. We strongly considered moving to OCLC Web Scale Management Services, but we preferred Primo to WorldCat Local and decided it would be better to use one vendor for ILS, discovery, and link resolution. We also judged Ex Libris' support and business strategy to be superior. (Type: Academic)

We're currently working on bringing up Worldcat Local. We'll go 'live' in the spring of 2012. (Type: Academic)

We are seriously considering moving to ExLibris' hosted catalog service when we reach the point of having to acquire a new server. (Type: Academic)

ExLibris hosts our system which takes some headache out of the situation. We're planning on review of options for new system in two year time frame. (Type: Academic)

We are gathering information on our next system now. The economy may determine when we switch systems. (Type: Academic)

No vendor is addressing the needs of small academic libraries like ours. We have looked at open source possibilities, but the major vendor, LibLime, does not inspire any confidence at all in their competence or trustworthiness. And it appears there would be no cost savings by going to open source--either we would pay for significant IT support in-house or we would pay a vendor like LibLime as much or more than we currently pay ExLibris for the commercial ILS. We are interested in the possibility of hosted ILS, such as OCLC is moving towards, but again there doesn't appear to be any cost savings there. We trade off cutting our in-house IT costs with higher payments to the outside vendor. (Type: Academic)

We'd like to add a discovery layer and are looking at low cost options. (Type: Theology)

We're excited to be rushing into the 21st Century with Voyager. The latest version now has the ability to send SMS messages to customers - we shall encourage people to start purchasing cellphones now! Seriously, Voyager is showing its age very much, and everyone is keen for something new - which actually gets serious and sustainable support from the vendor (i.e. not just enough to keep it limping along until everyone can be switched to the new product). There are factions in the library that have been pushing for a couple of years to change and want to do it yesterday, and there are other factions that are wanting to wait a bit longer and see how the "next generation" products just coming on to the market will fare. (Type: Academic)

[...] Library does not expect to be at the decision point for a next generation ILS for at least one, but likely two more years. We are working hard to "get our house in order" to try to be as ready as possible for whatever our next ILS is. (Type: Academic)

Recently implemented Primo. Committed to implementing Alma, probably in 2013. (Type: Academic)

Voyager continues to get the job done, but the primary reason we still use it is that we get an excellent price through our local consortium. If our consortium changed vendors and the price stayed similar, we'd change with them. (Type: Corporate)

Moving to e-formats, so item counts are not as relevant as in the past (Type: Medical)

Based on RFP, consortially, we are expecting to implement a resource discovery product sometime in Spring 2012. (Type: Academic)

Dissatisfied with ILS product phone support of upgrades to OS and required applications (MS Office) (Type: Academic)

Our current ILS is very flexible and because of this is VERY complex. It requires a huge number of man hours to support! (Type: Academic)

User community with Voyager is robust and can be a good source for support; third party add-ons offered by community members. (Type: Independent Research)

ILS