Few decisions cause a library director to fret more than choosing a new integrated library system (ILS). A new ILS is expensive in money, staff, time and stress no matter what you acquire. Additionally, the wrong choice can bear costs in morale with lasting consequences. Sometimes it is easy to identify which ILS is wrong for you - the contract costs are too high or maybe the features are not present that you need. But, too often selecting the right one is like going to a car dealership where everyone speaks in tongues and the price lists are encrypted.
This is the result of a decade of market disruption. Once upon a time proprietary ILS vendors were not optional. Picking the right ILS was fraught with danger but not conceptually difficult. Two changes in the market have had an enormous impact. One of these, the growth of applications as services has added new options to the ILS selection process. However, it has been the growth of open source ILSes, such as Koha and Evergreen that have made it necessary to rethink the selection process.
Choosing between an open source and a proprietary solution is not a choice between peaches and pineapples. Frequently, it is assumed that the two types of ILSes cannot be evaluated by the same criteria. In fact, they can be. Although they result from radically different economic models and divergent philosophies, in the end both are products and services that can be defined by a library's needs and resources for the purposes of acquiring. Four major criteria must be compared - product cost, features, communities and support. Until open source disrupted the ILS market one could safely ignore communities. The community of a proprietary ILS product might have added value but it was unlikely to either make or break the selection of an ILS. Now community plays a much more important role but that will come after we look at the other criteria.
Perhaps the first thing to dispel is the myth that open source should be discussed as the cheap option. The wise library administrator will realize that while many of the best things in life are free, your ILS isn't going to be one of them. Your cost won't always be in legal currency. I have met staff so traumatized by a bad migration that they are still visibly shaken years later by what is now a stable and reliable tool. The library has paid an ongoing price in terms of post traumatic stress and that cost can be too high. The best migration is pointless if the library's experience falls apart within a year or two causing the whole thing to happen again - an experience I've seen happen with both open source and proprietary.
Each of the four criteria can have multiple metrics as well as multiple vectors to plot them on for both a migration and on going support. In the end a data set for ILS selection should probably look more like a scatter chart than a report card. Now, can we simplify the process? The answer is yes. A detailed consideration would be worthy of it's own book but by taking a few conservative shortcuts we can sketch a road map for your selection process in a period of time that isn't comparable to earning another master's degree. For example, we will assume that you have the same vendor handle a migration as ongoing support. This will not be a road map for the adventurous. This is for those whose boards will require that all core functions work on the day of go live with minimal surprises. And being conservative does not exclude you from an open source solution.
First, do a needs assessment. This is the point at which many upgrade processes fail. Rather than say something like "we need acquisitions" or "we need EDI" do use cases and narratives. These should create an unambiguous picture of your needs. Be careful to not attempt to recreate your existing ILS. This is the point at which libraries realize how deeply embedded their current ILS is in their operations. The documents you produce at this stage will be used extensively in working with vendors. Be honest about what you need and what is merely on a wish list.
Now, find your vendors. Don't even worry about the ILS itself yet. That may sound heretical in an ILS selection process but you need to safeguard from fixating on a single product and not evaluating honestly. Fixate on your needs instead. Some vendors will support multiple ILSes and at this stage you are looking at who can provide support during a migration and ongoing. Look at each vendor's ability to support hardware, provide reliable access, and expertise with the ILS, their ability to find solutions, their training resources and expertise at setting a system up. Do yourself a favor and look in depth at their experience with data migration - it is surprisingly hard to do well. Do not let a vendor make vague promises about your data. Looking at vendors before solutions may seem to be putting the cart before the horse but in the long run the greatest frustration most libraries have with an ILS doesn't stem from software but support. At this point you should also rank yourself as a vendor to see if you want to fill some of these support roles yourself. Be honest about your ability to sustain support. Many libraries begin projects that falter when key personnel leave because the skills are not part of the institution.
Many open source advocates argue that support is an inherent advantage of open source. Some libraries delay leaving an ILS they are unsatisfied with the support of due to the stresses of migration. If you use a vendor for support of an open source ILS they cannot lock you into the ILS itself. Once your contract is up, if you leave a support vendor and extract your data you can import rather than migrate your data into a new system. That ease of changing support vendors without changing software means that open source support companies have to compete on the basis of support because the threshold of difficulty for the library leaving is reduced by orders of magnitude.
The next step is to define what kind of support contract you want. Do you want a local install with minimal support, do you want local with remote administration or perhaps an application as service where you sign a check and everything is just made to happen. At this point evaluating yourself, as a potential vendor, will help you determine if you want to exclude yourself. A product supported fully by a reputable vendor with skilled support staff is what you're looking for. Increasingly, the choice most libraries make is buying an application as service. Vendors can take advantage of high capacity Internet connections and big virtualization systems to achieve economies of scale and offer remote hosted ILS services much cheaper than a library can locally offer it. But, you may have factors, such as response times needed, which make a local installation more attractive. Knowing what kind of support contract you need you can begin looking at the packages offered by the vendors and dramatically simplify the rest of the process.
Next, make two lists to look at support and features separately. Vendors need their feet put to the fire to answer if they can fill your needs, which is why the use cases and narratives are critical. Find out what the vendors' uptime guarantees are, what their response times are and what tiers of support they offer. For example, do they handle user interface level troubleshooting, will they do custom development to solve issues, or do they simply do systems administration? What services do they offer during the migration? Can they extract your old data? Can they offer project management or training? Will they offer documentation? Now, some of these resources may originate in part or whole from a community but at this point worry about the availability through the vendor and their obligation to you to make it happen. List the support levels of each vendor. Go back to Buying An ILS 101, call references and do every other thing you would do with any big-ticket purchase.
Parallel to support, review the ILSes themselves and isolate what software will be viable for you. Make sure the vendors support those features and how you want to use them. I've had clients spend a lot of time preparing to move to a system only to have their vendor say, "we don't support serials" even though the ILS has the functionality. Return to those use cases and narratives your staff developed earlier. While sharing the use cases get a detailed analysis of what your narrative experience using the ILS(s) will be. If they can build a comparative scaled system (number of patron, bib, copy records, etc..) for you to test against this is critical for applications as services. More than one library has been burned by not seeing their data run at scale and not doing hands on features testing.
Think about future features too. Will there be things you can't anticipate or live without? Will the new social network that everyone gushes over be critical two years from now? Can the company you are working with provide you with development options? If not, then open source may provide you with other kinds of development paths depending upon the community surrounding it. What about wish list features? Maybe like William Henley you want to be the captain of your own soul, or at least ILS. Ask yourself if you want to make changes to the software and control those changes in the future. If the answer is a firm yes, then you probably want an open source ILS and will need to allocate resources for development. Don't automatically discount a proprietary vendor but giving you that control is not usually a part of their business model.
It is also worth asking if you want to be part of a consortium. Although really large resource sharing consortiums aren't unique to open source they do seem to be more common with growths in the Evergreen community, like SCLENDS. Materials sharing may or may not be on your agenda but adding to an existing installation has a lot of advantages including a built in local community to draw on.
Since applications as services are delivered over Internet connections it is important to know the impact they will have on your connection. Prolonged profiling will tell you when you may have interruptions in service and what delays in response time you may have. Map obscure phrases like "ping times" and "drop rates" to real measurements like "it will take 2 seconds to check out an item." Often time, work flows can be adjusted to handle the increased latency from moving an ILS from inside your network to remote hosting but an unexpected impact like that can heavily damage morale. This is a time to bring in heavy-duty network expertise and make sure they go over issues with a fine tooth comb.
Finally, we get to every library's least favorite topic that isn't protected by confidentiality laws: budgets. Take those support options and the ILSes by the vendors you find acceptable and map them against how much you have to spend. Any that you can't afford, toss. What you're left with is ILSes that will work for you, companies you can trust to support you and an experience you can afford. Be wary of rushing into support contracts for applications as services though. Compare your costs across the lifespan of the longest contract you would have to sign - which should be three years. A longer contract than that which locks you in should be a concern. Make sure there are guarantees about maximum rate increases and reasonable rates for extracting data.
Many an ILS has been chosen because the library administrator feels overwhelmed. An implementation by the current ILS vendor can seem like an easy and safe choice. That is a poor assumption to make. In the course of development or corporate acquisitions sometimes the upgrade path defined by a vendor is actually to a whole new product. When that happens an upgrade is really a migration. So, donÕt be deceived by the potential level of difficulty of the project. Vendors like to define upgrade paths because they know many local governments provide clauses that allow organizations to upgrade without going through a competitive bid process. ThatÕs also how you can get stuck doing two migrations in two years Ð something no one wants to do.
At this point you may be ready to select an ILS but you should take one more step. So far we have flattened out the modern twists to ILS selection and used a model built on common sense. The next criterion is not a leap into uncommon sense but it is much harder to define. Evaluating community requires the administrator to understand how their staff as professionals will interact with a larger community rather than perform workflows. Community is not an open source specific criteria though it might be more central to those ILSes. The communities of proprietary ILSes can be hampered or facilitated by the corporation linked to the ILS. Open source ILSes are built by their communities but may still have large corporate presences. When evaluating those dynamics don't frame the discussion as business versus community, as that's a false comparison. Evaluate the businesses as members of the community by their actions and consider that when developing a picture of the whole community.
As you investigate vendors, how they interact with communities might tell you something about the character of the company. Does it allow for independent user groups and conferences? Are there emails lists and public forums? Are there places to share and ask questions of others who use the ILS? Some proprietary ILS vendors have encouraged these things and allowed outside repositories for documents. In open source communities these are the norm. Do not underestimate the value of community. Not only do ILS communities help you make the most of one of the largest pieces of your infrastructure but also an active engaged community can be invaluable for the professional development of your staff.
Look at your resources and ask if you are the kind of organization that is ready to be part of a larger community or if you prefer to play alone on your own ball field. Sometimes it is the larger libraries that are less prepared to be strong community members because they are accustomed to making decisions as an independent entity. In the end you may choose to leave community out of your considerations for an ILS selection. However, at least some awareness of the larger community should always be there, to compare experiences with a vendor at the very least. If you are using an open source ILS vendor and you successfully vetted them they should be involved in the community and may be a gateway to you becoming involved in the future if your priorities change.
At this point you have decided on the viability of a given ILS migration and looked at communities as added value. Do you need a tiebreaker query? If you do look at what your gut tells you. The truth is that for all of our development as a species we still sometimes process information subconsciously and have gut instincts that lead us well. Do you have a philosophical leaning towards open source? Does one vendor click as a partner?
If you are willing to endure some hardships you can play fast and loose with this process. Risks can pay off but it's a luxury most boards don't give their directors. Open source succeeds where it is the best solution, not because of philosophical biases just as commercial software succeeds when it does so on quality, not on spreading fear, uncertainty and doubt about competition. As we look critically at these solutions, their vendors and communities we also have to look to the future. Mark Twain said a sure way to look a fool is to try to predict the future. But we need a sense of how the future of these ILSes will unfold since we will be tied to one once we make that selection. Communities and companies can be filled with amazing people who can make all the difference, and they can fall apart. Engagement with partners in companies and communities are where we will the future unfolding. We need to remain aware of these dynamics - they are often why we end up moving to a new ILS after all.