Drupal Intranet project: Journal Part 4

Part 4 of 4


If my place of employment decides to transition to a web content management system and use the ideas outlined in this journal, I imagine that implementation will involve the following steps:

1.      The Drupal installation and setup will be handled by the library’s technology person, assisted by the City’s IT Department to help with the server and security side, and one representative, preferably Web 2.0 aware from Circulation, Reference, Technical Services, and Library Administration.

2.      After installation and setup the library persons mentioned above will be the responsible in identifying content from the previous setup that will be transferred to Drupal.

3.      An all-staff meeting to introduce Drupal and the evangelist and trainers will then be held to start the process of transitioning the organization to the new system.

4.      The evangelists will be responsible for identifying correct versions and collaborating with content creators and assisting them in transitioning content from the old system to the new one.

5.      I imagine that this can go on from three to six months depending on how quickly staff members are adapting to the new system.

6.      Naming convention standards and other content creation rules might even be develop to standardize everything.

7.      Once the library’s technology person determines that the transition to the new system is complete, the old system will be put offline. I imagine this happening after a year from the installation and setup of Drupal. A year is also a good time frame since it will give the organization enough time to iron out problems and issues that will crop up.

Future possibilities

1.      Add a calendar and schedule code tracker.

2.      Add an instant messaging module.

3.      Add and create photo galleries and a depository for multi-media

4.      Develop avatars and expand user profiles

5.      Create and develop an organizational chart that links to user permissions

6.      Create several user permissions tailored to pages and levels of access. For example, a page on library budget can be viewed and edited by users with a certain level of permission.

Acknowledgement of Content Sources for MY Library System

As this project is a proof of concept rather than an actual intranet of an existing library system, I used the policies and procedures, information, forms, and images from different sources to demonstrate the features of Drupal as a content management system. Some of these documents were sourced from document repositories like the Municipal and Research Services Center of Washington that makes available on the Web sample library policies created by different library system under its jurisdiction. Others were sourced from the Library Success wiki’s section on wikis, and the rest were sourced from different library websites. I altered the document to replace the names of the original content creators to tailor it to my imaginary library system for presentation sake and not to claim ownership on the contents or the documents. To give credit to the original creator of the content I acknowledged the source of the document as a footnote on every document or cite them in this section.

ALA: Policy on Confidentiality of Patron Records. Retrieved May 7, 2009, from http://www.ala.org/Template.cfm?Section=Other_Policies_and_Guidelines&Template=/ContentManagement/ContentDisplay.cfm&ContentID=13084

Budget Approval Policy Statement. Source: http://midhudson.org/department/ member_information/policy/budget_approval_cycle_woodstock.pdf

Collection Development Policy. Source: http://midhudson.org/ department/member_information/policy/collectiondev_coxsackie.pdf

Customer Training and Customer Care handout. Memphis Library Intranet Wiki. Retrieved May 7, 2009, from http://tempo.memphislibrary.org/mediawiki/index.php/Customer_Care

Generic Disaster Plan Workbook. Source:http://www.calpreservation.org/disasters/ generic/unit1.html

Grievance Procedure policy. Illinois State Library sample. Retrieved May 7, 2009, from Midhudson.org sample policies page.

Photo Release form. Oak Park Public Library, IL photo release form found in the Midhudson.org sample policies page.


Farkas, M. G. (2007). Wikis. In Social software in libraries. New Jersey: Information Today, Inc.

Kraft, B. (2008). Case Study: Content Management System vs. Wikis for Community Website. OpenSource Magazine. Retrieved, May 1, 2009, from http://opensource.sys-con.com/node/784508

Wiki. (n.d.) Retrieved, May 7, 2009, from http://en.wikipedia.org/wiki/Wiki

End of Journal

Discuss - 7 Comments

  1. Dawn says:

    This is really great, Melvyn! I became very interested in Drupal while working on my WordPress project. I noticed a lot of debates about WordPress vs. Drupal online, so it is great to see how Drupal works on a project like this. I really appreciate hearing about your process in such detail–I have learned a lot!

  2. I cannot believe this will work!

  3. I was searching in Google for Drupal recommendations did your project go ok what was your experiences.

  4. I am setting up a blog for Customer Service training, my designer has suggested we use drupal would you agree as I will need to modify it http://www.service-training.co.uk

Add a Comment

Your email address will not be published. Note marked required (*) fields.