Autotagger Manual Update
| Project: | Taxonomy Autotagger |
| Version: | 6.x-1.x-dev |
| Component: | User interface |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
We finally got to understand how Autotagger works.
1. The admin settings determine whether or not you see the jquery based term selection panel. If you set the option for automatic tagging you don't get to see it. Conversly if you set it to manual update you do.
2. This is fine except when a node has been automatically tagged and you want to modify the tags, choosn by autotagger, to automatically exclude certain tags. Of course at this point you can't because since you are in automatic tagging mode you don't get the jquery user interface!
3. This is because unlike Calais, which we also use, autotagger does not determine whether or not it is operating on a new node or updating an existing node. We think it should have the same sort of options as Calais so that it can take different actions depending on the node status.
4. The jquery interface could be replaced with a simple check box, thereby reducing the number of module dependencies
5. Another user interfce issue is that rather than set all taxonomies as selected to be used for autotagging, the reverse should be true. In other words you should have to actually set the option. This ensures that you do not get unexpected resuts. We were using it to tag around 750 new articles per day, and this setting caused some of the taxonomies to be used when we didn't actually want them, just because we forgot to go and disable the automatic autotagging feature on each taxonomy.
6. We also got some weird results we think due to the fact that the headlines were html links to articles not found on the website. We we just wanted the summary indexed, Autotagger seemed to go out and pull in the article that the summary was linked to and tagged that.
7. All in all a great module...with great prospects.
Ade Atobatele

#1
I agree with points 3,5 and 7.