Tag soup clean up

Question

The following list contains tags for which I cannot see any practical use. They are way too vague, probably just meta tags.
What should we do with those tags?

• body
• bulk-import – we have also bulk and import
• challenge
• code
• coding
• create
• customization
• default and defaults
• deleted and deleting
• duplicates
• field
• foreach
• fragment
• handling
• id
• lifetime
• list and lists
• management
• merging
• modifications
• multiple
• next
• parse
• paths
• permissions
• pre
• previous
• recursive
• registered
• [tag:rem. April oval]
• reset
• save
• scale
• sharing
• sort and sorting
• split
• structure and structuring
• switch
• table
• text
• theory
• transfer
• troubleshooting
• type
• ui
• update and updates

Already merged by me today

• guid with guids,
• header with headers,
• img with images
• l18n (!) with i18n
• link with links,
• meta-box with metabox,
• permalink with permalinks,
• previewing with previews,
• profile with profiles,
• user with users and
• global with globals.

Merged 29. April

• comment with comments
• directory with directories? Related: folder-structure
• localization with l10n. Which one should be canonical?]
• page with pages
• pictures with images
• uploading with uploads
• loop with loops and the-loop? Lingua wordpressiana prefers the singular …

What about automate and automation? Do we need one of them? If so: which one?

Merge candidates

• multisite with network
• registration with signup

Why is custom-fields linked to custom-field? We prefer the plural usually.

Related articles on Stack Exchange

• How do I correctly tag my questions?
• Should I remove tags that don't contribute to categorizing the question?
• Why do we tag questions?
• The Death of Meta Tags

  If the tag can’t work as the only tag on a question, it’s probably a meta-tag.
  If the tag commonly means different things to different people, it’s probably a meta-tag.

Answer 1

Just my 2 cents:

• body delete
• bulk-import leave, as there can be problems/errors during bulk import actions
• • bulk delete
• • and import leave as you can import other stuff too
• challenge Afaik, this was incorporated by @MikeSchinkel in the early days of WPSE
• code delete
• coding delete
• create delete
• customization delete
• default and defaults merge to plural
• deleted and deleting no idea. in detail they're different, but I'm not sure if they really add any value and so it's simply too broad in scope.
• duplicates again: too broad scope but somehow valid. Let's see if this gets more detail with example dublicate-posts, etc. Then every "sub"-tag could be made a synonym of the duplicates
• field delete
• foreach delete
• fragment delete
• handling delete
• id pfffft
• lifetime delete
• list and lists again: too broad scope, but no idea
• management delete
• merging too broad scope
• modifications delete
• multiple delete
• next this would normally apply to pagination stuff what we've got a lot. could be made a synonym of pagination
• parse no good Qs there, so delete
• paths valid
• permissions valid, but too broad scope
• pre delete
• previous see next ↑
• recursive delete (php only stuff as foreach, etc.)
• registered delete as too broad scope
• removal delete
• reset delete as too broad scope
• save valid, but too broad scope
• scale valid - WP is known for scaling issues when it comes to meta data for posts/taxonomies or the menu system
• sharing valid - could be merged if we got a social
• sort and sorting php only as mentioned with recursive, so delete
• split delete
• structure and structuring delete
• switch applies only to users and themes (afaik), so valid. But needs clean up if used in the php-meaning, which wouldn't happen too often
• table delete too broad scope, mixed meanings, etc. I'd have suggested to merge with wp-list-table, but we already got too many posts referring to html tables.
• text delete
• theory valid
• transfer no idea what that would be
• troubleshooting delete
• type delete
• ui valid
• update and updates merge to plural

I've written "too broad scope" several times. This means

»I don't think that someone would search the tag archive as the scope simply is too broad«

Getting no real result from a search in tag archives, means the archive is useless to everyone.

When I wrote "delete", then I meant deleting the tag from all questions and wait for it to get empty.