Is there a way to have multiple tag fields in the page properties dialog and have them work with the default TagManager API? From what I've tried so far it looks like anything that is not in the root jcr:content node of a page or asset doesn't apply the cq:Taggable mixin to it. We are trying to spread out our structure of tags across fields so that authors don't have to navigate through multiple heirarchies. We are worries about that list becoming unwieldly to manage.
I'm not against doing some customiziation but it looks like the TagManager will only utilize fields named cq:tags in its query.