Running head: DRUPAL AS AN OPEN SOURCE CMS FOR LIBRARIES

yieldingrabbleInternet και Εφαρμογές Web

7 Δεκ 2013 (πριν από 4 χρόνια και 25 μέρες)

88 εμφανίσεις

Running head: DRUPAL
AS AN OPEN SOURCE CMS FOR LIBRARIES


1

Drupal as an Open Source
Content Management System
Solution for Libraries

Anne Gresham

ILS 534
-
S70: Library Technology

Dr. Jinging Liu

Fall, 2011

October 16, 2011

g
reshama1@owls.southernct.edu
DRUPAL AS AN OPEN SOURCE CMS FOR LIBRARIES


2

Abstract


Drupal is an open source content management system (CMS) with several advantages for
libraries. The p
latform began as a personal project, but has since expanded to include an
immense international community of users and developers. Drupal may be installed in an entirely
open source server environment, and its licensing requires continued adherence to the
open
source model. This has allowed significant development and extension of the platform by its
users. Drupal works as a CMS by separating form and content. Content is stored as “nodes,”
which are separate from HTML coding and even from HTML pages. Nodes
are presented using
CSS and PHP
, allowing developers to change appearance of content without altering the content
itself. Drupal includes taxonomies and menus to assist in organizing and managing content. It
also fosters collaboration and interactivity thr
ough workflow management and social media
integration, and adding content requires no programming skill. Drupal has been used in libraries
to create public websites, staff intranets, catalog discovery layers, library database organization
and search functi
onality, digital collection management, and manuscript submission capabilities.
The use of Drupal in libraries has positive implications for libraries’ continued relevance and
ability to provide virtual services.
DRUPAL AS AN OPEN SOURCE CMS FOR LIBRARIES


3

Introduction


Open source software is becoming an increasingly popular option for libraries, from ILS
products to institutional websites to staff intranets. Library websites, formerly static entities
composed by either an in
-
house “web master” or a third party contracto
r, are now expected to be
portals of information that provide an interactive, user
-
friendly experience enriched with social
media and Web 2.0 technologies. Drupal, an open source content management platform, is a
powerful tool for creating these sorts of o
nline environments. This paper will provide an
overview of Drupal, outline its capabilities, and discuss its utility in libraries.

Overview of Drupal


Drupal was created in 1999/2000 by Dries Buytaert, as a way for a group of
college friends to stay in to
uch. From its beginning as a simple message board, Drupal evolved
into a full fledged platform, which was publically released as open source software in 2005
(Wiersma, 2009). Since then, Drupal has grown into an enormous international user and
developer co
mmunity, including 228 countries and 181 languages as of October 10, 2011.

Drupal is a web
-
based content management system (CMS). Webopedia defines CMS as

software or a group or suite of applications and tools that enable an organization to seamlessly
cr
eate, edit, rev
iew and publish electronic text” (2011). Other open source CMS products include
Wordpress and Joomla, and commercial CMS products include IBM Lotus and Micros
oft
Sharepoint. Libraries
publish several different types of content authored by va
rious library
departments, including bibliographic data, policies, events, marketin
g materials
, and staff
documents. CMS products have the potential to assist libraries in organizing and managin
g this
diverse content
. However, Drupal supports a wide range
of activities in addition to basic CMS
functionality, many of which are highly relevant to libraries.

DRUPAL AS AN OPEN SOURCE CMS FOR LIBRARIES


4

Drupal may be freely
downloaded under a GNU General Public License, meaning that
anyone is free to make changes to the source code provided they make thei
r modifications
available to others (Drupal, n.d., Wiersma, 2009). This has resulted in a highly extensible
platform; Drupal users share their modifications as “modules,” 8,845 of which are currently
available on the Drupal website. These modules include e
xtensions for e
-
commerce, project
management, syndication, and more. Thus, new Drupal users may immediately benefit from the
creativity and technical skill of the vast Drupal development community.

Developing in Drupal


Drupal
-
powered sites differ from traditional HTML websites in that content and form are
entirely separated; instead of including content between HTML tags, Drupal uses server
-
side
scripting to store content in a database and inject it into HTML code, which

then works with CSS
to present that content in the presentational theme of the user’s choice or design. This allows
developers to drastically alter the appearance of the site without altering the content itself (Austin
& Harris, 2008).


