I have a Book
model that needs two separate Tag fields: genre
and tags
. I'm considering whether it would be better to write my own Genre
and BookTag
models for this, and linking it with ManyToManyField
s or using DjangoTagging to achieve the same.
Ultimately, I need users to be able to filter either according to genre
, or according to tag
, but I don't need the Tag Cloud functionality.
From what I can see, Django Tagging allows two TagField
s, but then it casts both into the same tag cloud. That's not a problem for me, but before I start refactoring all my code to use Django Tagging instead of my own ManyToMany fields, are there any other catches of using Django Tagging in this situation that I should be aware of?