(Cross-posting to Web4Lib, Code4Lib, and Drupal4Lib - apologies for any
We're looking at developing a new library website in Drupal, and would like to
create a sensible staffing model for future development and maintenance. We
are a large academic library looking to do moderate to heavy customization.
What sort of staff do we need to support a large, relatively complex Drupal
site? I've checked the archives, but didn't see any recent posts on the
Please feel free to either take our 5-10 minute online survey at
http://goo.gl/Oqx3 or reply to me directly using the questions below. I'm
happy to summarize and post back to the list.
Thanks in advance,
Research Instruction Librarian
Northeastern University, 270 Snell Library
360 Huntington Avenue Boston, MA02115
a.r...@neu.edu / 617-373-8548
Drupal Staffing Survey
Save typing! This survey is also available online.
This is a short survey exploring different staffing levels needed for Drupal
development. Any reports or publications based on this research will use only
group data and will not identify any individual. If you have any questions
about this study, please feel free to contact Amanda Rust by e-mailing
1) Are you an academic, public, or special library? *
1a) For academic libraries: what is your institution's full-time equivalent
1b) For public libraries: what is the population in your legal service area?
1c) For special libraries: how many people do you serve?
2) Is your Drupal website minimally, moderately, or heavily customized?
2a) If your Drupal site is customized, do you do template customization and
module development in-house?
3) Do you feel that your current level of staffing is sufficient to support
your current and planned Drupal projects?
4) Do you have permanent library staff with responsibilities in Drupal
development and maintenance? If not, please go to question 8.
5) If you do have permanent library staff with responsibilities in Drupal
development and maintenance, what skills do they have? (CSS, PHP, graphic
design, server administration, etc.)
6) If you do have permanent staff with responsibilities in Drupal development
and maintenance, in which department do they reside?
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?
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.
7b) If they have shared responsibilities beyond Drupal development and
maintenance, what are their other areas of focus?
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.)?
8) If you do NOT have permanent library staff with Drupal expertise, how do you
support Drupal development and maintenance?
9) Do you distribute website editing around the library, or does only your web
manager make content changes to the website?
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?
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?)
9c) In your opinion, is content updating more/less difficult than using
Microsoft Word, or 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.
If you are willing to share the URL of your library's Drupal website, please
include it below. However, this is not necessary -- we're happy to have your
anonymous responses, too!
If you would permit us to contact you with follow-up questions, please give us
your contact information. However, this is not necessary - we're happy to have
your anonymous response, too!