Cherry Hill has been building and hosting websites for libraries since 1995, and Drupal has been our framework of choice since 2006. We strongly believe in Drupal as the best framework for most library websites and web applications. Our reasons for this belief are described in detail below. Over the years, we have created LibrarySite, a hosted, feature-rich Drupal website solution for public libraries that can be customized based on the specific needs of each library using it. The features in LibrarySite are based on the most common requests we receive from public libraries we serve.
There are many missives on the internet?which compare Drupal with Wordpress, Joomla, or other options, and many of the points made in those discussions reveal?misunderstandings on the part of the author or commenter of what each CMS is truly capable in the right hands. Ultimately, whatever tool you choose for your library will only be as good as the planning you put into the project before you start building your site or features, which is a topic for another blog post, coming?soon.
Why Drupal is great for libraries
The power of?Drupal?is in its customizability. This means that if you can imagine it, you can build it given enough time and resources. Over the years, we have found that every library has different needs, because the communities each library serves are unique. In many cases, the branches within a library system, and the range of demographics the library serves (e.g. young adults, new parents, etc.), are also different. As such, there isn?t a one size fits all solution that will work for every library, so Drupal?s customizability becomes its most potent feature.
The range of?services libraries offer their patrons often include:
- Online catalog searches
- eBooks and audio books that can be checked out online
- Programming, including event registration
- Teens and Kids sections with homework help and targeted services/programming
- Reading lists and book clubs
- Digital collections
- Access to electronic databases to which the library subscribes, some of which must be restricted to users physically located in the library
- Complex content management/editing workflows that allow for an approval chain, or for librarians of a specific branch to only edit their branch content
While it is possible to build a Drupal site with much of this key functionality out-of-the-box, Drupal isn?t really intended to be used in that way. It is up to the site builders and owners to determine how they want these features to work, and to adjust their configuration to those specifications. Many such customizations are straightforward ? and therefore inexpensive ? in the hands of skilled Drupal developers, making it possible for a library to have a highly specific system for a very small budget.
This is largely the result of one of the key aspects of Drupal that makes it an amazing resource for libraries:
The Drupal Community
Many open source tools, including Wordpress, come with vibrant communities. Drupal is built by an international network of developers who care a great deal about the quality of the Drupal product, and who are constantly engaged in reviewing each other's modules, writing?patches and answering questions. Visit the?Drupal.org?support network?with just about any question (as long as it is somewhat related to Drupal), and you will get a response. This community loves to help each other.
A few great resources for libraries using Drupal include:
- The?Drupal4Lib?mailing list
- The?code{4}lib?mailing list
- The?Groups.Drupal.org?libraries group
Drupal4Lib and Code4Lib offer?mailing lists that have active participants from both libraries using Drupal, and developers?(including us) building with Drupal.
Contributed Modules (the Drupal Ecosystem)
Largely because of its prolific community, Drupal boasts an entire ecosystem of contributed modules that extend functionality. While other open source CMSes might offer a larger number of modules (also called Addons, Extensions or Widgets in other CMSes), Drupal developers work together to create more robust and versatile solutions that can be used to address a wide?array of requirements.?
A favorite expression among Drupal site builders is "there's a module for that." And if there isn't, you can create one!
Third Party Integration
Many contributed modules make integration with third party solutions, such as Evanced, LibAnswers and PayPal, relatively straightforward.
Third party integration, however, doesn't end there. Drupal is very flexible for developing with APIs through SOAP, REST and JSON. Additionally, there are larger solutions created specifically for Drupal that are entire third party integrations on their own.
One larger solution of specific interest to libraries is the digital object repository system, Fedora Commons. Fedora Commons can be accessed to make quality digital asset management systems (or digital collections) using Islandora, which provides a Drupal user interface for Fedora Commons. In addition to LibrarySite, Cherry Hill offers an entry level Islandora site for public libraries called LibraryDAMS, in which the bulk of the work is already done for the library.
Other Useful Considerations
There are many other reasons why we stand behind Drupal as our CMS of choice for libraries, including (but not limited to):
- Workflow and user roles: Many libraries require detailed content management workflows, including either the ability to have a draft and approval process for content edits, or restricting access to content editing based on branch and/or audience. Drupal is particularly good at highly customized content workflows and permissions.
- Taxonomy structure:?Drupal's taxonomy structure enables content to be tagged with subjects (called terms in Drupal) that have meaning and determine who sees what content when, and where. This system, used well, also makes it easy to access content based on which terms are relevant to a particular user.
- Relationships between content: It is relatively straightforward to create relationships and dependencies between content. As with taxonomy, this helps users find the information they need more easily, and enables libraries to refine how they present content to the public.
- Powerful multilingual capabilities.
- Built-in caching options for site performance.
- Scalable databases.
- Security:?By design, Drupal sites can be carefully crafted to be highly secure. Additionally,?Drupal's dedicated security team is always on the lookout for possible security holes, which is why the Drupal ecosystem sees frequent security updates for both Drupal core and the contributed modules. The frequency of security updates is a sign of a more, not less, secure system, addressing potential vulnerabilities before issues become viral.
When Drupal may not be right for your library
Drupal is a?powerful solution, and with that power comes complexity and responsibility. It is?possible to have a decent site using the stock Drupal installation profile, but doing so seldom produces the best possible?results.?Drupal is a tool that shines brightest when customized to your needs.
Drupal also comes with a learning curve. While the Drupal community offers many free ways for you to learn Drupal, including local DrupalCamps,?local user groups?and?global training days, your library may not have the time or resources to commit to this learning curve and get the most out of Drupal. There are pre-built and custom solutions that greatly reduce that learning curve, such as our own?LibrarySite solution.
Also, any public-facing?software system will require regular security updates, backups, and monitoring. If your library is not able to commit resources to regular updates and maintenance,?you might consider alternatives?such as Cherry Hill?s LibrarySite hosting, which provides?professional?management, site?security and performance optimization.
More about LibrarySite
We created Cherry Hill's LibrarySite?as a low-cost, easy solution for smaller public libraries with limited resources, as well as a flexible, feature-rich?starting point for more ambitious systems. Learn more about LibrarySite here ?