Completely agree. One of my biggest gripes with switching from subtags to properties (i.e. a text property called “affiliation” rather than a tag #affiliation/group) is that I can’t see the amount of notes with each affiliated group as easily as just looking at tags and seeing I’ve got 15 notes affiliated with a group. It makes querying easier to have it as a property, BUT I regretted changing it from a tag to a property when I realized there was no easy way to see how many notes were affiliated with each group, what the names of the groups were, and easily change them en masse (such as with the tag wrangler plugin). Having multiple tags fields would make this a breeze and it would be WAY easier for me to remember all the tag types I want associated with a note (i.e. what to build in with a template).