Spreadsheet: 01526083-4d92-4c53-9d31-5480c8ad26b2
Sheet: Main Analysis

Northeastern University Libraries, November 2010
Please see http://www.lib.neu.edu/ALADrupalPoster2011 if you have questions.
The following survey was sent to three email lists (Drupal4Lib, Web4Lib, and Code4Lib)
on 10/20/2010 and 11/01/2010.
Type of Library
Total # | Special | Public | Academic
Size
Academic* |  |  | * Uses Carnegie Classification
Very small (Under 1,000)
Small (1,000 - 2,999)
Medium (3,000 - 9,999)
Large (10,000 - 19,999)
Very large (Over 20,000) | 5 | **One public library answered "over 20,000" using the academic classification rather than public;
 |  | we categorized this as small, below.
Public
Very small (Under 10,000)
Small (10,000 - 24,999) | 2 | **One public library answered "over 20,000" using the academic classification rather than public;
Medium (25,000 -99,999) |  | we categorized this as small
Large (100,000 - 499,999)
Very large (500,000 and over)
Special
Very small (1-9) | 0
Small (10-49) | 0
Medium (50-99) | 0
Large (over 100) | 2
 | 2
Customization level
Minimal |  | v. small | small | medium | large | v. large
Academic | 1 |  |  |  | 1
Public | 1 |  |  | 1
Special | 1 |  |  |  | 1
Moderate |  | v. small | small | medium | large | v. large
Academic | 12 |  | 2 |  | 8 | 2
Public | 3 |  | 1 | 1 |  | 1
Special | 1 |  |  |  | 1
Heavy |  | v. small | small | medium | large | v. large
Academic | 10 | 1 |  | 4 | 2 | 3
Public
Special
Customization in house?
Yes |  | Minimal | Moderate | Heavy
Academic | 21 | 1 | 10 | 10
Public | 2 |  | 2
Special | 1 |  | 1
No |  | Minimal | Moderate | Heavy
Academic | 2 |  | 2
Public | 2 | 1 | 1
Special | 1 | 1
Current level of staff sufficient?
Yes |  | Minimal | Moderate | Heavy
Academic | 10 |  | 5 | 5
Public | 2 |  | 2
Special | 0
No |  | Minimal | Moderate | Heavy
Academic | 13 | 1 | 7 | 5
Public | 2 | 1 | 1
Special | 2 | 1 | 1
Permanent Drupal staff?
Yes
Academic | 22
Public | 4
Special | 2
No
Academic | 1
Public | 0
Special | 0
If permament Drupal staff, what skills?
PHP
Academic | 21
Public | 3
Special | 1
CSS
Academic | 22
Public | 4
Special | 2
HTML
Academic | 22
Public | 4
Special | 2
Graphic Design
Academic | 12
Public | 0
Special | 1
Server Adminsitration
Academic | 16
Public | 3
Special | 1
Other | 7 |  | Database admin, usability testing, JavaScript, Java, Ruby, SQL,
Academic | 5 |  | Ajax,multimedia, Perl, Python, accessibility training
Public | 1
Special | 1
If permament Drupal staff, in which department?
Library Systems | 19
Academic | 16 | (also called Library IT, [NAME], Web Services)
Public | 2
Special | 1 | (dual, in both Systems and Tech Services)
Technical Services | 3
Academic | 2 | (dual, in both Lib Systems and Tech Services)
Public | 0
Special | 1 | (dual, in both Systems and Tech Services)
IT/IS of larger org | 0
Academic | 0
Public | 0
Special | 0
Other | 8
Academic | 5 | Sibling to [NAME] and [NAME], New Media, Reference, branch library, admin, [NAME]
Public | 2 | Technology, Computer Services
Special | 1 | [In Dept] unrelated to IT
If permament Drupal staff, shared or Drupal only?
Shared | 27 |  | Comments: | The answer to 7 is 'both'.  I have one FTE devoted to Drupal
Academic | 21 |  |  | and 2 additional FTE who work in Drupal, but do other non-
Public | 4 |  |  | drupal work, as well, including the proxy server, a
Special | 2 |  |  | Metalib install, and non-Drupal PHP applications.
Drupal only | 2
Academic | 2 |  | **Note about numbers: one academic library left a blank response to this question, and one
Public | 0 |  | academic library had "both" (see comment above) so was counted twice
Special | 0
If Drupal-only, receive support from other depts?
** poorly worded question; many just listed the support they get from other depts even if shared responsibilites, which may have been the better question to ask
Yes | 4
Server admin by sibling dept in org chart
Have 17 Drupal instances, most run on central IT dept servers with [NAME] IT support
Server administration by campus IT. Since IT does not have any linux experience, we also have an off-campus paid linux consultant for occasional server maintenance.
Server OS support, i.e., software patching, and maintaining our virtual server
No | 1
If shared, what other responsibilities?
They maintain the library's ezproxy configuration, the [NAME]'s Ex Libris Metalib server, and legacy non-drupal php and perl code.
Other web applications in the library. i.e., ContentDM
Non-Drupal website/application development, database design and administration, scripting languages, help desk support
other systems (wordpress, mrbs, etc.); ref desk, library & campus committees
[NAME] web applications, [NAME], system architecture development, external program support.  I do a lot of work in the international
information systems andsome of my time is on a contract with [a large organization]
The answer to 7 is 'both'.  I have one FTE devoted to Drupal and 2 additional FTE who work in Drupal, but do other non-drupal work, as well, including
the proxy server, a Metalib install, and non-Drupal PHP applications.
instructional and elearning design, training, web conferencing, multimedia development
Everything else dealing with our web presence, including static HTML/CSS, design, CONTENTdm, application development.
content management
Catalogue api usage; server maintenance; general scripting;
On the Systems side, maintenance of staff computers; maintenance of the Voyager catalog, ILLIAD, eRes, and more systems; and more than I think
of right now.  On the Web Services side, overall maintenance of the web presence, including some content updates, graphic design, and support of
digitization efforts.
Reference and instruction
Library ILS, ezproxy, SFX, server administration, digital library, contentdm
Internal library programming projects
educational technology, user support
Library instruction, reference services
Technology Helpdesk every third week.
helpdesk, ILS (Evergreen) enhancement, custom one-off web apps
Web master: Building coordinator, merit staff coordinator, oversees student employment program. Systems:  database development projects for
Metalib and Xerxes
Supporting all [NAME] web applications development (excluding applications referred to as enterprise systems) and server administration.
system management.  Reference. E-resources.  marketing
We run about 10 different servers, 2 of which host drupal sites.  We run a variety of Drupal sites, including our intranet, primary website, and an online
community for our campus. We manage ILLiad, SFX, EZProxy, online Chat (just the technical side of this), LibAnswers, LibGuides.
Bibliographer: order books in one area and teach some library instruction sessions. Responsible for all library Web Services including ILLiad Web
interface, CONTENTdm Web interface and all custom applications and web pages.
- overall maintenance of libraries' web presence, web services, - programming for other web services & internal databases - maintaining ILS
server administration for other library servers
Other dynamic content systems, web server account management
All areas of computer support
How many hours/week on lib website?
Less than 5 hours per week | 3 | Minimal | Moderate | Heavy
Academic | 2 |  | 2
Public | 1 | 1
Special | 0
6-10 hours per week | 4 | Minimal | Moderate | Heavy
Academic | 1 |  | 1
Public | 2 |  | 2
Special | 1 |  | 1
11-15 hours per week | 5 | Minimal | Moderate | Heavy
Academic | 5 |  | 3 | 2
Public | 0
Special | 0
16-20 hours per week | 7 | Minimal | Moderate | Heavy
Academic | 7 | 1 | 3 | 3
Public | 0
Special | 0
More than 20 hours per week | 8 | Minimal | Moderate | Heavy | Comment: Currently more than 20 because
Academic | 7 |  | 3 | 4 | still migrating
Public | 1 |  | 1
Special | 0
 |  |  |  |  | Comment: The question doesn't make sense
