I noticed that adding a tag to a post in draft mode now automatically adds the parent tag. But it’s not clear to the user why two tags are being added at once. This also contributes to the overtagging of posts.
On Wikipedia, the guideline is to tag pages with the most specific categories they belong to. So if category B is a child of category A, then pages that belong to both A and B should only be tagged with B, whereas pages in A \ B should only be tagged with A.
In general, I think the EA Forum should be more thoughtful about tags. If we want to replicate what Wikipedia does, one possible approach is to automatically remove a parent tag from a post when a user adds a child tag to that post. However, this messes with the voting mechanism of tags. A less disruptive approach is to hide parent tags by default when both the child and parent are added to a post (or hide the child tags if the parent is a white tag), and then allow the user to expand the full list of tags.
Thanks, I think think this is good feedback. I recognize the way parent /​ child tags work now isn’t ideal. We’ll have to prioritize improving this against other things we could work on!
I noticed that adding a tag to a post in draft mode now automatically adds the parent tag. But it’s not clear to the user why two tags are being added at once. This also contributes to the overtagging of posts.
On Wikipedia, the guideline is to tag pages with the most specific categories they belong to. So if category B is a child of category A, then pages that belong to both A and B should only be tagged with B, whereas pages in A \ B should only be tagged with A.
In general, I think the EA Forum should be more thoughtful about tags. If we want to replicate what Wikipedia does, one possible approach is to automatically remove a parent tag from a post when a user adds a child tag to that post. However, this messes with the voting mechanism of tags. A less disruptive approach is to hide parent tags by default when both the child and parent are added to a post (or hide the child tags if the parent is a white tag), and then allow the user to expand the full list of tags.
Thanks, I think think this is good feedback. I recognize the way parent /​ child tags work now isn’t ideal. We’ll have to prioritize improving this against other things we could work on!