By rinehart on

I'm still working on the concept of Taxonomy and how I can apply it to my site. I publish an online magazine, and I'd like my content to be organized by issues, with sections in each issue and stories under each section. I was thinking about creating the following taxonomy to help organize my content:

  • Taxonomy - Magazine
    • Vocabulary - Issue 1
      • Multi-parent term - Features
      • Multi-parent term - Columns
      • Multi-parent term - A & E
      • Multi-parent term - News
      • Multi-parent term - Opinion
    • Vocabulary - Issue 2
      • Multi-parent term - Features
      • Multi-parent term - Columns
      • Multi-parent term - A & E
      • Multi-parent term - News
      • Multi-parent term - Opinion
    • ...

From there I suppose I could create a static page and link to a term under the appropriate vocabulary item. Am I getting this?

From that point I'd like to have the current issue's table of contents be profiled on the home page. For that I was thinking about publishing an RSS news feed and then subscribing to my own feed to get the content for the current issue.

Does that sound like a good approach, or am I running down a dead-end path?

Thanks,

Mac

Comments

rinehart’s picture

rinehart commented

Actually, now that I reflect on it RSS may not work because it doesn't include any mechanism for classifying articles by section. Any other ideas on how I can publish a table of contents for each issue?

moshe weitzman’s picture

moshe weitzman commented

your outline looks perfect to me. a static page can become your home page, as you suggest. note too that you can assign any URL as your home page, should that be desirable.

I'm not sure what you are using RSS for in this scenario.

rinehart’s picture

rinehart commented

Question on multi-parent terms. Say I have Parent X and Parent Y, and a term A that has both as a parent. Does that mean that navigating from X to A displays the same content as navigating from Y to A?

Thx,

Mac

moshe weitzman’s picture

moshe weitzman commented

yes, thats right.

killes@www.drop.org’s picture

killes@www.drop.org commented

I think that your whole structure should be in one vocabulary.

--
Drupal services
My Drupal services

nolageek’s picture

nolageek commented

I would go a different route:

Vocabulary - Topics
Term - Features
Term - Columns
Term - A & E
Term - News
Term - Opinion

Vocabulary - Issues
Term - Issue One
Term - Issue Two
Term - Issue Three

I think that would work.

rinehart’s picture

rinehart commented

Based on feedback from multi-parent term question above, I suspect that I'll need n+2 vocabularies for site navigation:

1) One Vocabulary for major nodes in the site like the home page, forums, links, eStore, advertising, etc
2) One Vocabulary for issues
3) One vocabulary for the Table of Contents (TOC) in each issue. I think that's necessary because when navigating to features for Nov, 2003, I don't want users to see all features from all time.

Theoretically I could put the current TOC in a block on the home page. My main site navigation taxonomy could have an entry for "archives" which loaded a node containing from the issues vocabulary. And each issue could have a node with a TOC for that issue. I think that's supported by the taxonomy_html module, correct?

- Mac

Uncas’s picture

Uncas commented

I have similar needs, I'm moving over my online magazine to Drupal. But having looked at the various possibilities, the Book module would seem to have exactly the features we need, as you can organize pages in whatever hierarchy you need by designating their "parent".

So you would have:

  • Issue 1 (book page with parent "root")
    • Features (book page with parent "Issue 1")
      • Feature 1 (book page with parent "Features")
      • Feature 2 (book page with parent "Features")

That way you automatically get a properly organized table of contents and hierarchical navigation pattern.

Taxonomy is best used for creating an overall index by subject. For example, mine being a travel magazine, my main vocabulary will be organized geographically:

  • Europe
    • France
      • Paris
      • Lyon

That way readers can navigate the content by issue but they can also find whatever has been published concerning Paris in features, news or whatever, in any issue.

Flavio Grassi

joel_guesclin’s picture

joel_guesclin commented

I agree with this approach. I have several magazines and had envisaged having each current magazine's "book header page" published to the front page. My idea was to leave it blank except for the automatically generated list of sub-pages (ie articles).

However when I do this, the table of contents does not appear on the front page, although it works fine when I approach via the "books" menu and the list of books.

Any ideas?

Joel