Other: | 2 | Minimal | Moderate | Heavy | for us. We have 3 people who work on Drupal.
Academic | 1 |  |  | 1 | 100% of their time is spent on the library
Public | 0 |  |  |  | website. But the lib website is not all Drupal.
Special | 1 | 1
 |  |  |  |  | Comment: highly variable depending on
 |  |  |  |  | what's happening
If NO Drupal lib staff, how support?
campus IT staff (small academic moderate customization)
Distributed editing?
 |  |  |  |  | Comment: Distribution is possible, but webmaster ends up making most
Yes | 27 | Minimal | Moderate | Heavy | changes
Academic | 23 | 1 | 12 | 10 | Comment: Distributed with understanding that web developer will fill in
Public | 2 |  | 2 |  | gaps if requested
Special | 2 | 1 | 1 |  | Comment: Simple text editing distributed, but changes to navigation and
 |  |  |  |  | search tools done by Web Services
 |  |  |  |  | Comment: Mixed, main pages by [NAME], librarians manage own
 |  |  |  |  | content
No | 2 | Minimal | Moderate | Heavy
Academic | 0
Public | 2 | 1 | 1 |  | Comment: Moving towards distributed.
Special | 0 |  |  |  | Comment: Only webmaster makes changes.
What # can add content to web?
Academic
Minimal | 6
Moderate | Anyone with need | 15 | All lib'ns plus selected staff | 25 (once Drupal adopted) | All professional staff for own bios, dept heads for pertinent pages | 9 | 8 | 10+ | 12
 | 29 | 30 | Everyone libguides, 8 on website | 4 with plans to expand
