By felixsmile on

Hello,

As the people who are going to edit my site are not always IT-professionals (that's a euphemism...), I would like to force them to use a taxonomy-term to classify their content.

Now, it is possible to mark a vocabulary as required, but that is not what I want. Why? Because I will have several vocabularies, and some content will be in one vocabulary and will have no link with any other vocabulary.

A possible workaround for this may be using the Module Taxonomy Access Control, and give each user only the rights for one Vocabulary, then, it works out fine.

However, this is not an acceptable solution for me. I would like to give the user the choice of which vocabulary he wants to put his page in, but force him to put it into one of the vocabularies, so that he cannot forget.

Thank you very much in advance for your help,

Felix.

⋅ Categories: Drupal 4.7.x

Comments

cog.rusty’s picture

cog.rusty commented

I don't think I understand what you want to do. Can you give a simplified example?

I'll add a few thoughts anyway. Are you familiar with CCK or (the older) flexinode, which can create content types just like 'page' and 'story'?

When a user goes to create a node (of a particular content type) all vocabularies which apply to this content type will appear. Using many different content types (e.g. article, review...) for content creation may give you a lot of flexibility. An article could be associated with vocabularies A B C and a review with A C F. The user chooses any permitted content type (same as 'add story').

Sometimes people expect too much from taxonomy alone, and that's a source of confusion. That's why I say that content types are for creating content and taxonomy for listing it.

felixsmile’s picture

felixsmile commented

You are too modest! You perfectly got my point :)

I'll reformulate it, so that other users can benefit from your idea.

Vocabulary 1:
TermA1
TermA2
Vocabulary 2:
TermB1
TermB2

Some editors should be able to access only Vocabulary 1, and then, they should choose whether their article is a "TermA1" article or a "TermA2" article. They SHOULD means that they should not have any choice: they have to put the article into one of the two categories.

The solution now looks roughly like this:

Every vocabulary is marked as "Requested", which forces the editor to choose one of the terms of that Vocabulary. However, every Vocabulary is only linked to one particular type of content type, so that a node cannot be in more than one Vocabulary, which is what I wanted.

I am using CCK and the Module Taxonomy Access Control, both together do a wonderful job (FlexiNode is not as powerful, if I analysed it right: am I wrong?).

Thank you very much! Have a nice day,

Felix.