Unit 5: Adding Tools to Drupal

This week we added some tools to Drupal such as the image module and CCK and Date fields.  These tools made my collection more presentable in addition to enhancing it.  For example, the fields are displayed in bold with the applicable information underneath it which made it more noticeable.  In addition, for the records consisting of an image, it was nice to see the image displayed in the record along with the other information about the image.  I ended up installing the lightbox2 module; however, I had wanted to add the audio module since I have one recording in my collection.  Unfortunately, in addition to having to install 3 other modules, the 6.x update is incomplete.  Overall, once the creator gets a handle of how to install and configure modules to enhance the collection, Drupal can be a suitable content management system.

Unit 4: Building Collection in Drupal

Entering my digital collection in Drupal has begun.  Drupal allows the creator of the opportunity to be as basic or extensive as one wants to be when developing the categories one wants to use for their digital collections.  Planning at the forefront and prior to entering any information is critical.  Already having a list of categories and controlled vocabularies makes the entering of information in Drupal a much faster and easier process.  In addition, I appreciate Drupal’s flexibility to allow categories to either be free-tagged or pre-defined.  When using controlled vocabulary, knowledge in this is greatly helpful.  The search function is definitely helpful for users; however it is critical that the record includes the necessary keywords that will allow users to find the information they are searching.  This is when tagging proves to be useful.

Unit 3: Pace of IRLS 675 Course

The tech assignments have moved along just fine.  Luckily, I have been able to install Ubuntu, VirtualBox and Drupal with minimal issues.  I look forward to working with Drupal and starting my digital collection.  Keeping up with the two discussions (technical and management) has been a struggle.  More specifically, keeping up with the readings required for the technical portion of the class has been a bit difficult.  Nonetheless, I do understand the importance of both discussion sections and appreciate how the management section has been included in the class.  Somehow, in the mist off all the assignments, I missed that we were supposed to post our digital object collection on the blog (which will be added to my Unit 1 post).  I did post my blog URL in D2l, but I have no idea how I missed the blog post. I plan to make a few changes to the titles of the blog posts I have previously posted for this course. 

Unit 2: Case Study Review on the Implementation of a Content Management System

In this course, we have been exposed to the advantages of implementing a content management system for the library web site. A study at Wheaton College was conducted explaining the experiences of the college using a content management system for the library web site. The case study is outlined in “Untangling a tangled web: a case study in choosing and implementing a CMS” authored by Terry L. Huttenlock, Jeff W. Beaird, and Ronald W. Fordham. The importance of the library web site at Wheaton College became evident when electronic resources boosted; however web site maintenance became a hardship. As a result, the library searched for an alternative: an open source CMS in which the web site could be maintained by non-programmers, have links to electronic resources, be straightforward, have the ability to migrate information from the old website, and be installed fairly quickly. Wheaton selected WebGUI. WebGUI provides support services (additional price), implements Perl, Apache and MySQL. Installing WebGUI required experience with mod_perl. The installation process was somewhat painless; however, at first navigating the system was a challenge as it involved a lot of figuring things out and knowing HTML. Once the system was figured out, it ran smoothly. Security issues were encountered after the first year; however, they were solved promptly. In the end, Wheaton was happy with WebGUI as updates and adding pages was simple. WebGUI was upgraded in 2004 which caused staff to learn how to navigate a new system and create a web site similar to the previous. Once again, the system was figured out and it ran smoothly. Wheaton was happy with WebGUI.

Reading this article was helpful as it makes one understand that there may be struggles when implementing an open source CMS; however, one should not be discouraged. It is important to think of the outcome and that in the end the new web site will be beneficial to its users.