Heavy | Approx. 200 | 10 | 150 | 10 | 3 | All staff at different levels | 30 | 20
Public
Minimal | 1
Moderate | 12 (bloggers only) | 20+ | 7
Heavy
Special
Minimal | 4
Moderate
Heavy
For content, use different editing permissions?
Yes | 25
Academic | 22
Public | 2
Special | 1
No | 3
Academic | 1
Public | 1 | (plus 1 N/A)
Special | 1
For content, editing more, less, same difficulty as [NAME]?
More
Less
Same
Do Not Know
Other comments?
Drupal is not easy to learn, and requires heavy development to get a quality site. However, it is easier than trying to create a 2.0 site in-house.
Allow designers and developers freedom (work from home/coffee shops, flex time, etc). Avoid committee thinking, but include your web team on decision making processes
that will affect your web presence. Do not pile unrelated work onto your web team due to staffing shortages in other areas. Outsourcing may seem attractive as far as
budget is concerned, but you will be one of many clients to a contractor who cannot invest the time to understand your culture like full-time staff can. If you do decide to
contract, don't ask for speculative work ("Design something for us and we'll pay you if we like it"). It's evil. Oh, and pay well. :)
don't assume that just because librarians can make changes, that they all will want to. Some may want to leave it to others, which could/should be accomodated. have other
testing instances of drupal for the developers to play on, and also (another one) for the real keen non-systems staff. training done once is not done once and for all, must be
repeated and iterative
Similar issues apply to all content management scenarios - pasting in crappy code, adding animated gifs, etc.  Good procedures and policies from your previous scenario will
help.  Also - Drupal is more complicated even for the content editors, so expect that they'll need training and that you may need to do some work around permissions.
That last question (9c) doesn't quite make sense. 99% of people who use Microsoft Word do it incorrectly, without regard to document well-formedness. These people will
almost certainly be incapable of creating properly formed web pages in Drupal as well. It's not about *difficulty*; it's about understanding the nature of proper content creation.
I would have a content expert create the initial Drupal site, and give training on creating well-formed web documents before setting general library staff loose on the website.
It is critical to have PHP skills. We are stretched thin because we have only one person with real programming skills, and he has competing duties. Jquery is another useful
skill that we are trying to develop in Web Services.
I highly recommend this excellent presentation given by [NAME] at LITA National Forum a couple of weeks ago:
http://connect.ala.org/files/79651/editorial_and_technological_workflow_tools_pdf_56609.pdf .  It has been very helpful to me in working out content management issues on
our Drupal site, which we just launched in August.
You can never have all the staff you really need, but there are a couple of areas that we miss in our organization they are: 1. Usability person: Someone with a little expertise
in designing interfaces for better usability. 2. Designer - someone to make things look nice. 3. [NAME] to students/facutly: Somebody to set up a sustainable system for getting
regular feedback and testing from our user community.
You need more than one person with the skills necessary to implement and customize Drupal.
Time for developing and giving training is essential.  Developing training guides and sessions is time consuming but very important to do.  I haven't had as much time to focus
on this as I would like.  I'm mainly responsible for our site but ask for PHP work from our database person.  He has assisted with creating custom templates and figuring out
module patches.  He may eventually create simple modules if we have a need.  We have a network person who works with me on servers and maintains the server side of
the Drupal installations.
Staff users tend to find change frustrating. The idea of separating content from presentation is foreign to a lot of staff. Aim to use as few modules as possible (which tends
to still be a large number but if you can avoid module overload, it is highly suggestible). Due to the very nature of drupal it supports gradual change and implementation, so I
would suggest that you focus on the must haves, and then slowly bring in additional features. Even you have a large staff, this may not be as much of an issue but scope
creep tends to make the initial rollout (and migration of old web content) potentially painful.
time to train, learn and make mistakes. lots of free resources out there, training videos, podcasts, etc to take advantage of. make time for creating and delivering in house
training if you are going to have multiple authors/editors
There is a significant learning curve -- but a LOT of potential with Drupal.  And it's worth it --- so much you can do once you get started!
Have someone who loves Drupal (and there are folks who are crazy about it) enough to really get into and waylay the naysayers.
we're in the initial stages of migrating our site onto Drupal, so there's a heavy focus on the system.  We're also trying to do hiring, so our staff levels in support of Drupal
aren't stable at this point.
We maintain our own servers.  Depending on your level of customization, you're going to want to be able to work closely with the server administrator or [NAME] so you
can tweak rewrite rules, mysql performance, php configuration, etc, as well as do backups and restarte the server when necessary.
work across departments so people can handle their own content