Spreadsheet: 01526083-4d92-4c53-9d31-5480c8ad26b2
Sheet: Full Data

Drupal Survey Questions
1) Are you an academic, public, or special library? | Academic | Academic | Academic | Academic | Academic | Academic | Academic | Special | Academic | Special | Public | Academic | Academic | Academic | Academic | Academic | Academic | Academic | Academic | Academic | Public | Academic | Academic | Public | Academic | Academic | Academic | Academic | Public
1a) For academic libraries: what is your institution’s full-time equivalent (FTE)? | 1,000 - 2,999 | Over 20,000 | 10,000 - 19,999 | 3,000 - 9,999 | 10,000 - 19,999 | Over 20,000 | Over 20,000 |  | Under 1,000 |  |  | 10,000 - 19,999 | 10,000 - 19,999 | 1,000 - 2,999 | 3,000 - 9,999 | 10,000 - 19,999 | 3,000 - 9,999 | Over 20,000 | 3,000 - 9,999 | 10,000 - 19,999 |  | 10,000 - 19,999 | 10,000 - 19,999 | Over 20,000 | 10,000 - 19,999 | 10,000 - 19,999 | 10,000 - 19,999 | Over 20,000
1b) For public libraries: what is the population in your legal service area? |  |  |  |  |  |  |  |  |  |  | 500,000 and over |  |  |  |  |  |  |  |  |  | 25,000 -99,999 |  |  |  |  |  |  |  | 10,000 - 24,999
1c) For special libraries: how many people do you serve? |  |  |  |  |  |  |  | 100 and over |  | 100 and over
2) Is your Drupal website minimally, moderately, or heavily customized? | Moderately | Heavily | Moderately | Heavily | Moderately | Heavily | Heavily | Minimally | Heavily | Moderately | Moderately | Moderately | Moderately | Moderately | Heavily | Moderately | Heavily | Moderately | Heavily | Heavily | Moderately | Moderately | Moderately | Minimally | Moderately | Heavily | Minimally | Moderately | Moderately
2a) If your Drupal site is customized, do you do template customization and module development in-house? | Yes | Yes | Yes | Yes | Yes | Yes | Yes |  | Yes | Yes | No | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No | No | Yes | Yes | No | Yes
3) Do you feel that your current level of staffing is sufficient to support your current and planned Drupal projects? | Yes | No | No | No | Yes | Yes | No | No | Yes | No | No | No | Yes | No | Yes | Yes | Yes | No | No | No | Yes | No | No | No | No | Yes | No | Yes | Yes
4) Do you have permanent library staff with responsibilities in Drupal development and maintenance? If not, please go to question 8. | No | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes
5) If you do have permanent library staff with responsibilities in Drupal development and maintenance, what skills do they have? |  | PHP, CSS, HTML, Server Administration | PHP, CSS, HTML, Graphic Design, Server Administration | PHP, CSS, HTML, Graphic Design, Server Administration, database administration, usability testing | PHP, CSS, HTML, Server Administration | PHP, CSS, HTML, Graphic Design, Server Administration, javascript, [NAME], ruby, etc | PHP, CSS, HTML, Graphic Design | CSS, HTML, Graphic Design | PHP, CSS, HTML, Graphic Design | PHP, CSS, HTML, Server Administration, Drupal skills | PHP, CSS, HTML, Server Administration | PHP, CSS, HTML, Graphic Design | PHP, CSS, HTML, sql, ajax | CSS, HTML | PHP, CSS, HTML, Graphic Design, Server Administration | PHP, CSS, HTML, Server Administration | PHP, CSS, HTML, Graphic Design, Server Administration, SQL, multimedia | PHP, CSS, HTML, Server Administration | PHP, CSS, HTML, Server Administration | PHP, CSS, HTML | PHP, CSS, HTML, Server Administration, perl, python, javascript | PHP, CSS, HTML, Graphic Design, Server Administration | PHP, CSS, HTML, Graphic Design, Server Administration | CSS, HTML, Server Administration | PHP, CSS, HTML, Server Administration | PHP, CSS, HTML, Graphic Design, Server Administration | PHP, CSS, HTML, Server Administration | PHP, CSS, HTML, Graphic Design, Server Administration, Accessibility training | PHP, CSS, HTML
6) If you do have permanent staff with responsibilities in Drupal development and maintenance, in which department do they reside? |  | Our department is kinda a sibling to Library Systems and Technical Services | Library Systems | New Media | Library Systems | Library IT | Library Web Systems | unrelated to IT | Library Systems | Library Systems, Technical Services | Library Systems | Library Systems, Web Services | Library Systems | Reference | Library Systems | Library Systems, Technical Services | branch library | Library Systems | Library Systems | Library Systems | Technology | Library Systems, Administration | Library Systems | Library Systems | Library Systems | Web Services (library department) | Library Systems | Library Systems | Computer Services
7) If you do have permanent library staff with responsibilities in Drupal development and maintenance, do they have shared responsibilities, or are they solely devoted to Drupal development and maintenance? |  | Shared responsibilities | Shared responsibilities | Shared responsibilities | Shared responsibilities | Shared responsibilities | Shared responsibilities | Shared responsibilities | Shared responsibilities | Shared responsibilities | Shared responsibilities | Shared responsibilities | Shared responsibilities | Shared responsibilities | Shared responsibilities | Shared responsibilities | Shared responsibilities | Drupal only | Shared responsibilities | Shared responsibilities | Shared responsibilities | Shared responsibilities | Shared responsibilities | Shared responsibilities | Shared responsibilities | Shared responsibilities | Shared responsibilities | Shared responsibilities | Shared responsibilities
7a) If they are solely devoted to Drupal development and maintenance, do they receive support from other departments in the library or organization?  (For exanple, server administation is done by city or campus IT.) If yes, please tell us what type of support. |  | Server administration is done by a separate sibling department in our org chart. |  |  |  | We have about 17 Drupal sites with the entire library system.  Most sites run on servers hosted by central IT dept but with [NAME] IT support | 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. |  |  |  |  |  |  | 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
7b) If they have shared responsibilities beyond Drupal development and maintenance, what are their other areas of focus? |  | 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 and some 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. | Other IT | 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
7c) If you have library staff with responsibility for Drupal, and they also have responsibilities in other areas, how many hours a week do they devote to the library website (including maintenance like server backup, account administration, software updates, etc.)? | Less than 5 hours per week | More than 20 hours per week | Currently more than 20 because are still migrating | More than 20 hours per week | More than 20 hours per week | 16-20 hours per week | More than 20 hours per week | highly variable depending on what's happening | The question doesn't make sense for us. We have 3 people who work on Drupal. 100% of their time is spent on the library website. But the library website is not all Drupal. | 6-10 hours per week | More than 20 hours per week | More than 20 hours per week | Less than 5 hours per week | 11-15 hours per week | 16-20 hours per week | 16-20 hours per week | 11-15 hours per week | 16-20 hours per week | 16-20 hours per week | 11-15 hours per week | 6-10 hours per week | 6-10 hours per week | 11-15 hours per week | Less than 5 hours per week | 11-15 hours per week | More than 20 hours per week | 16-20 hours per week | 16-20 hours per week | 6-10 hours per week
8) If you do NOT have permanent library staff with Drupal expertise, how do you support Drupal development and maintenance? | Campus IT staff
9) Do you distribute website editing around the library, or does only your web manager make content changes to the website? | Distributed around library. | Distributed around library. | Distribution is possible, but webmaster ends up making most changes | Distributed around library. | Distributed, but with understanding that web developer will fill in gaps if requested | Distributed around library. | Distributed around library. | Distributed around library. | Distributed around library. | Distributed around library. | Moving toward distributed editing | simplete text editing is distrubted, but changes to navigation and search tools are done by web services. | Distributed around library. | Distributed around library. | Distributed around library. | Distributed around library. | Distributed around library. | Distributed around library. | Distributed around library. | Distributed around library. | Distributed around library. | Distributed around library. | Distributed around library. | Only webmaster makes changes. | Distributed around library. | Distributed around library. | Distributed around library. | mixed -- main pages done by [NAME], librarians manage own content | Distributed around library.
9a) If more than one person can make content changes to the website, what number of library staff have permission to maintain content on the site? | anyone who has a need to do so | Around 200. | 15 | 10 | all librarians if they choose (mostly on their areas), and selected staff | 2010-05-10 00:00:00 | 150 | 4 | Drupal hasn't been 100% adopted yet. When it is, about 25 people will have permission. | 2010-10-15 00:00:00 | bloggers only; about 12. | all professional staff have access to their own bio pages. Department heads have control over pages that are pertinient to them. | 9 | 8 | 10 | 10+ | 3 | 12 | All staff have limited access, different levels | 30 | 20+ | 29 | 30 |  | everyone has libguides permission.  8 people on the library website (this could grow according to need) | 20 | 6 | 4 (currently -- plans to expand) | 7
9b) If more than one person can make content changes to the website, do library staff have different levels of permissions (for example, some can only draft content while others can edit and publish?) | No | Yes | Yes | Yes | Yes | Yes | Yes | No | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No | Yes | Yes |  | Yes | Yes | Yes | Yes | Yes
9c) In your opinion, is content updating more/less difficult than using Microsoft Word, or about the same? | Less difficult | Less difficult | More difficult | About the same | About the same | Less difficult | About the same | Do not know | About the same | About the same | About the same | Less difficult | More difficult | About the same | More difficult | Less difficult | Less difficult | Less difficult | About the same | About the same | About the same | About the same | About the same |  | More difficult | Less difficult | About the same | About the same | About the same
10) What other issues should we take into consideration when developing our staffing model?  Please share any other comments you have here. |  |  | 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 | You can outsource theme development, but having an in house person with a good understanding of PHP is important, even if you're not doing custom module development. |  | 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. |  | The specific Drupal experience of a particular developer is the biggest factor in staffing. One experienced [NAME] equals about three or more newbies. | 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