As a CMS, Drupal
allows presentation of both static and dynamic content on a single
page (Farkas, 2008). It accomplishes this by using content “chunks”, referred to as “nodes” in
Drupal, rather than using fully formed HTML documents (pages) as its base units of content.
No
des are highly flexible and may appear on multiple pages or share a page with other unrelated
nodes. The default “content types” (node types) are pages and stories, but there are many other
more complex content types, such as polls, RSS feeds, or shared ca
lendars. Developers may also
create new content types as needed (Austin & Harris, 2008).


Drupal also includes means of manipulating and organizing content through taxonomies
and menu structures. Taxonomies may be hierarchical or freeform. For example, Li
brary of
DRUPAL AS AN OPEN SOURCE CMS FOR LIBRARIES


5

Congress Subject Headings might be imported as a hierarchical taxonomy, or author names
might be used in freeform taxonomies, which would allow all works by a particular author to be
viewed on a single page (Austin & Harris, 2008). Taxonomies coul
d also be used to provide
multiple views of database records, e.g. alphabetically or by subject (Rosenthal & Bernardo,
2010). Menu structures in Drupal provide an additional layer of organization in that they can be
configured to appear based on permission
s. This allows a single site to provide multiple services
to its user groups and deliver information based on user profiles (Austin & Harris, 2008).


Drupal is also very conducive to collaborative and/or interactive site structure. Wiersma
(2009) notes tha
t Drupal installations tend to overturn traditional web master roles by allowing
greater staff participation in content creation. Workflow management in Drupal can facilitate
content review processes, and any staff with word processing experience would be
capable of
using the WYSIWYG (“what you see is what you get”) Drupal content editor, thus extending
content creation beyond the web services department (Morton
-
Owens, 2011). In terms of
interactivity, developers may allow comments on every node element on
a site if they wish
(Austin & Harris, 2008). Furthermore, developers without advanced programming knowledge
can easily integrate blogs, wikis, share calendars, or forums into a seamless online user
experience (Farkas, 2008).

However, there are some potenti
al disadvantages to using Drupal. A steep learning curve
has been noted, especially with unique Drupal jargon. Additionally, while the modular,
community
-
driven design of the platform is usually an advantage, some modules may not be
updated with the same f
requency as the core Drupal system. Therefore, installing a system
-
wide
update may cause some independent modules to crash (Nelson, 2010). Furthermore, as with any
open source product, “free” may not necessarily mean that Drupal is without cost. The Drupal

DRUPAL AS AN OPEN SOURCE CMS FOR LIBRARIES


6

website includes a “Marketplace” area, containing contact information for commercial firms who
specialize in Drupal installation, design, training, and technical support. If a third party
contractor is not employed, Drupal may incur serious costs in terms

of staff time and effort.

Drupal in Libraries


Drupal has been widely a
dopted by libraries. 100 public libraries, 3
school librari
es, 57
academic libraries, 8

special libraries, and one library consortium are listed on the Libraries
Drupal Group page (201
1). This page includes 19 library
-
related modules, which include
s

Z39.50 protocol modules, link resolvers, ILS bridges, and more (Libraries, 2011). In 2010,
Druplicon (Drupal’s annual conference) included its first program targeted for libraries
(Fitzpatri
ck, 2010), signaling its widespread adoption and interest in the library community.

Several prominent libraries and related organizations use Drupal to power their public
websites. The American Library
Association moved

to Drupal in 2010, and the organiza
tion
described the use of Drupal as “align[ing] us with libraries’ community
-
focused values” (“ALA
Drupal Migration Company Selected,” 2010). The ALA Connect and MentorConnect pages also
use Drupal to great collaborative effect (Coombs, 2009). The Ann Arbo
r Public District Library
installed Drupal to foster interactivity between the library and its patrons (Rogers, 2005), and the
New York Public Library launched a Drupal
-
powered site in 2010, citing Drupal’s modular
design as a means of maintaining a contin
uously evolving web presence (Oder, 2010).


Moreover
, libraries have found other uses for Drupal. Ann Ar
bor District Library
develop
ed

SOPAC (Social OPAC), a
Drupal
catalog discovery layer. SOPAC is freely available
for other libraries, integrates with an
y ILS system, and some commercial firms support migration
and installation (Coombs, 2009). Similarly, McMaster University in Ontario uses Drupal not
only to provide access to its digital collections, but also to create and catalog digital items
DRUPAL AS AN OPEN SOURCE CMS FOR LIBRARIES


