Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Comments on Creating tags is much easier than adding description

Parent

Creating tags is much easier than adding description

+10
−0

It is probably not controversial to say that if you're creating a tag, you should add a description for it. Otherwise, how will anyone else know what you intended the tag to be used for?

Unfortunately, this is a challenge right now on Codidact.

Creating tags is a very easy ability. I'm not sure if I did anything at all to gain it, it was available the first time I tried after making a handful of posts.

However, I cannot edit the description of the tags I create. Of course, I try to make the tag name be obvious and self-explanatory, but sometimes this is not possible.

https://meta.codidact.com/abilities/edit_tags says that:

To earn this ability, you need to have roughly a 97.5% approval rate for suggested edits to either the detailed tag wiki or the usage guidance for tags, with a hard minimum of 76 approved suggested edits (these numbers may vary from site to site).

So I must edit existing tag wikis at least 76 times (more if some edits are rejected)! Well, that's going to be a while, because most existing tag descriptions are already not bad and there's not much to edit. Ironically, there are fewer tags with descriptions because of this requirement. I also don't want to engage in mod-grinding by making lots of trivial, contrived edits just to gain the privilege.

  1. There should not be such a big difference between creating tags and editing their description. If you trust a user with one it doesn't make sense to not trust them with the other. Either both abilities must be hard to gain, or easy.
  2. Adding a description to a tag you created is a good practice, new users should not be discouraged from it. We don't want more tags without a description! We want fewer. An exception should be made and the creator of a tag should always be able to edit it.
History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

Although I can understand why you feel the current behavior is wrong, may I suggest that you change t... (2 comments)
Post
+4
−0

Although I have just created my first new tag as a fairly new user and thus profited from the current liberal approach, I would propose to raise the bar for creating a tag to the same threshold as for editing tag metadata (which might be somewhat lowered in return, but that is a different discussion). I agree with the argument by @matthewsnyder on why the gap is not helpful.

The rationale for raising the bar for creation is that new contributors should, in my opinion, have some time (and I acknowledge that it would be "enforced" on them) to get used to the categorization scheme on a site before changing it, in order to prevent tag proliferation which on Similarly Engineered sites can lead to orphaned tags or synonymous tags (sometimes so close in their names that someone should have noticed much earlier).

If they feel a tag is missing, they can still ask on the corresponding Meta site for a community consensus about the need for a new tag, which can then be implemented by an established user who has gained that ability.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

2 comment threads

Strange behavior of editing dialog (3 comments)
Yes, let's raise the bar, but later? (2 comments)
Yes, let's raise the bar, but later?
matthewsnyder‭ wrote over 1 year ago

I'm okay with raising the bar also.

It can sometimes be annoying when it obviously should be a tag, but then you're not allowed to make them. Especially when you use an alt account for privacy (eg. sensitive/identifiable questions), and it treats you like a clueless noob when you know what you're doing. But so long as the bar is no unreasonable high, I'm sure we can deal with it.

However, I consider Codidact right now to be in a bootstrap phase, so we should defer raising the bar until we have accumulated enough healthy activity. If we did it right now we could end up with situations where too few people have the mod ability for the site to function.

However, I think the discrepancy between creation and edits is a bit more urgent - it makes a difference now.

AdminBee‭ wrote over 1 year ago · edited over 1 year ago

Interesting point. I guess the aspect about the "bootstrapping" phase didn't come to my mind immediately because CD has already been around for a few years now. But then again, you are right - (at least in the case of LS CD), the community is still small and the usage frequency as well. So the amount of "proliferation" that would need to be corrected should probably stay at a manageable level for the moment even if we don't raise the bar for tag creation just yet. And as I said, I completely concur that creating a tag without the ability to describe what its scope should be is somewhat pointless.