A while back, I wrote about taxonomies in Drupal - see post. We're now at the point where we're creating first drafts of our main taxonomies - a "master" taxonomy for organizing more or less ALL content on our flagship site and a few auxiliary ones for information like news and archives.
So, I'm revisiting some of the links and presentations from my previous post and doing some more research on how best to go about creating our taxonomies. There is an interesting discussion here, by the way, on the whole nodes/content types vs. taxonomy for organizing content in Drupal sites in which I definitely feel, with my limited Drupal knowledge (3-4 months as a user), that making everything a taxonomy is NOT the way to go. Content types and taxonomies are nicely complementary and should be kept that way.
Anyway, we've been in an IARD (Information Architecture Re-Design) process for about 9 months now and have so far created or done the following:
- Domain model
- Content audit
- some user interviews in the form of conversation with stakeholders, information gathered through a wiki, some polling and surveys
- Wireframing and prototyping
and are doing some content modeling (slightly out-of-order!) now. The domain model, content modeling exercises and content audit are all informing the creation of our "master" taxonomy. It's tricky stuff. I'm a librarian by training and thus have some significant experience with many classification systems (Dewey, LC, Dublin Core, etc.). But, keeping things simple and allowing for flexibility (not letting the level of specificity get too high or granular) is difficult.
So, here's what I'm reading to help:
as well as other IA resources. We're still at least 6 months away from the data & content migration phase so we have time to play around with various taxonomies and how they can help fix our confused IA.
We are still commited to only using 2 of the 3 types of vocabularies that Drupal offers, namely: simple lists of terms and organized hierarchies of terms. We are not planning to allow any free tagging of content initially. So, the taxonomies we employ will, at first, only be used "behind-the-scenes" for content editors to organize content and to aid users in navigation and creation of RSS feeds.
This could prove to be the most challenging part of our project so far. But, for me, it will likely be the most exciting and rewarding!
The Weekly Drupal is a weekly column on mavergames.net about Drupal from the perspective of a new user. Use this feed to subscribe.