Allow user AND module to set terms

Yes version 1 of the module removes the taxonomy select from the node form, removes all previous tags from the autovocabulary and adds new ones. If you want users to tag, you should use a separate vocabulary. Probably you would want a a freetagging vocab for users and a carefully designed, closed vocab for automating.
Make a feature request for version 2 if you see a better way.

OK, I think both the user and the module should be able to set terms, so you always have the user's terms and the system terms together.

Interesting because I was looking around and the autotag module has a problem in that respect too. That is, it changes the flags you can setup in your taxonomy. Not only that, the automatic requires another screen. So not that automatic. 8-)

I was hoping this one would solve my problem. Too bad.

Thank you.
Alexis Wilke

If this feature request is implemented please make it an option:
in my use case I adopted autocategorisation in order to prevent
users from entering their own tags.

Skizzo,

I think there is a need for different types of "auto-tag" and this one (autocategorise) is one of them. Now I actually wrote my own module called MO Auto add terms. That way I have exactly the functionality I need, namely, I want to add new tags and make sure that I don't miss any. Especially, if I add a new tag, I want all my older pages to be updated too. And so far I have not seen any other module even remotely doing that sort of a thing.

Now it would probably be easy for my module to not allow for new tags to be inserted... That's an idea for a new feature.

Thank you.
Alexis Wilke

Actually, I thought that preventing new tags by user was a native feature in autocategorise, as the module home page reads "Users cannot be trusted to categorise things themselves". Thank you for mentioning the "MO Auto add terms" module, and considering my request for inclusion, although I try to avoid modules that are not registered with Drupal CVS. What I ended up doing, is to use autocategorise and prevent user tagging via Taxonomy Role: not the ideal solution, as that means adding an extra module.

Mr Wilke,

I am also desperate to find an autotag module that works. I have two vocabularies: Furniture Type (eg. table, coffee table, chair, easy chair etc.) and Materials (oak, ripple sycamore, burr walnut). These apply to a CCK content type Exhibit, which has title (including Furniture Type), description (including Materials) and photo fields. Users will upload photos and add a title and brief description, the taxonomy terms will almost duplicate these fields, so it's a perfect fit for auto tagging. The content will be checked before publication, so terms can be added to the vocabs at this stage.

Having tried and failed with autocategorise and taxonomy autotagger, I was happy to pay the 10 bucks for your module. Had I been able to read the doc files before purchase, I'd have seen that it won't tag terms with spaces or dashes (i.e. more than one word). Having installed it, I find that only one vocabulary at a time is possible. Perhaps you could be more up front about the module's capabilities and bugs on your website? I usually check the issues lists here first, but like I said, I was desperate...

Hi woodbutcher,

The problem with the "only one vocabulary" is now fixed.

To solve that problem in the autocategorise, the author would need to load all the terms for the node, tweak those of the current vocabulary (i.e. add "missing" terms") and then save the result.

At this time, he (and I was also doing that in version 1.0, get 1.1 instead!) only loads the terms of the current vocabulary and calls the taxonomy save function which overwrites ALL the terms. I find the taxonomy module rather bad in that regard.

As for multi-word I will fix my module. The autocategorise would not work properly for me because something like:

Redwood trees lose bark as they grow

"wood" and "wood tree" are matches (assuming you have such tags,) but the node includes "redwood", not "wood". In this example, it may be okay, but in English you have loads of words that would match in that way (i.e. something matches some and thing, taxonomy matches tax, overwrite matches over and write--and those are words in this small message and that's just broken, something should not match thing).

This being said, the solution for autocategorise is simple:

1. Load all the terms (or all but those from the vocabulary being worked on)
2. Add terms from the node
3. Save the larger buffer

And be careful with the Load since there is a caching going on in many taxonomy functions!

Thank you.
Alexis Wilke

Hi Alexis,

That's great news, your prompt reply gives me confidence to continue. I agree that only whole words and phrases containing them should be picked up, if 'redwood' needs to be tagged as 'wood' I can add it as a child term with 'wood' as parent. So I guess a check that the word has a space at both ends would be needed.

Ideally, a phrase would override component words: so content with 'blanket chest' would not be tagged as 'chest' if 'blanket chest' was a term as well as 'chest'. That would be a very powerful tool, but looks like a nightmare to code (to a novice like me). In our application, most phrase terms will be children of component words - the rare exceptions can be caught by a site editor, hence the need for hand tagging to override the automatic tags.

By the way, the download link for v1.1 seems broken - I get 'your cart is currently empty'.

Thanks,

Woodbutcher

Actually I misunderstood the question. This module effectively prohibits free tagging because it removes the taxonomy select form from the node form. If users are writing their own tags, that's not autocategorisation.
The idea behind the module is that the administrator determines the categories and the matching terms, and then nodes are automatically categorised according to those criteria.

matslats,

I agree that the question was something else.

Now when you say "removes all previous tags from the auto-vocabulary" it actually removes all the tags from ALL the vocabularies. Try adding another "normal" category (without auto-categorise turned on) and see that the selection for that extra category doesn't hold too well.

Now my module, MO Auto add terms, does what the user was asking. It lets users add new terms (unless Tag is turned off) and it also automatically adds terms that are found in the taxonomy. The only requirement is that you have Multiple turned on.

Now I like the concept of auto-categories, because when you turn off the Tag flag you still get a complete list of terms on your page which would not automatically be useful if there is a module that auto-reassign the terms anyway.

Thank you.
Alexis Wilke

Well, is it possible to add the user and module usecase to this module? I can't be the only one who's looking for something like that right?

Minqenan,

I don't think the author wants to do that in his module... You could give a try to MO Auto add terms though...

Thank you.
Alexis Wilke

The author said to make a feature request, and that's what this is. Isn't the heavy work already done anyway, just need an option to disable the disabling of user tags.

Minqensan,

Yes. A true/false flag would suffice here!