7

(Coombs, 20
09). The University of Alabama Library uses Drupal for both its public website and
its staff intranet (Battles, 2010). The Florida Gulf Coast University Library developed a Drupal
module for searching library databases, which included content fields specif
ic to database
records, e.g. coverage dat
es (Rosenthal & Bernardo, 2010)
. Simon Fraser University

Library

used Drupal to create a submission method for theses and dissertations (Coombs, 2009).


While a full
-
featured Drupal Integrated Library System has no
t yet been attempted, it
would be a feasible undertaking, especially given the significant Drupal library functionality
already in place. Web design firms who specialize in Drupal installations notwithstanding,
Drupal already competes with major commercial

systems (Microsoft Sharepoint, other
commercial web design firms), and its growing library following may soon have implications for
the traditional ILS market.

Conclusion


Drupal is an excellent example of the power of open source development. It has ins
pired
a diverse development community to extend its application beyond that of a traditional CMS,
and its collaborative nature is reflected in its ability to deliver specific content and behaviors to
targeted users. Libraries have embraced Drupal as an ele
ctronic tool and repurposed it to suit
library needs. Future library involvement in Drupal appears to be inevitable, as Drupal offers a
non
-
proprietary platform for providing access to information in a world in which information
resources are becoming incr
easingly privatized. Drupal not only engages library patrons, but also
engages libraries as developers in a global effort to provide information access through online
user experience.



DRUPAL AS AN OPEN SOURCE CMS FOR LIBRARIES


8

References

ALA Drupal Migration Company Selected. (2010).

American Li
braries, 41
(11/12), 12
-
13.

Austin, A., & Harris, C. (2008). Adding "Stuff" to a Drupal site.

Library Technology Reports,
44(
4), 10
-
14. Retrieved from EBSCOhost.

Battle
s, J. J. (2010). Designing and building a collaborative library intranet for a
ll.

Journal

of
Web Librarianship, 4(
2/3), 251
-
263. doi:10.1080/19322909.2010.500570

Becker, D. A. (2010). Adv
entures in Drupal: Designing a l
ibrar
y website u
sing a CMS.

Online
(Weston, Conn.), 34
(5), Retrieved from EBSCOhost.

Content management system (2011). In
Webo
pedia.
Retrieved October 14, 2011 from
http://www.webopedia.com/TERM/C/content_management_system.html


Coombs, K. (2009). Drupal done r
ight.

Library Journal
, 134
(19), Retrieved
from EBSCOhost.

Drupal (n.d.). Retrieved October 10, 2011, from
http://www.drupal.org


Farkas, M. (2008). CMS fo
r next
-
gen w
ebsites.

American Libraries, 39
(10), Retrieved from
EBSCOhost.

Fitzpatr
ick, S. F. (2010). Drup
al: The change we n
eed.

American Libraries, 41
(6), Retrieved
from EBSCOhost.

Libraries

(2011). Drupal Groups. Retrieved October 10, 2011 from
http://groups.drupal.org/libraries


Morton
-
Owen
s, E. G. (2011).

Editorial and technological workflow tools to promote website
q
uality
.

Information Technology & Libraries, 30
(3), 91
-
98. Retrieved from EBSCOhost.

Nelson, W. (2010). Some T
t
houghts on Drupalization.

Searcher, 18
(5), Retrieved from
EBSCOhost.

DRUPAL AS AN OPEN SOURCE CMS FOR LIBRARIES


9

Oder, N. (201
0). NYPL launches new, Drupal
-
based web s
ite.

Library Journal, 13
5(2), 16.
Retrieved from EBSCOhost.

Rogers, M. (2005). Ann Arbor's web site maximizes blogging s
oftware.

Library Journal
,
130
(14), 27. Retrieved from EBSCOhost.

Rosenthal, D., & B
ernardo, M. (2010).
Creating a library database search using
Drupal.

Code4Lib Journal, (10),

2. Retrieved October 9, 2011 from
http://journal.code4lib.org/articles/2920


Wiersma, G. (2009). Building

online content and c
ommunity with Drupal.

Collaborative
Librarianship, 1
(4), Retrieved from EBSCOhost.