Module Link: http://drupal.org/project/views_header_nodes The Views Header Nodes module allows you to have an editable psudo header that doesn't require going into the Views UI to modify. Who: Technical and non-technical When: Use this module when you know your users are going to need to edit the headers of a view but you don't want them messing around inside of the views UI. Think of this as node as a block for views headers. Where: Create a page view and then add a new display of type ""Header Node"". Then make sure that you add in a node with an address of {your page view}/header Why: All I can think of is keeping your users/clients out of the views and safely in node land. P.S. What the heck is a "Wibble"   Theme song "i dunno" by grapes. module-a-day_podcast-0028.mp3

Module Link: http://drupal.org/project/backreference The BackReference module causes your node reference field to back populate to the current node. While some modules of this type use additional tables to maintain the relationship this one just fills in a node reference field on the receiving end. Who: Technical and non-technical users. When: Use this module when you need to track node references in reverse but still want the full advantage of having that back reference stored inside the node so you can do node like things to it (views, etc). Where: When you add a node reference field you'll see an additional option to map that field to another node reference field. Why: It's just a different way to store reversed node references. It feels like it's doing things in more of a Drupal way.   Theme song "i dunno" by grapes. module-a-day_podcast-0027.mp3

Module Link: http://drupal.org/project/nodedump The Nodedump module helps you see the various information that is stored inside of the node object/array without having to add print or debugging statements. Who: Technical Users (module developers or themers who are diving into PHP) When: Use this module when you need to do some quick debugging or want to look at a naked node and you don't want to install the devel module or add debugging statements to your template files. Where: You can find the node dump at /admin/content/nodedump and you just need to enter in a node ID number. Why: It's possibly the quickest way to look at the naked node. You dirty Drupal person!   Theme song "i dunno" by grapes. module-a-day_podcast-0026.mp3

Module Link: http://drupal.org/project/schema The schema module helps module developers work with database tables. Who: Technical Users (module developers) When: I only use this when creating new modules. I'm lazy and use it to generate my schema for .install files. Where: You can find all of the schema options/reports in the site building section of the admin back end. Why: It gives you insights to how your tables are setup in relation to each other and it helps lazy module authors like me :)   Theme song "i dunno" by grapes. module-a-day_podcast-0025.mp3

Module Link: http://drupal.org/project/advanced_help Who: All users should enable this module and site developers should use this for documentation What: The advanced help module allows your modules to define more advanced help files than the basic functionality that Drupal provides. When: I enable this module on all of my sites. Where: You can find the advanced help index at /admin/advanced_help but quite a few modules reference advanced help directly Why: Lets face it, documentation isn't the strong point of most open source projects. This module helps you find the documentation you need directly in Drupal without having to drop to the filesystem and read things like the README.txt.   Theme song "i dunno" by grapes. module-a-day_podcast-0024.mp3

Module Link: http://drupal.org/project/views Who: Technical and non-technical users depending on how deep you wish to go What: The views module allows you to query information from your database and displaying it in configurable formats without knowing any SQL (Structured Query Language). When: Use this module when you need to pull out information (more than one node) and display it to a user. Where: You can find it under the Site Building section of the admin back end. Why: While some may see this as a nice to have module, I see it as required. Even though I write SQL day in and day out this module makes my life so much easier, I don't have to create crazy joins or even touch SQL if I don't want to. Some of my non-technical clients even use this interface to add various fields to the output!   Theme song "i dunno" by grapes. module-a-day_podcast-0023.mp3

Module Link: http://drupal.org/project/migrate Who: Only VERY technical users - You need to understand how the Table Wizard module works and not get frustrated too easily. What: The Migrate module allows you pull information from non-Drupal database tables and make them into Nodes, Users, Comments, etc. When: Use this module when you need to pull data from a table that isn't related to Drupal AND you want to get that data into a Drupal native table. Where: You can find this module in the admin back end under content management. Why: Writing import modules for Drupal is not fun and takes a lot of time. If you already have your information saved in your database this makes it easy-ish to import.   Theme song "i dunno" by grapes. module-a-day_podcast-0022.mp3

Module Link: http://drupal.org/project/tw Who: Only technical users - You pretty much have to understand how tables in databases work to get the most out of this module. What: The Table Wizard module allows you to interface Drupal with non-Drupal database tables in the form of views. When: Use this module when you need to pull data from a table that isn't related to Drupal but it does not need to go into nodes. Note: This module is useful for niche operations by its self but it really shines when paired with the Migrate module. Where: You can find this module in the admin back end under content management. Why: Not everything needs to be a full Drupal module. If you just need to reference data out of a database and you don't need it to be a full node, this is the module for you.   Theme song "i dunno" by grapes. module-a-day_podcast-0021.mp3

Module Link: http://drupal.org/project/filefield_paths Who: Technical and semi-technical users What: The FileFields Path module allows the paths for your uploaded fields contain information from your node (such as fields, node id, etc.) When: Use this module when you want to keep a clean /files directory. It is especially useful in keeping your files together when you have multiple file uploads per node. Where: After enabling the module go to your Content Types that have file uploads and configure a file field. Scroll down until you find a field set labeled "FileField Path Settings", expand it and take a look at the replacement tokens. Why: By default Drupal only allows you to use generic tokens when saving files on a node. This module gives you many more options that are tied to the specific node and all of it's fields.   Theme song "i dunno" by grapes. module-a-day_podcast-0020.mp3

Module Link: http://drupal.org/project/node_import Who: Technical users What: The node import module allows you to import nodes, users, blogs, books, comments, paths, taxonomy and many other things. When: Use this module when you have a lot of data stored in a program that doesn't have a real database behind it, you need it and Drupal and your software can export CSV (Comma Separated Values) files. Where: In the admin section under content management. Why: This module makes importing data from flat files fairly easy and is much easier than creating nodes by hand.   Theme song "i dunno" by grapes. module-a-day_podcast-0019.mp3